An Architect has defined the following tracking specifications:
* A userlD variable must be set in the data layer
* The userlD value must be mapped to eVar5
* The userlD value must be used as the Adobe visitor identification method.
The tagging engineer confirms that Adobe Launch is configured as requested.
An Analyst notices that the eVar5 report is not being populated.
The Architect can see that the userlD data object is populated in the data layer after the page loads.
What is causing this problem?
To track website usage without visitors seeing which data points are being collected, the recommended approach is to send tracking calls server-side via the Data Insertion API. This method allows for the collection of page names, form names, a counter event for each page of the checkout flow, and the s.products variable while keeping the tracking logic and data points hidden from the client side.
Brice
1 months agoReuben
2 days agoTwanna
13 days agoLynna
20 days agoDion
1 months agoAyesha
2 days agoAlison
3 days agoTerrilyn
20 days agoRicki
23 days agoPok
2 months agoLouvenia
13 days agoDerrick
26 days agoReynalda
2 months agoLynelle
18 days agoMaryrose
21 days agoShonda
1 months agoAntione
1 months agoColene
2 months agoEva
2 months agoWalker
2 months ago