It is usually not missing data, but the lack of a single definition of an order. These are the three situations we see most often. A campaign that learns from a picture missing about 40% of events shifts budget every month towards the channel that looks effective, and keeps doing so for as long as nobody puts those numbers side by side.
Ad blockers, browser restrictions and missing consent take away part of the events on the way. Campaigns then learn from a picture in which every third order is missing.
Google Ads counts a sale after a click, Meta also after a mere view, and the ERP holds the number you actually invoice. Three attribution models give three totals, and none of them is a mistake.
The report shows revenue, not margin after product cost and returns. The decision to scale is then made on a number that does not say how much is left.
Not every store needs the top level. The table shows what each level includes and when it pays to move up.
| What you get | Level 1: order in GA4 | Level 2: server-side tracking | Level 3: data with margin |
|---|---|---|---|
| E-commerce events and funnel | ✓ | ✓ | ✓ |
| Consent and Google Consent Mode | ✓ | ✓ | ✓ |
| Resilience to ad blockers and browser limits | – | ✓ | only with level 2 |
| Conversions sent to campaigns from the server | – | ✓ | only with level 2 |
| Product cost and returns in the report | – | – | ✓ |
| One source for Google Ads, Meta and the store | – | partly | ✓ |
| When it makes sense | every store | ad budget from around €1,000 a month | when you decide on scaling |
It does not say that the third level contains the second. A data warehouse and server-side tracking solve two different problems: the warehouse tells you how much is left after product cost and returns, while server-side tracking makes sure the ad channels see the order at all. You buy them separately and we quote them separately.
The order is not accidental. Google and Meta come in the first phase of every implementation, TikTok fits within the standard setup scope, and the last two systems are a separate job.
Events for the whole purchase path, conversions and audiences. Every implementation starts here.
A container in the browser and on the server, Google Consent Mode and cross-domain tracking. It goes hand in hand with GA4.
The pixel plus conversions sent from the server, so Meta campaigns learn from the full picture, not from whatever the browser lets through.
Within the standard setup scope, on the same terms as Meta: events go to TikTok from the server.
We implement it, but outside the basic scope. It is a separate analytics job, quoted after we check how many events need to be moved.
Same as Pinterest: we do it, but as an additional job, not within the price of the environment setup.
PrestaShop is our specialisation and the platform we implement tracking on most often. We cover the other systems in the same scope, within the price of the environment setup.
Our specialisation: Premium GTM, Pixel Plus with Conversions API, the product feed and modules other systems do not have. We quote it separately, because PrestaShop takes a different amount of work.
E-commerce tracking on WordPress: events for the whole purchase path, consent and conversions sent to campaigns.
Websites and landing pages without a store, where the conversion is a form or a phone call. The same Tag Manager, different events.
Tracking on a Polish off-the-shelf SaaS platform, within the limits its template layer allows. We name that limit before quoting.
E-commerce events and server-side conversions, together with the restrictions Shopify places on scripts in the checkout.
Closed systems and in-house applications. We plug events in where the platform allows it and send the rest from the server.
Four stages. The first is a separate service and you can stop there.
1-2 weeks
We compare GA4 events with orders in the store and in the ERP, and check consent, campaign conversions and the Google Tag Manager setup. You get a list of discrepancies together with their causes.
2-3 weeks
Order in GA4 and Tag Manager, e-commerce events, Consent Mode, connection to Google Ads and Meta. From €250 net, depending on the starting point; a PrestaShop store is quoted separately.
3-4 weeks
A server-side container, conversions sent from the server and tests of consistency with the panels. A one-off implementation followed by a monthly maintenance fee, both quoted individually.
ongoing
Profit Analytics: data from campaigns, the store and the ERP in one view, with product cost and returns. A one-off implementation followed by a monthly fee plus the cost of the cloud.
Web analytics is the one service whose effect you cannot judge on your own: the numbers after our work look different from before, and you have to trust that the new ones are closer to the truth. Trust in the contractor weighs more here than in any other item of the price list. These are the ratings clients have given the agency on three platforms, with a link to each profile.
weighted average of 224 reviews across three platforms. Clients gave them, and each site links to the profile with the full text of every review.
Read the reviewsAnalytics becomes useful only once you know why the ad panel shows a different number from the report. These are the statuses that let us ask the platforms themselves about the cause, instead of guessing from inside the tool.
A gap between the ad panel and the report is the most common reason nobody in the company trusts the numbers. For that kind of diagnosis we have support on Google's side and access to features before their launch.
The same order comes back to Meta from the browser and from the server, and the pixel has to treat it as one. The partner status shows us whether deduplication really works, which the regular panel does not tell you.
Analytics that does not change budget decisions is a report, not a tool. This ranking is based on exactly such decisions, made on client accounts, not on the quality of presentations.
A form enquiry is a conversion only once the CRM confirms something came of it. The team certification covers closing the tracking loop on the sales side, not only on the website.
Three levels, each available separately. Prices are net, plus the cost of external tools, which we give you before the start and which you pay directly to the providers.
Order in GA4 and Google Tag Manager, e-commerce events and consent.
A server-side container and conversions sent from the server.
Campaigns, the store and the ERP in one view, together with margin and returns.
| Scope | Setup | Server-side | Margin report |
|---|---|---|---|
| Audit of current tracking | ✓ | ✓ | ✓ |
| GA4, Tag Manager, e-commerce events | ✓ | ✓ | ✓ |
| Consent banner and Google Consent Mode | ✓ | ✓ | ✓ |
| Server-side container | – | ✓ | ✓ |
| Conversions sent from the server | – | ✓ | ✓ |
| Product cost and returns in the report | – | – | ✓ |
| Dashboard for the board | – | – | ✓ |
| Tracking monitoring after implementation | optional | optional | optional |
The call is led by a new business specialist. When we get into the details of an account, the specialist for that channel joins in. We reply within one business day.
Before the meeting we review your website, your visibility and what your campaigns show from the outside. We will not open with “so, what does your company do?”.
The reply comes from the same new business specialist who will run the call. No qualification form and no call from an unknown number.
We go through your numbers and your questions. If it turns out we are not the right fit, we will tell you straight away.
