I'm trying to implement Analytics in a new site. I have copied over the Launch library from one of my other sites where it is working well however in the new site when I trigger an SDK call, the dataObject is not being populated...
If I look at the dataObject data element, it is also empty, which leads me to believe the Update Variable action in my Launch rule is not working
However, this is identical to the rule that is working fine on my other site. I've tried modifying it, even deleting out all custom code and only using the standard wizard but no dice...
Anyone got any ideas what the problem is?
Solved! Go to Solution.
Views
Replies
Total Likes
Never mind, I raised a ticket with Adobe Support and they advised that it is a known bug. The workaround, which worked for me is:
You need to create a copy of the data element referenced in the rule and update the rule to use the new data element. This should resolve the issue. Alternatively, if you revert to the previous data element, it should generate an ID for it, which will also work.
Here’s a video explaining the bug and the workaround:
https://www.youtube.com/watch?v=oMVDbsgJyf0
Views
Replies
Total Likes
Hi @darrin_lim
can you maybe post a screenshot of your Web SDK sendEvent action to be sure the data element is referenced?
Also, have you made sure the data element is included in the library and the referenced other data elements as well? Especially when you copied the Launch property they must be initially added in your new property to be included in the build.
Also, your data object may only be filled during the page view rule and not return anything outside of it.
i would start with some console logs in your page view rule, trying to figure out which parts are missing tbh, after you've verified that all data elements are included in the build
Views
Replies
Total Likes
Never mind, I raised a ticket with Adobe Support and they advised that it is a known bug. The workaround, which worked for me is:
You need to create a copy of the data element referenced in the rule and update the rule to use the new data element. This should resolve the issue. Alternatively, if you revert to the previous data element, it should generate an ID for it, which will also work.
Here’s a video explaining the bug and the workaround:
https://www.youtube.com/watch?v=oMVDbsgJyf0
Views
Replies
Total Likes