Hunor.digital
Tracking FoundationBuild it right, once.
← Solutions02 · Tracking Foundation

Tracking you can bet on.

A full setup or rebuild of your tracking — dataLayer, events, marketing libraries, and the docs to keep it honest.

1–2 weeksClean property + documentation
or scroll the story

3 of 3 dots are off · tap them

[01]The Situation

Sound familiar?

  • 01

    Every fix so far has been a patch on a patch.

    Nobody remembers why half the tags exist. Deleting one feels like defusing a bomb.

  • 02

    Your events answer nobody's questions.

    Someone set up 'engagement tracking' in 2022. No decision has ever used it.

  • 03

    The platforms can't agree on reality.

    Facebook says 212 purchases. GA4 says 167. Your store says 189. You report whichever one the meeting needs.

  • 04

    Documentation is a person, and they left.

    The setup lives in one ex-contractor's head. You're one Chrome update away from finding out what breaks.

[02]The Turn

I rebuild from the questions down. First: what does the business actually need to know? Then: the exact events, dimensions, and dataLayer architecture that answer it — and nothing that doesn't.

Then I build it, and verify every event against the receiving platform. Not the tag manager preview — the actual destination. If Facebook should see a purchase, I check Facebook.

You get a clean property and documentation your next analyst can actually read. The dependency on me ends at handover, by design.

Tap a card for the honest version
[03]The Work

What actually happens.

Tap through the steps — this is the whole engagement, no hidden phases.

Days 1–2

Business questions become a measurement plan.

We map what you actually need to know — which channels drive profit, what a qualified signup looks like, what the funnel really is. That becomes an event map and a dataLayer spec. You see and approve the plan before any code lands.

Days 3–8

dataLayer, events, and marketing libraries — done cleanly.

The dataLayer implemented to spec. Events, custom dimensions and metrics built to answer the blueprint's questions. Marketing libraries (Facebook, TikTok, Google, LinkedIn, Reddit, Pinterest, Snapchat and friends) implemented properly, wired to consent.

Days 8–10

Every event checked at its destination.

Tag manager previews lie by omission. I verify each event where it lands: the analytics property, the ad platform, the server-side container. What you sign off on is what the platforms actually received.

Final day

Documentation and a walkthrough. You own it.

Event dictionary, dataLayer spec, naming conventions, and the why behind the decisions — written for the next human who touches this, whoever that is. I document the cut-over date too, so before/after comparisons are never ambiguous.

[04]The Outcome

What you keep.

A foundation, not a favor — everything is documented so it outlives our engagement.

  • Full tracking setup or rebuild
  • Event mapping driven by business questions
  • Custom dimensions + custom metrics
  • dataLayer specifications
  • Marketing library implementation (FB, TikTok, Google, LinkedIn, Reddit, Pinterest, Snapchat, +)
  • Server-side tracking add-on available
  • Clean property + full documentation
No funnel, just email

Want the event-naming convention I install?

One email, subject prefilled. I reply with the real thing — no drip sequence, no “resources”.

Email me for it →
[05]The Estimate

€1500 for the full setup or rebuild. Server-side tracking is a separate €1500 add-on, and I'll tell you straight whether you actually need it yet. Plenty of businesses don't, and it's real money.

Tap to narrow your ballpark
0/1 answered

Server-side tracking?

Your ballpark
€1 500–€3 000

The rebuild itself is flat €1500 — the only variable is the server-side add-on.

[06]The Fit

Not for you if…

Pointing you at the wrong engagement costs me the thing this whole brand runs on. So, honestly:

  • You don't know what's broken yet. Start with Clarity — it's cheaper than rebuilding the wrong thing beautifully.

  • You want every metric your platform can produce. I build what answers business questions, not dashboards for their own sake.

  • Your dev team wants to own the implementation. Good — get them the Clarity report instead and let them run with it.

If this isn’t the right sizePartnership

Clean tracking decays without an owner. Partnership keeps it honest, month after month.

[07]Questions

Asked before. Answered straight.

Not required, but usually smart. The audit tells us whether you need a rebuild or a repair — and if it's a repair, you just saved money. If we skip it, the blueprint phase absorbs some of that discovery.

Recovering data lost to ad-blockers and browser privacy features, better match rates for ad platforms, and more control over what leaves your site. If your ad spend is small, the math doesn't work yet — and I'll say so instead of pushing it on you.

A rebuild changes definitions, so before/after comparisons need care. I document the cut-over date and what changed, so nobody ever wonders why March and May disagree.

Analytics: GA4 and its ecosystem, plus server-side containers. Marketing: Facebook, TikTok, Google, LinkedIn, Reddit, Pinterest, Snapchat, and most others with a pixel or an API. If it accepts events, it can be done honestly.

[08]The Call

One honest insight
about your data
even if we never work together.

30 minutes. You talk, I look at your setup live. You leave with one fix worth making. And if we’re not a fit, I’ll tell you that too.

or email me directly →
Or pick a slot right here
Loading slots…