Google Tag Manager & GA4 Setup | SNS
SNS Team · Reviewed 4 November 2026
When an ad platform and the website tell different stories, first inspect the conversion definitions and implementation. SNS helps configure and review Google Tag Manager, Google Analytics 4 and conversion tracking around the website, existing tools and permissions available.
Installing GTM is not a measurement plan
Google Tag Manager manages tags, triggers and variables. GA4 receives events and supports reporting. Having a script installed does not prove that successful enquiries or purchases are recorded correctly; the customer journey needs an explicit event definition and test.
What can the scope include?
- Inventory of existing tags and installation methods.
- An event plan tied to the commercial objective.
- WhatsApp click and successful form-submission measurement.
- Ecommerce events, transaction identifiers, value and currency where available.
- Tests for duplicate events and relevant failure or cancellation scenarios.
- Documented configuration in accounts owned by your business.
A click is not a qualified lead
A WhatsApp click indicates an attempt to open a conversation, not a confirmed chat or sale. A submit-button click is different from a successful form submission. Recorded orders and collected revenue also need separate definitions. Reports should preserve these distinctions.
How the review works
- Agree the actual conversion and sales source of truth.
- Identify direct tags, plugins or GTM containers sending overlapping events.
- Run test journeys and inspect event parameters and errors.
- Document expected versus observed behaviour and the required corrections.
Questions before implementation
Do I need GTM if GA4 already works?
Not necessarily. We review the current setup before recommending migration. Adding another installation without resolving overlap can duplicate measurement.
Will GA4 and Meta report identical totals?
That is not a reasonable promise. Attribution windows, event definitions, consent, devices and collection methods can differ. The objective is to explain differences and correct implementation faults, not force reports to match.
What access is required?
We identify task-specific permissions and work in your accounts. Do not send passwords through the enquiry form. Data-layer development, server-side tagging and custom integrations are separately scoped where required.
Reference documentation
Share your website, platform and an example of the measurement issue without credentials. Where tracking is sound but outcomes remain weak, connect the findings to Media Buying or a Growth Diagnostic. Fees, timing and any development dependencies are agreed before paid work begins.