Goal metric for success/confirmation pages

Question

I have questions regarding goal tracking in specific scenarios:

Tracking Goals on Separate Pages: I'm wondering if we need to explicitly include success pages (e.g., post-form submission) OR order confirmation pages in my A/B test setup, even when the activity itself is running on a different initial page.
- For instance, consider a 5-step form. My current activity focuses on the first step, but the primary goal I'm tracking is the final "submit" button click on the fifth step.
- Similarly, if we're running an activity on the homepage, but our goal is to track order confirmations that occur on a separate order confirmation page, should that page be included in the activity setup?
Best Practices for Including Success/Confirmation Pages: If the answer to the first question is yes, what would be the recommended approach? Directly adding the success page as an additional page in the A/B test seems problematic, as users could potentially land on it directly without interacting with the main activity page, thus skewing the results.
Essentially, I'm trying to understand the optimal setup for an activity where content changes are limited to specific URLs, but goal tracking needs to encompass separate "downstream" pages that signify conversion.

I have also asked the same in the below thread.

https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/setting-a-goal-to-track-successful-form-submits/td-p/648380

pradnya_balvir · Accepted Answer

Hi @khushboobh3 ,

You Do Not Need to Include Success/Confirmation Pages in the Activity Setup

Run the test activity on a limited set of pages (e.g., Step 1 of a form, or the homepage).

Track goals/conversions that happen on separate, downstream pages (e.g., form submission on Step 5, or an order confirmation page).

You do not need to include the goal page in the activity setup as long as you're careful in how goals are implemented and tracked

Track Goals via Events, Not Page Views Alone

Use event-based tracking (e.g., click on "Submit", or page load of /thank-you ) rather than just relying on including the confirmation page in the activity.

This ensures: Only users who went through the test are counted.

You avoid counting users who might land directly on the success page (via reloads, bookmarks, or testing).

Thanks.

Pradnya

AnkitJasani29 · Answer

Hi @khushboobh3 ,

1) Yes, you need to explicitly include these downstream "success pages" in your goal tracking configuration - even if they are not part of the page where the A/B activity occurs. Adobe Target requires tracking goals across page flows, which means success metrics often need to be set on different URLs/pages than where the experience was shown.

2)

Use URL-based or event-based goal tracking with audience rules or custom success metrics.

Avoid including confirmation pages directly as part of the activity experience.

Instead, configure goal tracking separately via Adobe Target’s success metrics setup (e.g., “Viewed URL” or “Custom Event Fired” on a confirmation page).

This avoids inflating conversion counts from users who didn’t go through the tested experience.

Inscrivez-vous

Login social

Bienvenue

Login social

Analyse virus du fichier

Ce fichier ne peut pas être téléchargé