Your Adobe Target QA link may hide other live activities

A reviewer opens a link for one experiment and suddenly the rest of the personalized page looks ordinary. The team may treat that screenshot as evidence that live activities stopped. An Experience League question points to the less obvious explanation: the Activity QA link's option to show default content for other activities.

Read the QA settings before the screenshot

Adobe's Activity QA documentation describes the option and the persistence of QA mode. Record the exact QA URL, target activity, experience, environment and the state of “Show default content for all other activities.” A reviewer who keeps a QA session open can keep seeing behavior that differs from an ordinary visitor.

Compare with a clean visitor session

Test the same page in a fresh session without the QA parameter, then in the intended QA experience. Inspect the Target response in both. Do not change audiences or deactivate activities until the behavior is reproduced outside QA mode. For Web SDK implementations, follow Adobe's documented QA URL or bookmarklet method rather than assuming a legacy cookie behaves the same way.

Put context on review links

Send reviewers the expected scope with every QA link: which activity is forced, whether other activities should show default content, and how to exit QA mode. The acceptance screenshot should include that context. Otherwise a correct isolated test can be mistaken for a broken combined experience.

Adovo’s view

A review link is a test instrument, not a neutral browser session. It changes the thing being observed. The team should make that change explicit before anyone calls the production experience broken.