An Architect has defined the following tracking specifications: • A userlD variable must be set in the data layer • The userlD value must be mapped…

The issue is a race condition. The Adobe Launch rule that sends the page view beacon (containing eVar5 and visitorID) is likely firing before the userID value is populated into the data layer. The prompt states the userID is populated after the page loads, which is typically after the Launch "Page Bottom" or "DOM Ready" event has already triggered the rule. For the userID to be correctly captured as the visitorID and in eVar5 on the initial page view hit, it must be available in the data layer before or at the moment the rule executes.

A. This is inaccurately worded. visitorID is an Adobe variable, not a data layer object. The userID from the data layer is what is unavailable.
B. The method of population (dynamic variables vs. direct mapping) is irrelevant if the source data layer variable is empty at the time of execution.
C. Similar to option B, the method of populating eVar5 is not the root cause; the problem is the unavailability of the source userID value.

1. Adobe Experience League. (n.d.). visitorID. "This variable must be set before the s.t() function call. If you set this variable, you must also set trackingServer." This highlights the timing requirement.

2. Adobe Experience League. (n.d.). Rule events. In Adobe Launch, rules are triggered by events like "Library Loaded (Page Top)" or "DOM Ready". If a data layer variable is populated asynchronously after these events, the rule will execute with an undefined value for that variable.

3. Adobe Experience League. (n.d.). Data elements. "When a rule runs, it retrieves the current value of the data element. If a data element's value is not yet available... it can result in the data element being set to an empty or incorrect value in that rule."