I am following the instructions for Target client-side logging as described here https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/adobe-target/a4t/cl...
After executing the alloy sendEvent, I get a response that has `characteristics.eventToken` but no `characteristics.analyticsToken`.
Is this documentation still valid?
Solved! Go to Solution.
Views
Replies
Total Likes
I found the issue. My Target activity was set up with Reporting Source === Adobe Target rather than Adobe Analytics. I created a new activity with a reporting source of Adobe Analytics and scopeDetails.characteristics.analyticsToken was returned.
@Gaurav_Singh - Do you have any ideas about this?
Views
Replies
Total Likes
Yes the documentation is the latest for webSDK.
Have you applied the code as mentioned in the document here , for Analytics token?
Views
Replies
Total Likes
I did not because the analyticsToken field does not exist in the returned data.
Views
Replies
Total Likes
I added a log of the request and the response in case it helps. (my instance is named 'amalgam'). The experience is being returned and rendered as expected. It's just missing scopeDetails.characteristics.analyticsToken in the response.
Also, below is my Datastream config. Per the docs, I have disabled Adobe Analytics. (FYI, I have tried Datastream configs for no Adobe Analytics, with Disabled AA with report suite and Disabled AA without report suite). None of these configurations are returning the analyticsToken.
Views
Replies
Total Likes
I found the issue. My Target activity was set up with Reporting Source === Adobe Target rather than Adobe Analytics. I created a new activity with a reporting source of Adobe Analytics and scopeDetails.characteristics.analyticsToken was returned.
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies