Hi, our company recently switched from old Adobe tracking to the new Experience Platform Web SDK. We followed the steps mentioned on Adobe's documentation and configured XDM schema and datstream. There were no issues with the set-up, however after mapping all our Pops, eVars and events when we tried to QA the tracking we found out in Adobe Experience Platform Debugger there are number of props, eVars and events missing out the values.
The network section shows the same missing values.
As per Adobe's documentations in "console" with command _satelite.setdebug(true) this can be done and we were able to track all the missing values from the debugger and we are also able to track all the data in Adobe Analytics workspace but this method would be a lengthy process for our QA team as they previously relied on Adobe Experience Platform Debugger.
Any suggestions on how to troubleshoot this error?
Solved! Go to Solution.
You can also further click on the "hit" in the upstream to check what data exactly was received by Adobe Analytics and stored in Data Feed format. Since the availability of AEP Assurance, it is the prefered way to QA tracking for me than the old browser plugin.
Views
Replies
Total Likes
Hi @ruchit0622
There are few avenues to pursue here:-
Hope this answers your question.
Thanks
Madhan
Hi Madan,
We have done all the above mentioned steps but we are still missing the data in the network calls
I see, there could be an issue with the server-side forwarding of data from Adobe Experience Platform to Adobe Analytics then. Make sure your edge configurations and server-side forwarding are correctly configured. Did you check this ? Also if some of your events rely on user interaction or delayed scripts, they might be trying to fire before the necessary data is available. In this case, you may need to adjust the timing or sequence of your scripts.
Let me know.
I will check this and let you know Thank you Madan
@ruchit0622 did you check this?
Views
Replies
Total Likes
Hi @adobechat we did check that there is no issue with configuration either
Views
Replies
Total Likes
Then its most likely a problem with your Javascript.
Views
Replies
Total Likes
Did you try to use Edge Transaction in the debugger to monitor how tracking going through the client/edge/upstream
Hi @leocwlau yes i did check the edge transaction and found no issues on tracking
Views
Replies
Total Likes
You can also further click on the "hit" in the upstream to check what data exactly was received by Adobe Analytics and stored in Data Feed format. Since the availability of AEP Assurance, it is the prefered way to QA tracking for me than the old browser plugin.
Views
Replies
Total Likes
Hi @leocwlau Thank you, I can try to QA using this technique
Views
Replies
Total Likes
Views
Likes
Replies