Confirming 'Viewed a Page' Goal Tracking for Off-Activity URLs

[KhushbooBh3]

Just want to make sure I'm getting this right:

If my A/B test is on one page, can I still track a goal using a "Viewed a page" metric on a different page (which is not the part of activity)?

Basically, even if the page isn't part of the actual activity setup, Target will still count it as a conversion if someone who saw my test ends up there?

I know a custom mbox might be "better" (in case of order-confirmation/thank-you pages) but I'm specifically curious about how "Viewed a page" links up the data in the reports when the goal page isn't in the activity. How does Target know to count that view towards my test results on the initial page? Just trying to wrap my head around the architecture of this.

Thanks in advance!

[purnimajena]

Hi @KhushbooBh3 ,

Yes! As long as the Target library is loaded and an mbox fires on the goal page, Target will count that page view as a conversion, even if it's not part of the activity setup.
If a user sees your test (on Page A) and later visits your goal page (Page B) in the same session, Target will count that as a conversion-even if Page B isn’t included in your activity setup. Target connects the dots because it remembers who saw the test and checks if they reach the goal page.
No need to include the goal page in the activity. Just make sure Target is running there

You can go through below link for more understanding on goal settings 

https://experienceleague.adobe.com/en/docs/target/using/activities/success-metrics/success-metrics 

[KhushbooBh3]

Thanks @purnimajena 

[AnkitJasani29 · Accepted solution]

Hi @KhushbooBh3 ,

Yes, Adobe Target can track goals on a different page.
If your A/B test is on Page A and the goal is "Viewed Page B", Adobe Target can count a visitor reaching Page B as a conversion as long as:

The same visitor ID/session is preserved across both pages.

Adobe Target is implemented correctly on both pages (via at.js or Web SDK).

The activity is configured with that goal metric (even if Page B isn't part of the activity experience setup).

Behind the scenes:
Adobe Target assigns a visitorID and sessionID.

When a user experiences a variant on Page A, and later visits Page B (where Target is also active), Target logs that "Page B was viewed by a user who saw an experience in Activity X".

This lets it attribute the goal completion back to the initial variant shown.

Custom mbox:
yes, they are useful for tracking more specific or non-pageview goals (like clicks or form submits). But for simple "Page B viewed" goals, you can just ensure at.js loads on Page B and that it matches the goal URL setup.

[KhushbooBh3]

Thanks @AnkitJasani29 

[pradnya_balvir]

Hi @KhushbooBh3 ,

Yes, Adobe Target can track a "Viewed a Page" conversion goal even if the page being viewed is not part of the actual activity/page where the A/B test is running. Here's how it works under the hood:

When a user is exposed to your A/B test (i.e., a Target activity delivers a variation on Page A), Adobe Target creates a visitor profile and logs the activity participation using cookies and the mbox/at.js framework.

If that same user later navigates to another page (Page B) — like a checkout confirmation or a key conversion page — and that page fires a Target mbox (either global targetPageParams() or just the default target-global-mbox), then:

Adobe Target checks: "Has this user participated in any activity?"

If so, and if that activity has a goal set to "Viewed Page B", it logs the conversion for that specific activity and experience.

Even if Page B isn't included as a location in the activity, it doesn’t matter — as long as the URL matches the goal rule and the visitor was previously bucketed into the activity, Target will attribute that view as a conversion.

Thanks.

Pradnya

[KhushbooBh3]

Thanks @pradnya_balvir