We have created one Event Based listing impression rule in our React JS based single page application. On initial page load, this event based listing impression rule is getting fired 2 times. We checked and verified that Data Layer digitalData object is being prepared properly and is signally properly with unique random ID change each time and make a signal for DTM to pull request. When user search from homepage and thus navigating to search result page, at this time this listing impression rule is getting fired only one time.This issue of twice call is happening when direct search page URL is being hit in browser address bar. Not able to understand why this rule getting fired two times. Any help regarding this would be appreciated.
My name is Dejan and I am one of the technical consultant investigating the aboven mentioned issue.
What I would like to correct from the original post is:
The rule only fires once, so the rule isn't the issue. We have added console logs to the rule to make sure that part is indeed firing only once.
However for example in an incognito window, the first tag that should fire. Shows twice in different debug tools. But when you look under the "network" tab the call is only made once. So we have a feeling that this is a malfunction between the debug tools such as Adobe Analytics debugger plugin and the calls actually made.
Also we looked into the fact where we would segment on visitors that only have had 1 visit, to see what the bounce rate is. Which you would expect to be 0% if it actually was making calls double. This isn't however the case.
The tag that is on top, is the one that gets fired first. So if we would change the alphabatic order of the tags, the one on top would show "twice" according to the debug tools.
We also found this article regarding the above explained issue:
Our conclusion in this story currently is that all is working as intended. Do you agree?
When I look at the page using an incognito browser and the steps provided, I'm seeing two requests in the network tab for that call. The first is a 302 redirect which is used to set the s_vi cookie. The second is the 200 which is the actual beacon being sent to Analytics. This is expected behavior and shouldn't be viewed as a duplicate beacon.
If I understand your test correctly, you are correct. Having a bounce rate of grater than 0% proves that there is not a duplicate beacon on that page. If there were a duplicate beacon, it would be near impossible to have a grater than 0% bounce rate because every visitor would have at least two beacons.
Hopefully, this answers your question. Please let me know if you still have concerns.
When I load your page using the method you mentioned, I'm seeing 4 different server calls. I've highlighted the difference in the first two call since you indicated they were duplicates:
Do you have a rule that set's the Unique ID?
Here is a list of the rules that I show as firing on the page:
|Rule Name||Rule Type||Fired?||Other Info|
|0AA: page load||Event Based||yes||dataelementchange(Page id change)|
|AA: listing impressions||Event Based||yes||dataelementchange(Page id change)|
|AA: search result page||Event Based||yes||dataelementchange(Page id change)|
I assume one of these rules or somewhere in the Analytics tool itself, you have code setting the unique ID.
Hope this helps,
Please find the steps and URL as under-mentioned :
This issue seems not only in incognito mode, but also in normal chrome window. In case if you are not able to generate this in normal chrome window, you can try with incognito mode of chrome to reproduce the issue.
Do you have a URL and steps where I might be able to replicate this? It's hard to give more than just general advice without testing the page myself.
Yes, It is DTM rule (AA: listing impressions) which is getting fired 2 times. This rule(AA: listing impressions) is an Even Based Rule having top order, means this set on top first sequence of all rules defined. When search result page is being hit directly in browser, this rule gets fired twice. If I set any other rule (for e.g. AA: page load) at top order with first place sequence, then the this rule(AA: page load) gets fired two times. Means, any case, the first order rule we set, is getting fired two times. I don't know what's going on? You mentioned about default beacon, but I have actually no idea about that? But I had searched to suppress default beacon, and I have already applied adding code 'return false' in Customize Page Code section in general common DTM settings as mentioned in below links :
Still, the issue is same and first DTM EBR is getting fired two times.
Can you please help me out what could be the solution of my issue?
Are you sure it's the event based rule getting fired twice and not the default beacon or a page load rule being fired? Have you turned on debug mode in DTM and viewed the console messages to know which rules are firing?