You are here:
Considerations for Using Page Actions
Keep these considerations in mind when using page actions.
- For page actions to work, including wildcards, the page must have Account Engagement tracking code or tracking code implemented via a tag manager.
-
Account Engagement matches the most specific page action first. If a page action for a specific URL doesn’t exist, we match wildcards. For example, you have a page action set up to execute for https://www.example.com/products/form and a wildcard page action set for https:// www.example.com/products/*. If a prospect visits https://www.example.com/products/form, the specific page action is triggered, not the wildcard action.
- Wildcards match both the base URL and anything that comes after the base URL. For example, you have a wildcard page action for https://www.example.com/products*. If a prospect visits either https://www.example.com/products/ or https://www.example.com/products/form, the wildcard action is triggered.
- Completion actions are applied only to prospects. Anonymous visitors browsing your site don’t trigger the actions.
- Page actions aren’t applied retroactively. They execute when the page is accessed. If an anonymous visitor who previously accessed the page later converts to a prospect, the visitor session is tied to the prospect record. The prospect appears in the page action report, but the completion actions aren’t applied. In this scenario, the page action also appears in the prospect audits but doesn’t appear in prospect activities.
- Page actions can be made from non-visible pages and pages that require the user to log in.
- One page action notification is triggered per prospect per page per hour. If one prospect visits a page with a page action, a notification is sent to the designated user. If the prospect returns to the same page within the one-hour time frame, it doesn’t trigger a second notification. However, if the same prospect visits a different page with a page action, that page action notification executes.
- Page actions match only exact URLs. If you create a page action for https://example.com, the page action doesn’t execute for https://www.example.com/. In this case, you need two separate page actions.
Using Page Actions with Scoring Categories
- Points from the page action apply to both the category score and overall score.
- Adding a scoring category to a page action doesn’t change previous behavior of the page actions. For example, changing the point value doesn’t retroactively change the score. It only affects the page action.
- Changing a page action’s scoring category is retroactive. For example, you assign the Generators scoring category to a page action. Later, you change the page action to assign the Power Drills scoring category instead. The points originally attributed to the Generators category switch to Power Drills.
Did this article solve your issue?
Let us know so we can improve!
