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 missing your point...!!!! 🙂
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
We have hard coded the OneTrust cookie consent manager to the site, and
to be GDPR compliant we have had to use an opt-in methodology, whereby
upon entering the site all cookies are blocked until the user accepts
them. However, this has meant that it looks like the pageview tag is not
firing once the customer accepts all cookies for the first page, it only
fires once someone navigates to a new page. This means we are losing a
heap of single-page visit traffic.How can we get the pageview to fire
...
We use the old JS method of implementing analytics. (I know, we should
be using Launch! But we're not there yet!) 🙂We're creating a new SPA
mini-function on the site, and I need to be able to track each iteration
of the screens. Previously for SPAs we have imported a part of the URL
into the s.pagename, but for this SPA the URL will not change between
screens. Help!?
Hello!So, I need to tag a screen that gives the user multiple choices to
help them choose an insurance product (a help me choose function). One
of them is a whole list of radio button options that they might or might
not choose which are individual elements of particular insurance
products...I want to capture which ones are picked. I also need to be
able to tell if the customer then went on to purchase the insurance
product they will be presented with after using the help me choose
function.List...
I did think of that initially, but becuase the results appear in a
dynamic box attached to the search box as a user types, there isn't
really a need for them to click within the search box. Or do you mean at
point of clicking their chosen search result? I suppose then we'd miss
the opportunity to capture search terms that we don't currently have
content for, but something is better than nothing, right?! Thanks for
the reply.
We are implementing a new real-time site search box on our pages.
Previously we've had a search box where you type a word, press enter (or
the icon) and then the search results appear on a new page. We have used
a prop to collect the search terms and all was well. The new set up will
see users start to type their word, and results will start to appear
based on each key stroke they make, with no need to click enter. We can
change the minimum key strokes to what we want, currently set to 3 I
think...