We are implementing Adobe Analytics using AEP Web SDK. Issue is with the Click rule in Adobe Launch that trigger on a custom event. By the time this rule fires, Data layer on click is getting overwritten by the page load data layer.
For example, click on a breadcrumb from search results page leads to home page. From the website, data layer for breadcrumb click and the home page load sent are different. But by the time Adobe Launch fires the click rule, the data layer for breadcrumb click is getting overwritten by the data layer of home page load and hence page load data is being passed in the click network call.
Expected : Adobe Launch click rule should immediately listen to the click custom event fired from the website and pick the right data layer sent by the website
Please let us know if you have any solution or you need more information on this issue.
Solved! Go to Solution.
Views
Replies
Total Likes
Have you considered using a Direct Call Rule? https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/client/core/overview.htm...
It is possible to pass data to the direct call rule, so this might be an option for you.
Yes, that's generally the experience when trying to track clicks.
One workaround is to use the delay in the Click event. Set it to, say, 500ms.
Agreed. Try the delay in the click event as suggested.
Views
Replies
Total Likes
Thank you both for responding on this issue. We could have added the delay between the custom events fired from the site. But most of the clicks are working fine without having delay. Only few clicks mainly breadcrumb clicks that lead to page load is having this issue.
Views
Replies
Total Likes
That is the fickle nature of front end web interactions. There is so much in play with content on the page, what js might be building the breadcrumbs, are there are factors in play that modify the CSS as the page loads to format the breadcrumbs, etc, etc, etc, etc.
Within add the delay you can restrict it to just be on the links for the breadcrumbs so it's not on all the clicks that don't seem to have this issue.
Views
Replies
Total Likes
Thank you for your response.
There is one limitation of the site where developers cannot control the sequence of the calls made. For example: If a user clicks on breadcrumb which leads to a page load, the page load call can fire first, and then the breadcrumb call can fire. If the developer introduces a delay on page load, it may overwrite the click data layer again and vice versa.
Views
Replies
Total Likes
Have you considered using a Direct Call Rule? https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/client/core/overview.htm...
It is possible to pass data to the direct call rule, so this might be an option for you.
We gave a delay from the website code which resolved this issue. Thanks
Views
Replies
Total Likes
Views
Like
Replies