Google Tag Manager in Nepal should run in the client’s Google account with one container, consistent event names, and QA so GA4 and ad platforms do not double-count conversions.

Why this matters in Nepal

Duplicate GTM snippets are common on WordPress themes. Guide: duplicate GTM. Service: GTM Nepal. Expert: Google Analytics expert.

Minimum event set for SMEs

Page view, form submit, click-to-call, click-to-WhatsApp, and purchase/thank-you where applicable. Full recipes: GA4/GTM conversion recipes.

Suggested event names

Use GA4’s recommended names where one exists, so reports and Google Ads imports work without renaming later.

GTM and GA4 setup for Nepal sites
Event GTM trigger Useful parameters Mark as key event?
generate_lead Form submission or thank-you page view form_name, page_location Yes
click_to_call Click on a link whose URL starts with tel: link_url, page_location Yes
click_whatsapp Click on a link containing wa.me or whatsapp link_url, page_location Yes
purchase Order confirmation page or data layer push value, currency (NPR), transaction_id Yes
file_download GA4 enhanced measurement (no GTM tag needed) file_name Usually no

Keep currency as NPR on every purchase event. Mixed currencies are one of the quickest ways to make revenue reports meaningless.

Step-by-step: a clean container

  1. Create the account in the client’s Google login. The business owns the GTM account; the agency or freelancer is added as a user.
  2. Create one web container for the production domain. Use a separate container (or GTM environments) for staging, never the live one.
  3. Install the snippet once. The <script> goes in the <head> and the <noscript> iframe immediately after <body>. On WordPress, use either the theme’s header field or one plugin, not both.
  4. Remove hard-coded tags. Delete old gtag.js snippets, Facebook pixel code pasted into the theme, and plugin-inserted GA tags once GTM handles them.
  5. Add the Google tag with your GA4 measurement ID, triggered on all pages.
  6. Build the event tags from the table above, using built-in Click and Form variables.
  7. Preview and debug before publishing (see the checklist below).
  8. Publish with a version name and note, for example “v12: added WhatsApp click event”. Version notes are the only audit trail most small teams have.

QA checklist before publishing

  • Tag Assistant preview shows each event firing once per action, not twice.
  • GA4 DebugView shows the events with the expected parameters.
  • View the page source: only one GTM container ID and no leftover gtag.js for the same property.
  • Test on a phone over mobile data, not only office Wi-Fi; slow connections expose tags that fire before the page is ready.
  • Click-to-call and WhatsApp clicks register even when the app opens and the visitor leaves the page.
  • After 24–48 hours, GA4 key events appear in reports and Google Ads shows the imported conversions as “Recording conversions”.

Access and ownership

GTM has two permission levels. At account level, keep the business owner as Administrator. At container level, give agencies Edit or Approve, and keep Publish with someone accountable on the client side, or with a named agency lead under a written agreement. When a contract ends, remove the agency’s users rather than handing over a password.

Common problems on Nepal sites

  • Two containers on one page, usually one from the developer and one from a later agency. Merge them into the client-owned container and remove the other.
  • Theme plus plugin duplicates: Site Kit, an SEO plugin, and a header-scripts plugin can all insert GA4. Pick one route.
  • Developer-owned accounts: the person who built the site leaves and nobody can publish. Transfer ownership while relationships are good.
  • Thank-you pages that can be reached directly (bookmarked or shared), inflating lead counts. Prefer a form-submit trigger or a data layer event.

Detailed fixes for double counting: duplicate GTM and double firing. Ownership in practice: GA4 and GTM container ownership.

Handoff to ads teams

Primary conversion actions in Google Ads must match GA4 events after GTM QA — before scaling Search or PMax. Related: conversion tracking Nepal.

Name the person who may publish, and write that name in the container notes. A container only the developer can publish will drift the next time a festival landing page needs a new button click tracked.

How this fits the stack

More detail on Google Tag Manager Nepal. The full catalog is on Digital marketing stack Nepal. Numbered outcomes live only on case studies.

Next step

Skim the stack hub, then scope work through hire packages or contact.