3 Easy Steps To Test Server-Side Universal Analytics/GA4 and Facebook Conversion API

Google Tag Manager was founded with the aim of making marketers' tasks more manageable. You no longer need to request tracking pixels from developers and wait for the next update to see your tracking in action if you utilize the Google Tag Manager web container.

Server-side, the philosophy and technology behind server side tagging are entirely different from what we used to have on the web. Google Tag Manager tagging is more involved than web container setup, at least for now. However, server side tagging will enhance your website significantly.

With its ability to follow people who use AdBlockers, browsers with ITPs, and other tracking restrictions, server-side tagging is becoming increasingly common. Even tag managers such as MagicPixel can come in handy in this regard.

This article is not meant to urge you to use server-side tagging (there is another blog post that describes the main benefits of server-side tracking). I suppose you've already decided to employ server-side tagging on your website. This new article will show you how to check if your Universal Analytics, GA4, and Facebook conversion API Server-Side tracking is set up correctly.

Checking server-side tagging in Tag Manager server container debug mode, Facebook event testing tool, and developers tool inside your browser will be covered. Let us begin.

Inside your browser, you'll find a Facebook event testing tool as well as a developers tool.

To confirm that your tags are triggering when they should, I recommend starting with the Tag Manager preview and debug mode. The GTM (Google Tag Manager server-side) debug tool will show you which tags and events have been added to the site, as well as whether or not they have been fired on specific pages/triggers.

The tag management server containers' debug mode works similarly to the

web debugger. Merely go to the upper right corner and select the preview option. Then, on each page, click the button or carry out the activities that were set up in the server component.

Back to the Tag Manager debugger and double-check that the dataLayer received all necessary variables, as well as whatever tags and events were triggered. Then, we can proceed to the next phase if everything is in order.

You'll need to go further into the developer's zone to guarantee that requests are sent from a specific tagging URL. Again, developer tools for Chrome or Safari are necessary here (you can use other browsers as well).

Verify that base code and Facebook events are occurring correctly using the GTM server debug tool.

The same procedure applies to testing Facebook server-side tracking as it does for Google Analytics. You must be absolutely sure that events are triggered by the correct triggers. Start the GTM debug tool, go to your site's pages, and check the events you would like to test. Check the results in the Tag Manager debugger tab once you've finished.

The Facebook conversion API testing tool

Click on Test Events in your Facebook business manager's events manager. You'll see a test event code in Google Tag Manager that you should attach to our Facebook Tag. You may test Facebook server events in real-time with this code.

After adding a test ID, go to your site and perform actions that will cause your Facebook events to be triggered. Then, return to the Facebook testing tool and look at the events that appear.

It is important that marketers focus on what landed them a lead, form submission, sale or enquiry. Without this marketing attribution, there is no way they can realize the impact of their marketing strategies.​ ​

With MagicPixel, you can now get comprehensive insights and details on what channel is giving you the best ROI. ​

Book A Demo https://insights.magicpixel.io/