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.
I have a situation where I need to reference different paths of the data
object depending on what event type is being collected. The structure of
the data object loosely follows the old W3C data layer spec where there
is product information held in product[*] for "product views", in
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 disabl...
I am following the instructions for Target client-side logging as
After executing the alloy sendEvent, I get a response that has
`characteristics.eventToken` but ...
You could use the Reactor API https://developer.adobelaunch.com/api/# to
do this. The problem is that the learning curve is a bit steep unless
you're already up on the development techniques involved. Let's say that
you could do this manually to 2000 rules at 15 seconds per rule. You'd
spend about e...
Yep, I assume that doing a new build and publishing to production
(Publishing workflow in Launch) will resolve the issue. Do you have a
person who normally does this job? If so, speak with them. If not, let
me know and I'll see if I can help out. There is a slight chance that
your Launch library is ...
The Data Layer Manager extension will support this use case. As long as
the pushed event has an "event" key, DLM will work just fine.