Overview
While page-load tracking captures the "where," interaction tracking captures the "what." This check focuses on non-page load hits (triggered via s.tl()), such as button clicks, file downloads, or exit links. It ensures that when these interactions occur, the specific data points required for analysis—such as eVar values, props, and events—are actually included in the tag.
Without this check, you may see that an interaction occurred, but you won't know the context (e.g., which button was clicked or what the internal search term was at that moment).
Why it is important
Incorrectly configured interaction events lead to significant gaps in behavioral analysis:
Attribution Loss: If a "Add to Cart" click fails to send the associated eVar for the product ID, you cannot attribute that conversion to the specific product.
Incomplete Funnels: If interaction tags fire but lack the necessary "event" success markers, your conversion funnels will appear broken or under-reported.
Optimization Blindness: Marketing teams cannot perform effective A/B testing or UX optimization if they cannot see the detailed metadata associated with user interactions.
Implementation
Validating interaction events requires more than a simple page scan; it requires mimicking user behavior to trigger the tags.
Action: The platform identifies interactive elements (like CTAs or form submits) and performs a click action.
Logic: Once the interaction occurs, ObservePoint captures the resulting Adobe Analytics tag and validates that the eVars and Prop strings contain the necessary variables defined in your Solution Design Reference (SDR).
Validation: The check fails if required variables do not meet expectation criteria or the tag is missing completely.
Remediation
If interaction hits are missing data or events, review the following technical areas:
1. Configure linkTrackVars and linkTrackEvents
The most common cause of missing data in s.tl() calls is failing to "whitelist" the variables.
In AppMeasurement.js: Ensure that
s.linkTrackVarscontains a comma-separated list of every variable you want to send (e.g.,s.linkTrackVars = "eVar1,prop1,events").Action: If you are sending a success event, ensure
s.linkTrackEventsalso specifies that event (e.g.,s.linkTrackEvents = "event1").
2. Validate "Link Track Delay"
If the interaction navigates the user to a new page too quickly, the browser may cancel the request before the data is sent.
Action: Increase the Link Track Delay in your Adobe Analytics extension settings (typically to 500ms) to give the hit time to exit the browser.
3. Check Variable Scope
Variables set during a page load (s.t()) do not automatically persist to an interaction hit (s.tl()) unless specifically re-set or persisted via a plugin.
Action: Ensure your TMS rules for "Clicks" are explicitly setting the variables required for that specific interaction.
Conclusion
Interaction tracking provides the granular detail needed to understand user intent and conversion friction. By validating that interaction events capture the correct variables, you transform simple click data into actionable business intelligence.
Regular testing via ObservePoint Journeys ensures that your most critical conversion paths—from "Add to Cart" to "Lead Submit"—are always providing the full context required for optimization.