-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible race condition when dataTagGetData from 2 rapidly fired data layer events #28
Comments
Hi, Thanks for the issue. I think a workaround for this should be in gtm.uniqueEventId. But this needs to be tested. I added this bug to our backlog. |
Hi thanks, this is what I attempted and tested, but then I realised that it seems the only way to get the uniqueEventId is by using copyFromDataLayer, which still suffers from the race condition. Any ideas? template.js
data-tag.js
|
Sorry for now, no better ideas. Thanks for your input. |
At the moment, when marking "add_data_layer" to true on the Data Tag, the following function is called in browser window to retrieve the latest dataLayer data. However, if one has 2 of the same event firing in rapid succession in the client, the Data Tag is always only able to grab the latest dataLayer data of the second event. Resulting in a race condition. Any suggestions on how to solve this? For now I must unpack the dataLayer data on the client-side and send it as an event or user property.
The text was updated successfully, but these errors were encountered: