Free tool
Tracking ROI calculator
Manual tracking QA eats hours at every release, and unnoticed tag breakages steer your ad budget with wrong data. Put your own numbers on it.
Your manual QA cost
Deploys, CMS changes, new campaigns: anything that can break a tag.
The manual recette: re-testing events, tags and the data layer by hand.
Analyst, agency or freelance day rate, brought back to the hour.
Optional: ad budget at risk
If you run paid campaigns, estimate what rides on your conversion data when a tag breaks between two QA passes. This is an exposure, not a cost, so it is shown separately.
Budget optimised on the conversions your tracking reports.
Your estimate of conversions lost, duplicated or misattributed between two QA passes.
Cost of manual tracking QA
€17,280
per year spent on the manual recette: real time, real payroll or agency fees
- Hours of manual recette
- 288 h/year
- At €60/hour
- €17,280
Ad budget at risk
€24,000
per year optimised on wrong conversion data if tracking breaks and goes unnoticed. An exposure, not a cost: it is not added to the figure above.
The estimate is computed entirely from your inputs, in your browser. Nothing is sent to our servers.
Where the money actually goes
Broken tracking costs advertisers twice. First in time: every release needs a manual recette where someone re-tests events, tags and the data layer by hand. Then in budget: between two QA passes, a tag that stops firing or fires twice keeps feeding wrong conversion data to GA4, Google Ads and Meta, and your bidding optimises on it.
- Manual QA scales with your release rhythm: the more you ship, the more hours it burns.
- Tracking breakages are silent: nothing crashes, the data just quietly turns wrong.
- Ad platforms keep optimising either way: they learn from whatever conversions you send.
- Reporting built on broken data leads to wrong budget decisions long after the bug is fixed.
- Continuous automated QA turns the recette from a recurring project into a report you review.
Frequently asked questions
- What is tracking QA (recette)?
- Every time your site ships a release, someone has to re-test the tracking: open the pages, fire the events, check the data layer, confirm each tag still sends the right hits to GA4, Google Ads, Meta and the CMP. That manual test pass is what French analytics teams call the recette, and it has to be repeated at every release.
- How does broken tracking waste ad spend?
- Ad platforms optimise bidding on the conversions you send them. When a purchase or lead event fires twice, stops firing, or loses parameters, the algorithms learn from wrong data and your budget is steered by it. The longer the breakage goes unnoticed, the more spend is allocated on bad signals.
- How accurate is this estimate?
- It is exactly as accurate as your inputs: the calculator does transparent arithmetic on the numbers you set (releases, hours, hourly cost, ad spend, affected conversions) and nothing else. Adjust the sliders to match your reality and the result follows.
- How does Tag Insight reduce this cost?
- Tag Insight runs your tracking QA continuously and automatically: every tag, event and data layer push is checked against your tagging plan, and you get an alert the moment something breaks or duplicates. The manual recette pass shrinks to reviewing a report, and breakages stop living unnoticed between releases.