Track landing page view in Google Analytics

Hi @markpollak,

This should work. Accepting ‘statistics’ as a category should fire an event called cmplz_event_statistics.

This should then fire the tag related to the trigger.

If you have cmplz_event_statistics as only trigger, and only when it ‘equals’ this specific custom event I think it might be the tag itself.

Could you add the configurations of both as screenshots to this forum?

regards Aert

Thanks for the reply.

I’m pretty sure it is set up correctly as the google analytics page view tag is firing once the accept button is clicked – i.e. from the second page onwards

The Tagbird extension also shows that when the accept button is clicked, the ‘cmplz_event_statistics’ is fired but the google page view is not. Clicking onto another page on the site again fires the ‘cmplz_event_statistics’ and this time the pageview google analytics tag is fired.

This is also reflected when I look at Google Analytics in real time mode – the first page visited isn’t recorded when the user clicks the ‘accept’ button but future pages are. I’d be grateful if you could get to the bottom of this as I don’t want to underreport website visitors.

Sorry – links to screenshots below

View post on imgur.com

View post on imgur.com

View post on imgur.com

Hi @markpollak,

I’ve created a sandbox environment with the exact Tag Manager / GA4 tag configuration as displayed in your screenshot, but this issue does not seem to occur on my end, the pageview fires directly after providing consent. You can see the example site here: https://gtmtest.us7.instawp.xyz/

To narrow down the potential causes of this, a good starting point would be to use the Health Check & Troubleshooting plugin to start a temporary ‘testing session’ where only the Complianz plugin has been activated. That would allow you to verify whether the problem still occurs after all other plugins have been deactivated.

If the issue is resolved upon doing so, you’ll know that another plugin is related to the behavior. You can then start enabling plugins one-by-one until the issue re-appears, at which point you will know the plugin that causes it.

Kind regards,
Jarno

// RESOLVED //
Thanks for your help – I have been pulling my hair out over this and found the reason why. MAybe this will help someone else in the future …

The reason in the end was down to a separate Plausible analytics script which I’d totally forgotten I had installed. The reason it was hard to find was that during development, I also tried out Cloudflare’s Zaraz tool which is basically Clooudflare’s version of Google Tag Manager. I used Zaraz to instaall the Plausible Analytics script which is why it was not apparent it was firing. It was only when looking down the network tab that I saw a reference to ‘plausible.io’ script being loade.

Anyway, for some reason which I don’t know why (and at this point really don’t care! ) this plausible setup was blocking the first firing of the pageview Google Analytics tag described in my post above.

Many thanks for all your help again – it is a great plugin

• This reply was modified 2 years, 9 months ago by markpollak.

Hi @markpollak,

Glad to hear you managed to solve this already, thanks a lot for sharing the solution with us as well!

If we can provide any further assistance, feel free to reach out once more.

Kind regards,
Jarno