Analytics and tracking — Nepal

GA4 and tracking setupyou can actually trust

Soft Himalaya configures GA4, Google Tag Manager, conversion tracking and reporting from Kathmandu for businesses in Nepal, the UK, Australia, the USA and Canada.

  • Conversions defined before any tag is published
  • Every event verified in the live property
  • Accounts created in your name, access removable
What we report
Analytics dashboard displayed on a computer screen

Define before measuring

A written measurement plan keeps conversion definitions consistent across GA4, ads and reporting.

Analytics workspace photograph; displayed figures are not client reporting.
Measurement plan first
We agree what each event means and why it matters before a single tag is published.
Consent respected
Tags fire according to the consent your visitors give, and the setup reflects the rules of your markets.
Verified, not assumed
Every event is tested in preview and in the live property before it is called done.
Documented and owned
The plan, the container and the accounts are yours, with naming written down so future changes stay consistent.

What we set up

Tracking that reflects your actual business

A default install tells you page views. A useful setup tells you which enquiries, sign-ups or orders came from where — which requires deciding what counts as a conversion first.

GA4 property setup

Property, data streams, internal traffic filters, retention settings and cross-domain configuration.

Google Tag Manager

A structured container with clear naming, versioned publishing and no orphaned legacy tags.

Conversion and event tracking

Form submissions, calls, downloads, sign-ups and the other actions you actually judge success by.

E-commerce tracking

Product views, cart actions, checkout steps and purchases with revenue values passed correctly.

Server-side tagging

A server container where accuracy, page speed or data control justifies the added setup and hosting cost.

Consent configuration

Consent Mode and banner integration so tags respect the choice a visitor makes.

Ads and pixel setup

Google Ads conversions, Meta pixel and conversions API, with deduplication between browser and server events.

Dashboards and reporting

Looker Studio reports built on your data, answering the questions you actually ask each month.

Tracking audit and repair

A review of an existing setup: duplicate tags, broken conversions, misattributed traffic and missing events.

Why it matters

Bad data is worse than no data

A dashboard everyone quietly distrusts still gets used to make decisions. Getting the definitions and the implementation right is what makes the numbers worth acting on.

  • Define the conversion first

    If nobody has agreed what counts as a lead, two reports will disagree and both will be defended. The measurement plan settles it before implementation.

  • Defaults measure the wrong thing

    Out-of-the-box GA4 counts scrolls and outbound clicks as engagement. Left alone, it flatters reports without telling you anything you can act on.

  • Attribution is an estimate

    Ad blockers, consent refusals, cross-device journeys and platform models mean channel numbers are directional, not exact. We report them that way.

  • Setups drift

    Site redesigns, new forms and platform changes break tags quietly. Tracking needs occasional checking, not a one-time install.

How we work

Plan it, tag it, verify it

Setup time depends on the size of the site, whether e-commerce is involved and how much access and developer support is available for changes on your side.

  1. 01

    Goals and questions

    We start with the decisions you want the data to support, and the questions you currently cannot answer.

  2. 02

    Measurement plan

    Events, parameters, naming conventions and conversion definitions are written down and agreed before implementation.

  3. 03

    Implementation

    GA4, Tag Manager and any advertising tags are configured, with data layer changes specified for your developers where needed.

  4. 04

    Testing and debugging

    Every event is checked in preview mode, in real time and in the reports, including on mobile and through the consent banner.

  5. 05

    Reporting setup

    Explorations and Looker Studio views are built so the questions from stage one can be answered without exporting spreadsheets.

  6. 06

    Handover and review

    The plan and container documentation are handed over, with a check after a few weeks of real data to catch anything the tests missed.

Reporting

What a dashboard should answer

Rather than showing invented traffic charts, these are the four questions a reporting setup exists to answer. If a dashboard cannot answer them, it is decoration.

Where did people come from?

Channel, campaign and landing page for the visits that produced an outcome, not just the ones that produced traffic.

Where do they drop off?

The steps between arrival and conversion, so you can see which stage is losing people.

What did it produce?

Enquiries, sign-ups or revenue attributed as accurately as the platform honestly allows.

Is the data still trustworthy?

Checks that show when tracking has broken — a conversion that suddenly stopped is usually a tag, not the market.

Properties, containers and advertising accounts are created in your name, so the history and the access remain yours.

Tools

What we work in

Everything is configured inside your own accounts, with our access added as a user and removable at any time.

  • Google Analytics 4

    Events, conversions and reporting

  • Google Tag Manager

    Web and server-side containers

  • Looker Studio

    Dashboards built on your connected data

  • BigQuery export

    Raw event data where deeper analysis is needed

  • Google Search Console

    Organic queries and index coverage

  • Ads and Meta tools

    Conversion imports and the conversions API

Data quality

What tracking can and cannot tell you

Being clear about the limits is what makes the rest of the numbers usable. These are the caveats we put in front of any report rather than at the bottom of it.

Not everyone is counted

Ad blockers, privacy browsers and declined consent mean analytics undercounts visits. Totals are a floor, not a census.

Journeys cross devices

Someone can research on a phone and buy on a laptop. Without a login, those look like two unrelated people.

Platforms disagree

Meta, Google Ads and GA4 use different attribution windows and models, so their conversion counts will never match exactly.

Consent changes the picture

Where consent is required, the data reflects the visitors who agreed. Modelling can estimate the rest but does not replace it.

Project estimates

Scope first, then price

Cost depends on the size of the site, how many conversions and events are in scope, whether e-commerce or server-side tagging is involved, and how much developer support your side can provide.

Core tracking setup

GA4 and Tag Manager configured properly with the conversions that matter to a service business.

  • Measurement plan
  • GA4 and GTM configuration
  • Key conversion events
  • Verification and handover

E-commerce or campaign tracking

Full purchase tracking with advertising platforms connected and deduplicated.

  • E-commerce event set
  • Ads and Meta conversions
  • Consent configuration
  • Looker Studio dashboard

Audit or server-side setup

Repairing an existing setup, or moving measurement server-side for accuracy and control.

  • Full tracking audit
  • Server container setup
  • Data layer specification
  • Documentation and training

Questions

Frequently asked questions

Common questions about GA4, Tag Manager, consent, data accuracy and how tracking work is quoted.

GA4 is Google's current analytics platform. It records activity as events rather than sessions, which makes it flexible but also means a default install measures very little of value until the events that matter to your business are defined and configured.

Working together

A clear measurement relationship

We do not publish anonymous client quotes or screenshots of traffic growth that cannot be verified. These are the standards we hold ourselves to instead.

You own the accounts

GA4 properties, Tag Manager containers and advertising accounts are created under your business, with our access removable.

Definitions written down

What counts as a conversion, and how each event is named and triggered, is documented rather than left implicit.

Verified before handover

Events are confirmed in preview, in real-time reporting and in the live property — including through the consent banner.

Limits stated up front

Where the data is an estimate, we say so in the report rather than presenting modelled figures as measured ones.

Start a project

Tell us what youneed to measure

Send your website address, the actions you count as a conversion and whether GA4 or Tag Manager is already in place. We will reply with questions, a suggested scope and an estimate.

This opens your email client with the details filled in. Please do not include sensitive information.