Hi Pratheep,Thanks for taking the time to respond. Unfortunately, we do not use Launch for our implementation (yet), it's hardcoded. Is there a way around this issue for our rather archaic implementation method?Claire

I'm setting up an XT on our checkout which is built on React. My XT changes a bit of copy that appears on every page, so I'm adding additional pages to the experience. I have included to include the base URL in the page delivery for the first page in the experience. I've experimented with the first ...

Thank you, that nailed it

Thanks - but what about returning customers who once had the at=ps6260 query string param but on their next visit it isn't present anymore - will this still account for them?

Hi! I am trying to create an audience for an XT which includes a profile script. The audience will show a certain menu to users who visit the site with ?att=ps6260 as a parameter in their URL, and the profile script needs to then serve the same experience to users who return to the site but this tim...

Hey! I think the image explains my question....my pages reports do not match up with my fallout report data. The first page is always the same, then it differs dramatically. No segments have been applied, this is just basic data.  

Thank you so much for taking the time to respond to me here!!!!!! So because AA is hardcoded and doesn't touch GTM, would the GTM trigger still be relevant for that? It's given me a great idea for the remarketing pixels that we use, but I can't see how it would help the AA issue, but I might be miss...

Well. Our AA implementation is hardcoded Javascript, and we've also hard coded the OneTrust code. We do use GTM for our marketing pixels...

Aah, cool. Probably not possible without Launch then?!Thanks for the reply!

Hi jamesb37349107,We are having a similar issue, although not using Launch, whereby OneTrust is blocking first page tracking upon acceptance of cookies. Did you get round your issue? If so, do you have any insights to share?Cheers,Claire