Skip to main content

GTM Integration SOP

Overview​

  • What: After the client's GA4 property exists, create the client's Google Tag Manager container, publish the GA4 tag through it, and link the client's Search Console property to GA4.
  • When: Client onboarding, immediately after the GA4 Property Creation SOP.
  • Who: Implementation Lead, or an operator signed into the setup@symphonycore.com Chrome profile.
  • Time Required: 30 to 45 minutes, plus DNS lead time for Search Console verification.

Prerequisites​

Procedure​

  1. Create the container. In Tag Manager, signed in as setup@symphonycore.com, create a Web container named after the client's website URL.
  2. Install it on the site. WordPress: paste the container ID into GTM4WP (GTM WordPress Plugin SOP). Other platforms: install the container snippet per the platform's head/body code fields. If installation is blocked, coordinate with the client's web developer.
  3. Add the GA4 tag. Create a Google tag with the Measurement ID from Prerequisites, triggered on All Pages. Do not let any plugin (Rank Math's "Install analytics code", a theme option) add a second GA4 tag.
  4. Validate, then publish. Check in GTM Preview and GA4 DebugView, then publish the container.
  5. Search Console. Run the Google Search Console Property Setup SOP. It is the only verification path: a Domain property under setup@, verified by DNS TXT. Do not use the GA4, GTM, HTML-file or HTML-tag verification methods; each creates a separate URL-prefix property.
  6. Link GSC to GA4. GA4 Admin > Product Links > Search Console Links > Link: choose the Domain property and the web data stream.
  7. Cross-domain tracking, only if the client's journey spans domains: configure the domains in the GA4 tag's Configure your domains setting.

Verification​

  • GTM Preview shows the GA4 tag firing on page view on the live domain.
  • GA4 Realtime shows your own visit within a few minutes.
  • GA4 Admin > Product Links > Search Console Links lists the Domain property.
  • Exactly one GA4 collect request per page view in the browser's Network tab (no double tagging).
  • Full validation follows in the GTM and GA4 Validation SOP.

Revision History​

DateVersionChange
2026-10-311.1Restructured to the SOP standard (Overview, Prerequisites, Procedure, Verification). Duplicate in-body metadata block and placeholder reviewer removed. Flowchart corrected: SC creates GA4, not the client. GSC summary removed in favour of the GSC SOP, including the SearchAtlas /sitemap.xml instruction and the GA4/HTML-file verification fallbacks. Title matched to the filename
2026-02-051.0Initial draft