Implementation, Data Collection, and Tagging
What this domain tests
How data actually gets collected. Concepts: Adobe Experience Platform Tags (formerly Launch), rules, data elements, extensions, the Analytics beacon, s.t() vs. s.tl() behavior, link tracking, and the page-view vs. event distinction. Know that s.t() fires a page view and increments page views; s.tl() (or s.tl(true,'o',...)) sends a custom/exit link without a page view. Understand eVars vs. props (conversion vs. traffic), events, and how the AppMeasurement library sends data.
Traps to watch for
- Using
s.t()for a click that should not count as a page view - inflates page views. - Assuming props persist; they are hit-level unless otherwise configured, while eVars can persist via allocation/expiration settings.
- Forgetting that a tag rule needs a condition, an action, and often a data element mapping.
- Confusing client-side tagging with server-side forwarding.
Worked example
A "Download brochure" button should be tracked as a custom link. Correct: call s.tl(this,'d','Brochure Download') with an event, so page views stay clean and the download is attributed to the current page. Using s.t() here would create a phantom page view and skew bounce and pathing reports.
Rule of thumb
Ask "is this a new page load?" If yes, s.t(); if no, s.tl(). Every tracked interaction should map to a variable in the SDR.