AD0-E409 · Question #92
A marketer has set up an Experience Targeting activity for their regional website targeting users from that region using Target's Geo Targeting. After setting up the test the marketer has shared the…
The correct answer is C. The activity is created using a different at_property than the regional website. D. The activity is created using "URL is" under page delivery options in VEC. C and D are correct because they represent configuration mismatches that prevent QA URL delivery regardless of audience overrides. C - Adobe Target uses at_property tokens to scope activities to specific properties (websites, apps). If the activity was built under a different…
Question
A marketer has set up an Experience Targeting activity for their regional website targeting users from that region using Target's Geo Targeting. After setting up the test the marketer has shared the Activity QA URL with the business stakeholders which looks like Mi8Fn4sfdKGAJyg5DsJ3XxNj67A&at_preview_index=1_2&at_preview_listed_activities_only=tru e&at_pr eview_evaluate_as_true_audience_ids=2161154 However, the stakeholders are not able to see the experience using the QA URLs. What are two possible reasons the activity is not seen in QA? (Choose two.)
Options
- AThe users are not located in the region for which the activity has been created.
- BThe users are using the Company's VPN that is changing their actual location.
- CThe activity is created using a different at_property than the regional website.
- DThe activity is created using "URL is" under page delivery options in VEC.
How the community answered
(34 responses)- A9% (3)
- B21% (7)
- C71% (24)
Explanation
C and D are correct because they represent configuration mismatches that prevent QA URL delivery regardless of audience overrides.
C - Adobe Target uses at_property tokens to scope activities to specific properties (websites, apps). If the activity was built under a different property than the one deployed on the regional website, Target will not serve the activity there, even with a valid QA URL, because the property context simply doesn't match.
D - Selecting "URL is" in VEC page delivery creates an exact URL match rule. The QA URL appends multiple preview parameters (at_preview_index, at_preview_evaluate_as_true_audience_ids, etc.), making the full URL different from the original page URL. This exact-match check fails before the preview logic even runs, so the activity is never delivered.
A is wrong because QA URLs are specifically designed to bypass audience conditions - the at_preview_evaluate_as_true_audience_ids parameter in the URL forces the geo audience to evaluate as true, so physical location is irrelevant in QA mode.
B is wrong for the same reason: a VPN altering geolocation doesn't matter since the QA URL's audience override parameter (evaluate_as_true_audience_ids) already neutralizes geo-targeting checks.
Memory tip: Remember "P + U = Proof-breakers" - Property mismatch and URL exact-match are the two delivery-layer issues that block QA before audience logic ever runs, making them invisible to audience overrides.
Topics
Community Discussion
No community discussion yet for this question.