Data Tag + Client: Property Pollution Across Events

[daveb]

Hey all, hopefully something simple to solve but I’m out of ideas.

We have the Stape Data Tag sending client-side custom events up to ssGTM where they are received by the Stape Data Client (Template). By the time the Data Client emits the event in ssGTM it has mixed up properties between events, even adding in GTM-specific values that aren’t related to our custom events at all.

I can see that the Data Tag’s outgoing request does contain the incorrect properties, but in the GTM Debugger the variable values are undefined at the time the tag fires:

Any idea what could be causing the Data Tag to pick up and send incorrect values?

As this is my first post, I can only post a single attachment in my initial post, so I will follow up with some comments.

[daveb]

Here’s an example of an onboarding_completed event sent client side. Everything looks good:

[daveb]

Detail from above:

[daveb]

But by the time it arrives server-side, it has acquired some properties not related to the event at all:

[daveb]

In fact, those properties appear to be from the following event, called display_content and the Window Loaded built-in event, which is never sent by the Data Tag:

[daveb]

More detail on the above:

[daveb]

Finally, I can see that the Data Tag’s outgoing request does contain the incorrect properties, but in the GTM Debugger the variable values are undefined at the time the tag fires:

[daveb]

Undefined values at time of send:

[Dan]

Hi @daveb looks very weird, thanks for brining this up

1. do you have the latest gallery version of the Data Tag? I believe you don’t

2. Would it be possible for you to share this container with me for review? Or perhaps send me an export of it?

[daveb]

Thanks for the reply, @Dan.

You’re right, I don’t have the latest version:

Happy to share the container with you. I’ll DM it to you now.

DB

[daveb]

Sorry, looks like we can’t DM here. What’s the best way to share it with you?

[Dan]

@daveb just share to dan@stape.io, would want Edit rights please. Thx

[daveb]

Done. Let me know if you haven’t received it.

You’re welcome to test the site and create a test account on staging. You should find the main domain in the container and the staging site is https://staging.app.[sitename].com/.

[Dan]

thank you kindly.

I believe the culprit here is Send all from DataLayer option that is checked in your Data Tags.

I tested this on the Login flow (where, it seems there’s no display content firing after start_onboarding, at least not on stagin). And I don’t see anything extra added to the request, but then I went ahead and added a DL push on the same trigger - and voila a parameter I pushed in that new event gets added to the original hit - you can see leftovers of this experiment in a separate workspace I’ve created.

so for a quick fix: disable ‘send all from dataLayer’ and map the data explicitly (if/where needed)

for a more convenient fix, you have to wait till we do some adjustments to the template and v8.js snippet. cc @giovaniortolani

I also do recommend, regardless of this issue, that you update your DT template AND Data Client template in the server container.

p.s. the issue is clear, you can revoke my container access. thx!

[daveb]

Thanks so much for taking a look, @Dan.

I wasn’t able to post the below a couple of days ago due to my account being new, but we’ve since chatted a bit on email. I’ll post the final resolution here for others to be able to find.

We have quite a variety of events so the “send all from dataLayer” is very appealing and we’d love it if it did work as expected. In the meantime we can explicitly map each event and property.

Do you have any ETA on the update?