What Checks Should You Run After Installing GTM on Your Website?
Installing Google Tag Manager (GTM) does not end with adding the code to your site. Once it is in place, you need to make sure every tag, trigger and data flow is working correctly.
Google Tag Manager (GTM) installation does not end with adding the code to your site. Once it is in place, you need to make sure every tag, trigger and data flow is working correctly. Here are the essential checks to run after a successful GTM installation.
What Should You Check After Installing GTM?
Think of post-installation checks as a "health scan". By following the steps below in full, you can prevent data loss and reporting errors.
What Items Belong on a Post-Installation GTM Checklist?
1. Verify That the GTM Container Code Is Placed Correctly
Make sure the GTM code has been added in full to both the <head> and the <body>. Verify it from the browser console or with the "GTM Tag Assistant" extension.
2. Check for Duplicate Tags
If your site has both GTM and manually added GA4 code, your data will be counted twice. Make sure the manual code has been removed and that data is sent through a single tag in GTM only.
3. Test Your Tags with GTM Preview Mode
Open GTM's Preview mode and simulate every tag's firing conditions (triggers) as a real user would. Confirm that the tags appear under "Tags Fired".
4. Check the GA4 Tag and Measurement ID
Verify that the Measurement ID in the GA4 tag (G-XXXXXXXXXX) matches the one in your GA4 property. A wrong ID sends your data to an entirely different account.
5. Check the Live Data Flow in the GA4 Realtime Report
In the GA4 panel, go to Reports > Realtime. As you browse the site, check whether the data lands there in real time.
6. Test Your Google Ads Conversion Tags
"Google Ads Conversion Tracking" Make sure these tags fire and that the Conversion ID and Label values are correct. Test on conversion pages in particular.
7. Check Consent Mode and the Cookie Consent Flow
Test that GTM stops the tags when a user declines cookies and fires them again when consent is given. Verify that Consent Mode signals are sent as denied or granted.
8. Check Cross-Domain Tracking and Referrals
Check whether sessions break when users move from your site to payment pages (iyzico, PayTR, etc.). Remember to add payment providers to the "Referral Exclusion" list.
9. Test Critical User Journeys End to End
Complete the product view, add to cart and checkout steps as a real user would, and observe whether the purchase event and its values are passed to GA4 correctly.
10. Establish a Pre- and Post-Release Check Process
Keep a "GTM Version" record after every change. Build the habit of running a system where you can roll back to the previous version within seconds after a faulty release.
The Most Common Post-Installation GTM Check Mistakes
Testing only a single page: Missing errors on the site's other pages (blog, contact, etc.).
Relying only on the Realtime report instead of DebugView: DebugView gives you far more detailed debugging data.
Not testing in an incognito window: The browser cache can make a faulty installation look like it is working.
Ignoring Consent Mode: Trying to send data before the consent flow works breaks legal compliance.
Frequently Asked Questions
What is the surest way to tell that my GTM installation is working?
Use GTM Preview mode to inspect the "Data Layer" contents, then confirm on the GA4 DebugView screen that the same events appear with the correct parameters.
My tags are firing but I don't see data in GA4 — what is wrong?
The most common reasons are a mistyped Measurement ID or the 24-48 hours Google Ads needs to process the data not having passed yet.
Do I have to publish live after every change?
No — use GTM Preview mode to test changes in your own browser only, and publish with "Submit" once you are confident.