Loading
Salesforce now sends email only from verified domains. Read More
Market to Your Customers with Account Engagement
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Considerations for Completion Actions

          Considerations for Completion Actions

          Keep these considerations in mind when using standard and conditional completion actions.

          Required Editions

          Available in: All Account Engagement Editions

          General

          • Conditional completion actions aren’t available for classic emails or on link click triggers for enhanced emails.
          • Completion actions don’t execute in a defined order. To build a sequential prospect experience, use an Engagement Studio program.
          • Completion actions execute only for prospects and don’t affect visitors.
          • Completion actions aren’t retroactive and apply only to activities that happen after the action is added.
          • Most completion actions execute every time they’re triggered. However, completion actions based on email link clicks execute only one time per prospect per link.
          • If an Account Engagement user is deleted, Assign to User and Notify User actions associated with that user are skipped.
          • Completion actions can add processing time to form submissions. Depending on the type of actions and how many you have, it’s possible for a prospect to notice the form submission taking extra time to submit.
          • Image file downloads, filtered activities, unsubscribe link clicks, and email preference page clicks don’t trigger completion actions.

          Limits

          • To avoid conflicting completion actions, you can’t add a standard action and a conditional action that assigns a prospect. However, you can add one action that assigns a prospect to each conditional group.
          • It’s possible for a prospect to match multiple conditional actions. If a conflict occurs, the action that processes first is taken on the prospect. Actions don’t execute in a defined order.
          • You can have 15 total standard or conditional completion actions and six conditional groups on an asset. These limits don’t apply to classic emails.
          Example
          Example A single form can have 15 individual completion actions, or five conditional groups, with each group containing 3 individual completion actions, or 3 individual completion actions and four conditional groups, with each group containing 3 individual completion actions.
          • Emails have three trigger options: when a prospect opens an email, clicks a link in an email, or unsubscribes via an email. Enhanced emails can have 15 completion actions for open and unsubscribe triggers, and 5 completion actions for link click triggers. These limits don’t apply to classic emails.
          • If you used completion actions in Spring ’22 and earlier, it’s possible to have assets that exceed the limit of 15 total actions. Excess actions remain intact, and you can edit them without losing functionality. However, you can’t add more actions to your asset. If you delete actions, you can’t add more or add conditional groups until you fall below the limit of 15 actions.

          Throttling

          Sometimes prospects click a trigger button or link multiple times. To help prevent issues with your automations and prospect data, certain actions are throttled.

          • On file downloads and custom redirects, the Adjust Score action has a 24-hour throttling period.
          • If you set an Adjust Score completion action to be triggered by an email open, it can trigger on the first open. This functionality depends on your Email Open Scoring Rules.
          • The Send Autoresponder Email action has a 4-hour throttling period on most assets. On forms, there’s no throttling period and the prospect receives the email each time the form is submitted. On form handlers, there’s no throttling period if Disable Visitor Activity Throttling is enabled. The prospect receives the email each time the form is submitted.
           
          Loading
          Salesforce Help | Article