I want to use our own user ID to upload gclid, gbclid, wbraid, gbraid into stape store to store for 90 days when users land on site with any of these parameters in the url.
I am struggling with how to set this up so that the stape store only triggers on landing page when parameters are visible. And then i also want to ensure that the values are not overwritten if they already exist in stape store.
Any ideas?
Or any better solutions to store click ids so that we can attach them back onto offline events?
I am struggling with how to set this up so that the stape store only triggers on landing page when parameters are visible.
what is the struggle exactly? your events have common event data parameter called page_location
pull query parameters from it with either some gallery templates or a rudimentary custom one of yours, make a decision i.e. true/false based on their presence
incorporate it into a trigger for your Store Writer
And then i also want to ensure that the values are not overwritten if they already exist in stape store.
you have to make a read call to store to know this, Stape Store Lookup variable is your tool
in the Writer tag, make sure to tick “merge document keys” to account for cases where only SOME parameters are new
this is fairly high-level but answers your question overall
It does work to upload the initial value, but if i for example upload only gclid, and then after fbclid, then the original gclid becomes false, due to merging i would imagine?
