Fathom Analytics is installed and tracking traffic.
Tested with submitting an existing form
Tested by creating a brand new Ninja Forms form after Fathom Analytics Conversion plugin installation and still no luck after submitting a form.
Ninja Forms integration is enabled from settings.
Tracking for logged in users enabled
Tested also in incognito, with trackers & ads not disabled in browser
Tested with a completely separate mobile browser

Tested with WordPress 6.6.2, Ninja Forms 3.8.18 and Divi Theme.

We use the current version 1.20.x and we have carried out a test with customer data that can be sent to Google for conversion tracking.
(order data checkbox in GTM4WP settings screen)

We noticed that the zip code is not transmitted the way the user enters it in the checkout.
For example, if we enter a German postal code in a test order, GTM4WP will not transmit the 0 as the first digit to Google.

e.g. “06114” becomes “6114” in the dataLayer.
That’s wrong.

In addition, the zip code is transmitted as an integer. I assume that string would be better as a data type.
Because there are countries in which letters are also possible in a postal code. e.g. France.

If we process the conversion and remarketing tags via the server container, then conversion/remarketing tracking will not work. E.g. for the “purchase” event.

The problem is that GTM4WP fires the “purchase” event directly when the page is accessed.

However, the Tag Manager does not need to be fully loaded at this point.
With a classic tag manager setup, this is not a problem.
However, this doesn’t work with server side tagging.

The GTM container must be loaded when the “purchase” event is sent.
Then it works.

As a solution we tried the following approach.
It works for us.

// duracelltomi-google-tag-manager/public/frontend.php, ~ line 1254:


$js_script_inline= "document.addEventListener('wfa-google-tag-manager/page-view', (e) => {
  $datalayer_push_code
}, {once: true});";
		

wp_add_inline_script( 'gtm4wp-additional-datalayer-pushes', $js_script_inline, 'after' );

“wfa-google-tag-manager/page-view” is a custom event that we fire via custom HTML Snippet when GTM is ready. And GTM4WP’s inline frontend JS code will only be executed when our GTM container is ready.

If GTM4WP listens to this event and only then fires the “purchase” event, then server side conversion tracking works.

It would be good if GTM4WP had a plugin option where you could store a JS event name. If filled in, then wait for this event before sending events.

add_action('wp_head', function(){
?>
<script>document.addEventListener('<?php echo esc_js( $plguin_settings["event_name"] ); ?>', ()=> gtm4wp_woocommerce_process_inline_js_events(), {once:true});</script>
<?php
}, 1);

gtm4wp_woocommerce_process_inline_js_events() calls the inline script loaded at the end of body tag.

Something like that. It’s just a rough draft now.

What do you think about it?

Maybe all tracking-relevant scripts should simply wait until the event has taken place. Use data-src instead of src for GTM4WP scripts. When the event occurs, set src and all scripts will be executed + the associated events will be sent to the GTM container. Would probably be functional too?!

First of all thank you for developing this plugin, it’s really useful.

The latest version 2.22 seems to block the Google Ads conversion events tracking, so even if we still have Google Analytics v4 tracking working for those who accept the cookies, we don’t have anymore the conversion tracking.

Disabling the plugin fixes the issue.

The issue started right after we’ve updated to v2.22, so I’ve now reverted to v2.21 and I will update this post tomorrow after we see if the conversions are showing up again.

Meanwhile can you please check or advise on how to fix this with the latest version or is there an issue with the update ?

Thank you.

PS: I’ve just seen this mention in the settings “If you enable Google Consent Mode v2, consent will be denied intil the visitor accepts marketing cookies. If you do not enable Google Consent Mode v2, consent will always be denied.” so if I’m understanding correctly this option is disabled on my setup and it might affect the ads tracking, this is the first time I’m seeing it and the plugin has been installed for a while now. How did the v2.22 affected this setting, or was it neglected and now enforced ? if that’s the case it’s possible that there are other users that might be affected by the fact that this option was disabled by default for older installs.

If needed, can you use All Pages trigger or should you use Complianz’s own triggers?

I am trying to find the Plugin option on the backend of the page for one of my clients, but the backend interface seems completely different and I can’t seem to find any of the options that I am used to. No Plugin options, no ability to install extensions as the installation fails etc.

The main issue I want to solve, is set up a Google Ads conversion tracking snippet, but I can’t even find where to put it. Is it possible that the interface has changed completely from what I remember, or could it be that I am missing some permissions?

Thank you