A visitor clicks on a custom redirect with an action of adding a tag. The visitor them fills out a form and becomes a prospect. The form has a…

The sequence of events begins when an anonymous visitor, tracked by a cookie, clicks a custom redirect. This action queues a completion action (to add a tag). When the same visitor submits a form, they are converted into a prospect. This conversion event triggers three primary outcomes:

1. The form submission itself is recorded as a key event in the new prospect's activity history (A).

2. The form's configured completion action executes immediately, adding the prospect to the specified list (B).

3. The previously queued completion action from the custom redirect click is now applied to the identified prospect, adding the tag (D).

All prior anonymous activities are merged with the new prospect record upon conversion.

C. While the custom redirect click is indeed associated with the new prospect's activity history, the form submission (A) and the two direct data modifications (B, D) represent the most significant outcomes of the conversion event.

E. This is incorrect. The first submission is the critical event that converts an anonymous visitor into an identified prospect, triggering all associated actions and activity consolidation.

1. Salesforce Help, Account Engagement Documentation, "How Visitors Become Prospects": This document explains the conversion process. It states, "When a visitor submits a form... Pardot creates a prospect record... All of the visitor’s previous activity is converted to prospect activity and is shown in the prospect record." This supports that both the form submission (A) and the prior custom redirect click (C) will be in the prospect's activities.

2. Salesforce Help, Account Engagement Documentation, "Completion Actions": This resource details how completion actions function. It specifies, "Completion actions are triggered by... form submissions, ...custom redirect clicks... When a visitor or prospect completes the action, the completion action is applied to their record." This confirms that the actions to add to a list (B) and add a tag (D) will both be executed. The action from the custom redirect is queued until the visitor is identified.

3. Salesforce Help, Account Engagement Documentation, "Track Clicks with Custom Redirects": This page confirms that custom redirects can have completion actions. It notes, "You can also add completion actions that fire after a prospect clicks the redirect." This supports the premise that the tagging action (D) is a valid outcome.