Data Collection

Bad data doesn't improve further down the line.

If tracking is incomplete, duplicated or simply wrong, the problem follows the data into your dashboards, analysis, marketing platforms and business decisions.

So we start by working out what you need to measure. Then we make sure the right information is available across your websites and apps, and reaches the platforms that need it.

dc-hero

A selection of our clients

Why do my GA4 conversions not match my back end?

 

A gap of 5% to 30% between platform-reported conversions and actual orders is common. But just because it happens to most companies doesn’t mean you need to accept it. We have the tools and the experts you need to know what's causing the difference. Let’s use them. Four issues usually account for discrepancies between Google Analytics and internal reports:

 

Consent

Visitors who decline analytics or marketing cookies can still buy, without showing up in your reports.

Ad blockers and browser restrictions

Browsers and blocking tools can stop tracking requests before they reach your analytics platform.

Tagging errors

Missing, duplicated or misconfigured tags change conversion counts and other key metrics.

Conversions outside the website

Orders by phone, offline or through back-office processes land in your business systems, outside your web analytics.

What our monitoring finds at clients

Duplicate transactions

The same order counted twice, so campaigns look better than they are and budget follows the wrong signal.

Personal data in URLs

Email addresses or names in page URLs end up in GA4, against the GDPR and Google's own policies.

Broken campaign tags

Faulty UTM parameters send sales to the wrong channel, and your attribution with them.

Negative revenue

Transactions with a negative value. At one client, following them up uncovered fraud.

What is a data layer, and why do I need one?

A structured way to hand information from your website or app to the tools that need it.

Say someone buys a pair of shoes. Your data layer makes the product, price, transaction value and other details available in one consistent format. Your tag manager then sends the right information to platforms such as GA4.

Without a data layer, those tools pull information straight from page elements. That works until a website update moves the information, and your tracking quietly starts looking in the wrong place.

So first we define the events, interactions and business outcomes that matter to you, and what the data layer needs to provide for each. A Solution Design Reference gives your development and analytics teams one shared specification to work from. Personal data stays out of it.

Get the foundations right, and every future change is easier to manage. Every platform downstream receives the same clean events.

Any tag manager

Google Tag Manager, Tealium iQ or Ensighten. The design of your data layer stays the same; only the way events are pushed differs.

Apps too

Native, hybrid and progressive web apps. The design then also covers the Firebase SDK and your app events.

1: Design first

What needs to be measured? Which events and conversions matter? What does the data layer need to provide? The tags follow from those answers.

2: Then we implement

We fit tracking into your development team's existing sprints, either as specialist support or by managing the configuration ourselves.

3: and we keep watching

Websites change and releases introduce errors. Monitoring after go-live catches broken tracking before it turns into months of questionable data.

How long does a GA4 implementation take?

Six to twelve weeks for a typical implementation.

It depends on the number of properties, your measurement requirements and the technical complexity of your site.

Already live? Find out where you stand.

Start with an audit, then keep watch every day.

An audit shows what to fix first. Monitoring makes sure it stays fixed when your site changes.

Data collection audit

One score for your current setup.
49 checks on your Google Tag Manager container across eight areas, and 24 on your data layer. Security findings are reported first, ahead of the score, so you fix a leak before you tidy a container.

DataLayer monitor

Your data layer, checked after every release.
A new release can drop an event or rename a variable without anyone noticing. The monitor spots it and alerts your team, before the gap shows up in a report.

GA4 Monitor

200+ checks on GA4, every day.
Data quality, e-commerce values, campaign tagging and access rights, plus AI-based detection of personal data across 39 countries. Thresholds are tuned to your setup, so you only hear about what matters.

How an international brand kept 85% consent after adding a reject-all button

 Cloud Nine Digital made the website's consent signals measurable and connected them to the client's marketing data. The client could see in advance what a new cookie banner would do to its numbers, tested variants and kept acceptance at 85%.

Let's find out where the numbers went wrong

 If your reporting and business data don't match, we'll trace the problem back through the collection setup and work out what needs to change. 

 

2026-06-02 DIGITAL MARKETING FESTIVAL 0041
Contact details

Cloud Nine Digital
Johann Siegerstraat 24
1096 BH
Amsterdam, Netherlands

T: +3120 787 13 2397

E: info@cloudninedigital.nl


Need something else?

Please do reach out. We are happy to help!