Services
Measurement that agrees with the till.
If Analytics says one number, the eshop says another and Google Ads says a third, no decision made on them is really a decision. We put the measurement in the code, with consent, so there is one number that holds.
What you get
GA4 set up for your business
Events and conversions that match what actually counts — an order, an enquiry, a phone call — rather than the defaults that switch themselves on and measure scrolling.
Server-side tagging
Events leave from your server, not only from the browser. They survive ad blockers and Safari's cookie limits, and nobody can forge them from the browser's developer tools.
Consent Mode v2 & cookie banner
A banner that asks for real consent, and measurement that respects the answer. Without consent no identifier leaves; with it, the data is complete and lawful.
Conversions API for Google and Meta
The platforms receive conversions from the server, with identifiers weakened where they must be. Campaigns optimise towards sales that happened, not towards whatever the browser managed to send.
Reconciled against the till
We compare events with real orders and account for the gap: double counting, payments lost on a redirect, cancellations nobody was subtracting.
One report anyone will read
A single view of the numbers you decide on: cost per order by channel, what sold, what did not. Not twenty charts nobody opens.
How we work
Tracking is code, not configuration
Most of what breaks in measurement breaks on the site: a button renamed, a checkout step added, a thank-you page that no longer loads. No setting inside Analytics catches that.
So we put it in the code, alongside the feature it measures. It then breaks only when the feature itself breaks — which means we see it immediately.
Consent is not an obstacle to measuring
Banners that hide “reject” or assume consent are not only unlawful; they also produce dirty data, because the platforms now read consent signals and adjust to them.
With Consent Mode done properly you get complete data from those who accepted and modelled data from the rest, without sending identifiers you are not allowed to send. It is also the only setup that can be described honestly in a privacy policy.
One number, not four
Google Ads, Meta, GA4 and the eshop will always report slightly differently — they measure different things and attribute differently. The problem is not the difference; it is nobody knowing why it exists.
We name which number is the truth — almost always orders in the eshop — and explain what each other one shows and how far it drifts. After that, decisions are made on one thing.
The data is yours
GA4, Tag Manager, Merchant Center and the ad platform accounts are opened in your name. We take access; we do not become the owner.
It is common for a business to discover its own history belongs to its previous agency. Not here: if we leave, we leave without your data.
Process
Mapping
Two hours with you, one week in your data. It ends in a written account of what is wrong.
Plan & price
Scope, timeline and cost per layer. No open-ended invoices.
Build
We work in weekly cycles. You get a staging environment from week one.
Maintenance
Monitoring, updates, a monthly report and one person who knows your project.
Fit
A good fit
- Eshops where Analytics and the till disagree and nobody knows which to believe.
- Anyone spending on campaigns who cannot say what an order cost by channel.
- Anyone running a cookie banner from a plugin with no idea whether it measures correctly or lawfully.
Not a good fit
- Anyone who wants to track people without consent. We will not build it, and we will say why.
- Sites with no traffic or campaigns yet: there is no decision to support.
- Anyone who wants a monthly report full of charts and nothing to change because of it.
Questions
What is server-side tagging, plainly?
Instead of the visitor's browser sending events straight to Google or Meta, your server sends them. A browser can block or lose them; a server does not. The result is more complete, more reliable data — and far more control over what exactly leaves.
Will a proper cookie banner cost me data?
From people who refuse, yes — as it should. But with Consent Mode done properly Google models part of that back, and the data from those who accept is complete rather than half-broken. Most accounts we take over were measuring less before.
Can you work with my existing GA4?
Yes. We start by auditing what is measured today and what does not hold up, and usually repair rather than rebuild — the history has value.
Do I need a separate server?
Not necessarily. Server-side tagging runs alongside the site on platforms like the one we already use, with no machine for you to maintain. If your current infrastructure cannot carry it, we will tell you what that costs.
What does it cost?
Setup is priced once and ongoing monitoring separately. Ask for a quote below and you get a written price for your setup within one working day.
Quote
What would it cost you?
Every business is priced on its own numbers. Tell us yours in a minute and get a written offer, not a price list.
Quote request
- A person reads every request and writes the offer. Nothing is sent automatically.
- Ad budgets are separate: you pay Google, Meta or OpenAI directly, from your own card.
- No calls unless you ask for one.
Related
- Conversion rate optimisationCRO for Greek eshops and sites: where people drop out, speed, checkout, and changes measured in orders rather than clicks.
- Google AdsGoogle Ads management on tracking we build ourselves: Search, Performance Max and Shopping, budget reviewed weekly, reported in sales rather than clicks.
- SEOTechnical SEO and content for Greek businesses: indexing, Core Web Vitals, structured data, Greek keyword research. We make the changes in the code ourselves.