Events firing before consent update

  • angelofoodaloo

    (@angelofoodaloo)


    8 months, 1 week ago

    Hi,

    I’m reaching out regarding an issue I’m experiencing with the GTM4WP plugin on my WordPress site.

    I’ve manually installed the Google Tag Manager container snippet in the website’s code (not using the GTM4WP option to inject the container), and I’m using Iubenda as the CMP. The Iubenda team confirmed that their banner is blocking scripts correctly until user consent is given.

    However, I’m still experiencing a critical issue: some key events, such as purchase and begin_checkout, are firing before the consent update is processed. This results in consent being reported as denied, by not activating the relevant tags for Google ADS (Purchased and Start of payment procedure).

    Could you please advise on how to delay these events until after the consent update?

    Thank you for your help,

    Angelo

Viewing 2 replies - 1 through 2 (of 2 total)
  • Giovanni Sonego

    (@gsonego)

    8 months, 1 week ago

    I’ve a similar problem.

    I have an ecommerce site built with WordPress and WooCommerce. It uses the GTM4WP plugin. Consent mode is implemented using Legalblink, a CMP that I’m told is accredited.

    I’ve often encountered the following issues:

    1. Purchase and other events were not tracked in GA4 (they were completely missing).
    2. Purchase events were not properly tracked in Google Ads conversions. Sometimes they were missing entirely, other times the purchase amount was missing.

    When analyzing the flow of events using Tag Assistant, I notice that the “purchase” event appears in the left column BEFORE the “Consent Update” event. I believe this could be causing problems because all consent values are still set to “not granted” at that point.

    How can I change the order or delay the “purchase” event? Or is it possible to make the “Consent Update” happen earlier?

    Giovanni Sonego

    (@gsonego)

    7 months, 3 weeks ago

    Why is no one answering? Is it possible that only me and Angelo have this problem? Is there anyone who can help us? Should we wait for the new version? What other options do we have?

    Many thanks Giovanni

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Events firing before consent update’ is closed to new replies.