Skip to main content
TrackingConsulting
Now booking · 2–4 day turnaround

Broken after redesign · Conversion tracking

Recover 40–80% of your Broken after redesign ad revenue.

Done-for-you 1st-party server-side tracking on Meta, Google, TikTok and Microsoft. Built in 2–4 days. You own the entire stack. No monthly SaaS fees.

✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.

Built in 2–4 daysOne-time fee95% accuracy guaranteed400-day cookie lifetime1st-party server-side

Built on — and certified for — the platforms that matter

Stape

Pro Partner

Meta

Tech Provider

Google

Tag Manager

TikTok

Events API

Microsoft

UET Partner

LinkedIn

CAPI Partner

Pinterest

CAPI Partner

Built on the same partner stack used by enterprise DTC brands.

Ariful Islam — Founder, Tracking Consulting

Meet your consultant

Ariful Islam

Founder · 8+ years in paid media & tracking

Verified earnings

$200K+

earned on Upwork

Top Rated Plus
4.9/5 · 300+

Verify the receipts

You work directly with Arif — no SDR, no account manager.

By the numbers

No fake testimonials. Just the math.

70+

Platforms supported

Shopify · Woo · Magento · BigCommerce · 65 more

8+ / 10

Meta EMQ guaranteed

in writing — keep working free until hit

2–4d

Build to live

accurate data flowing within 7 days

$0

Monthly fees, ever

one-time fixed price · you own the stack

400d

Cookie lifetime

max RFC 6265bis allows · 57× Safari ITP

9

Ad channels covered

Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X

95%+

Tracking accuracy

verified vs Stripe · GA4 · ad-platform reports

30 min

Free founder call

no SDR · no pitch deck · written remediation plan

Numbers from realistic engagements. Your specific recovery depends on your iOS share, ad-blocker rate, and current setup — we’ll quantify it on the call.

Real clients · real videos · real outcomes

Don’t take our word for it. Watch the receipts.

Founders, marketers, and agency owners describing the before-and-after of their Broken after redesign tracking rebuild — in their own words, on camera.

The problem

What a redesign actually breaks

Broken after redesign-specific issues
Leak #01

The thank-you page URL changed

Triggers keyed to /order-confirmation or /thank-you stop matching the new path, and every conversion tag depending on that URL silently stops firing. No error appears in GTM, in Ads, or anywhere else.

Leak #02

The new theme renamed its dataLayer keys

It pushes productId where the old one pushed item_id, or nests the ecommerce object a level deeper. Variables resolve to undefined and events go out with empty value and currency — firing, but carrying nothing.

Leak #03

It's a SPA now, and pageviews stopped after the first load

React, Next or a headless storefront changes routes without a page load. If History Change triggers were never added, every step after the landing page is invisible, including the entire checkout.

Leak #04

The replatform changed your product IDs

New SKUs or variant IDs in purchase events no longer match the Merchant Center feed or the Meta catalog, so dynamic remarketing shows unmatched items and your value-based audiences quietly empty out.

Who this is for

Honest about who we’re a fit for.

We don’t take every project. Here’s how to tell if we’re right for you.

Good fit

You’re a great fit if…

  • You run Broken after redesign (or are migrating to it)
  • You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
  • Your reported ROAS doesn’t match what your bank account is saying
  • You want to own your tracking stack — no monthly SaaS fees forever
  • You have 2–4 days to do this once and never think about it again
Not a fit

Skip us if…

  • You spend less than $500/month on paid ads (browser pixel is fine)
  • You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
  • You need attribution modeling — we fix the data foundation, not multi-touch reports
  • You want a 6-month enterprise consulting engagement (we ship in 4 days)
  • You expect us to manage your ad accounts (we don’t — that’s a different service)

If you’re still unsure, book the call anyway — we’ll tell you straight whether we can help.

Our position

If your reported ROAS disagrees with your bank account, you don’t have an attribution problem. You have a data foundation problem. No SaaS dashboard fixes that — only a rebuilt 1st-party server-side stack does.

Ariful Islam — Founder
The outcome

What changes once the new site is tagged for what it actually is

Conversions come back from the pages that now exist

Server-side

Triggers rebuilt against the new routes, the new confirmation flow and the SPA's history events, so purchase and lead fire from the real steps instead of from URLs that were retired at launch.

No double counting from the snippet the old theme left

8+ EMQ

Hardcoded gtag or pixel code that survived the migration gets removed, or deduplicated against GTM by transaction ID, so you stop reading two of everything and calling it growth.

Catalog and feed line back up

Deduped

Item IDs in your events matched to the new feed IDs, checked in the diagnostics panel, so dynamic ads have products to show and value-based audiences repopulate.

A spec that survives the next redesign

Backend-verified

The dataLayer contract written down and handed to your developers, so the next theme update is a pre-launch checklist item rather than a week of nobody noticing.

The full transformation report

Before vs after — built in 2–4 days, accurate data within 7 days

We deliver the 1st-party server-side stack in 2–4 business days. Each metric below measured 7 days pre-launch vs 7 days post-launch using your own ad-platform reports + Stripe + GA4. No 30-day waiting game.

Attribution accuracy

  • Reported ROAS vs Stripe match
    Before60% (35% drift)
    After95%+ match
  • iOS conversion match rate
    Before~58%
    After~92%
  • Cross-domain click-ID retention
    Before~40%
    After~95%
  • Server-attributed conversions
    Before0%
    After100%

Audience quality

  • Meta Event Match Quality
    Before4.5 / 10
    After8+ / 10
  • Cookie lifetime (Safari)
    Before7 days (ITP cap)
    After400 days (max allowed)
  • Lookalike seed-list size
    BeforeShrinking as signal decays
    AfterRebuilt from server-side matches
  • Identity match params sent
    Before1–2 (email maybe)
    After9 (email · phone · IP · UA · click_id · etc.)
  • Retargeting list health
    BeforeDecaying
    AfterCompounding

Bidding performance

  • Smart Bidding stability
    BeforeRetraining weekly
    AfterLocked-in
  • CPA trend
    BeforeDrifts up as signal degrades
    AfterBidding learns from complete data
  • ROAS variance week-over-week
    Before±35%
    After±5%
  • Conversion volume Meta sees
    Before65%
    After95%+

Compliance & ownership

  • GDPR / CCPA audit-ready
    BeforeWeak
    AfterAudit-clean
  • Consent Mode v2 wiring
    BeforeNot configured
    AfterFully wired + verified
  • 3rd-party cookie deprecation ready
    BeforeNo
    AfterYes
  • Data ownership
    BeforeVendor-locked
    After100% yours

Server-side

money events from your backend

8+ / 10

Meta EMQ guaranteed

95%+

tracking accuracy

A typical engagement

The shape of a typical Broken after redesign rebuild

We’re not going to invent a fake testimonial here. Instead — here’s the realistic pattern of what happens, anonymized but accurate to engagements we ship.

Day 0 — They arrive

A 7-figure Broken after redesign store spending ~$25K/month on Meta. Reported ROAS shows 4.1× in Ads Manager. Their bookkeeper’s number says 2.6×. The founder doesn’t know which is real, so they keep doubling down on what looks like a winning campaign — except cash flow tells a different story.

Day 1 — Audit

We screen-share. Within 20 minutes we’ve found the leaks: native pixel firing twice on iOS, CAPI dedup using the wrong event_id (Meta is double-counting), GA4 showing 38% (not set), and the Customer Events API never enabled. The 1.5× ROAS gap explains itself.

Day 2–3 — Build

Server-side GTM container goes live on data.theirstore.com. Meta CAPI rebuilt with full advanced matching. Google Enhanced Conversions wired. TikTok Events API turned on. All event_ids deterministic. iOS recovered.

Day 4 — Launch

Live-fire test purchases through every funnel step. Meta Event Match Quality goes from 4.5 to 8.7 — verified live in Events Manager. They get a Notion runbook + Loom walkthrough so their dev team can extend it.

Day 5–7 — Accuracy

Conversion data starts flowing cleanly. Day 7: reported ROAS reads 2.8× (matches Stripe within 5%). Lookalike audiences grow because Meta finally has clean seed data. Their CAC dashboard makes sense for the first time in a year.

Day 30 — The math compounds

Smart Bidding has 30 days of clean signal. CPA drops 18%. They scale Meta budget 40% because they finally trust the data. Net new revenue from the recovered tracking: roughly $14K/mo above what they were getting before.

Numbers above are realistic averages from engagements we’ve shipped. Your specific recovery depends on your iOS share, ad-blocker rate, and current setup — we’ll quantify it on the call.

The cookie window unlock

400-day cookie lifetime — the longest your browser allows

Default Broken after redesign setups put cookies on a 7–30 day timer. Safari ITP caps client-set cookies at 7 days. That kills your retargeting windows, shrinks lookalike audiences, and starves Smart Bidding of historical signal.

We set 1st-party cookies via HTTP headers on your own subdomain — exempt from ITP’s 7-day cap. Lifetime: 400 days. The maximum Chrome, Firefox and Safari currently permit.

  • 57× longer retargeting window vs Safari default

    Reach users who saw your ad 6 months ago instead of last week.

  • Bigger lookalike seed pools

    More retained users in your custom audience = better lookalike quality on Meta, Google, TikTok.

  • Smart Bidding has 13× more signal history

    Algorithms optimize on 400 days of behavior, not 7 days. CPA stabilizes faster.

  • Critical for high-AOV / long-consideration purchases

    If your average buyer takes 30+ days to convert, default cookies miss them. 400-day cookies don’t.

Cookie lifetime — head to head

How long cookies survive in real-world traffic

Safari ITP (default)7 days
Chrome / Firefox (typical)30 days
Meta default retargeting window90 days
Google Ads default cookie540 days(but capped by browser)
Our 1st-party server-side400 days

400 days is the hard maximum enforced by RFC 6265bis (Chrome 104+, Safari 17+, Firefox 110+). We set it via HTTP Set-Cookie: Max-Age=34560000 on your subdomain. Survives Safari ITP’s 7-day client-side cap.

Under the hood

What’s actually happening on your server-side stack

Six capabilities your default Broken after redesign setup doesn’t have. Built on the same Stape Pro stack used by enterprise DTC brands.

Cookie window

Cookie Keeper

400-day 1st-party cookies

Set via HTTP headers on your subdomain — the maximum browsers allow. Survives Safari ITP’s 7-day cap that kills retargeting.

Ad-block resistance

Custom Loader

Custom-loaded GTM scripts

Your gtm.js and analytics scripts load through a custom path on YOUR domain. uBlock, AdBlock Plus, Brave can’t identify them as trackers.

Attribution

Click ID Restorer

Click ID restoration

fbclid / gclid / ttclid / wbraid recovered from the URL and persisted server-side. Multi-redirect funnels stop dropping attribution. Safari user IDs restored.

Profit signal

POAS Data Feed

POAS — Profit on Ad Spend

Send actual profit data (not revenue) to Meta / Google. Smart Bidding optimizes for the metric that matters: net margin, not gross revenue.

Identity

User ID

Cross-session User ID

Stable userID generated server-side from IP + UA + SSL fingerprint. Stitches anonymous → known → returning visitors across 400 days.

Audience signal

GEO Headers

GeoIP enrichment

Country, region, city, postal code passed to Meta / Google CAPI from your server — without exposing the raw user IP to the browser.

Compliance

Anonymizer

PII hashing by default

Email, phone, name, address are SHA-256 hashed on your server before they leave for Meta or Google. Zero raw PII in transit.

Quality filtering

Bot Detection

Bot traffic detection

Bot/scraper traffic identified at the gateway and blocked from polluting your audiences. Smart Bidding optimizes against humans, not bots.

Reliability

Dedup logic

Browser ↔ server dedup

Deterministic event_id and event_time so Meta / Google never double-count. Your reported ROAS stops contradicting Stripe.

Reputation

Dedicated IP

Dedicated outbound IP

Your sGTM gets a dedicated static IP for outgoing CAPI requests. Better deliverability to Meta, Google, TikTok — no shared-IP noise.

Residency

Multi-region

EU / US region routing

GDPR-conscious stores route their CAPI traffic through EU regions (Stape EU or self-hosted GCR europe-west). No US data hop.

Data warehouse

BigQuery export

BigQuery + Looker dashboard

Server logs + GA4 raw events streamed to BigQuery. Looker Studio dashboard branded for your team. Premium tier.

We’re official Stape Pro partners — every Power-Up above is enabled and configured for you. Or we self-host the equivalent on your Cloud Run / GKE if your traffic justifies the cost crossover. You pick.

Live data flow

What your stack is doing — right now

Every conversion fires through your subdomain, gets enriched with hashed identity params, deduped against the browser pixel, then forwarded to Meta CAPI, Google EC, TikTok Events API and Microsoft UET in parallel.

You see this stream live in your sGTM debug console — not a SaaS dashboard you rent. It’s your data, on your server, on your subdomain.

  • p99 latency< 80ms
  • Avg. event payload9 identity params
  • Browser → Server dedupDeterministic event_id
  • Failure handlingRetry · queue · dead-letter
sgtm-debug · data.fix.com
streaming
10:42:18[INFO ]evt=PageView | id=ev_a3f2.. | ua=ios17 | ip_hash=ok
10:42:18[OK ]→ meta.capi status=200 emq_pred=8.6
10:42:18[OK ]→ google.ec status=200 match=enhanced
10:42:24[INFO ]evt=AddToCart | id=ev_b1c8.. | val=$84.00
10:42:24[DEDUP]browser↔server merged on event_id=b1c8..
10:42:24[OK ]→ meta.capi status=200 emq_pred=8.7
10:42:24[OK ]→ tiktok.eventsapi status=200
10:42:31[INFO ]evt=Purchase | id=ev_c9d4.. | val=$184.00
10:42:31[POAS ]profit=$58.42 sent (margin 31.7%)
10:42:31[OK ]→ meta.capi status=200 emq=8.8 ✓
10:42:31[OK ]→ google.ec status=200 ✓
10:42:31[OK ]→ microsoft.uet status=200 ✓
10:42:33[BOT ]blocked: ua=AhrefsBot · 1 evt suppressed
uptime: 99.98%all channels healthy
Every paid-media channel · 1st-party server-side

CAPI / Events API ready for every ad platform you run

One server-side gateway. Every major ad platform fed real conversion data, deduped, with full identity match.

Meta

Conversions API

Server-side

Google

Enhanced Conv.

Server-side

TikTok

Events API

Server-side

Microsoft

UET Server

Server-side

LinkedIn

CAPI

Server-side

Pinterest

CAPI

Server-side

Snapchat

CAPI

Server-side

Reddit

CAPI

Server-side

X / Twitter

Events API

Server-side
What you get

What we rebuild on the new site

Item 01

A before-and-after tag inventory

Every tag, trigger and variable from the old site listed against its fate on the new one: survived, broken, or now firing twice. This is the document that tells you how bad it is.

Item 02

Triggers rewritten for the new routes

URL, element visibility and History Change triggers rebuilt for the new paths and SPA behavior, including checkout steps and the confirmation flow, not just the homepage.

Item 03

The dataLayer rebuilt to a written spec

Event names, parameters and types documented first, then implemented with your developers, so variables stop resolving to undefined the moment someone renames a field.

Item 04

Duplicate and orphan cleanup

Staging container IDs shipped to production, leftover hardcoded pixels, dead remarketing tags and the old consent snippet — all found and removed rather than left to interfere.

Item 05

Catalog and feed ID remap

purchase and view_item item IDs mapped to the new product IDs in Merchant Center and the Meta catalog, then confirmed in each platform's diagnostics rather than assumed correct.

Item 06

Server container and CSP check on the new host

Transport URL, custom subdomain and the new site's Content-Security-Policy headers verified, because a fresh CSP is a common and very quiet way to block your own tags.

The honest math

Three ways to fix your tracking. One of them makes sense.

Option 1

Hire a senior tracking engineer

$15K–$25Kin dev cost

or 2–4 weeks of senior FTE time

  • 2–4 weeks before anything ships
  • Misses iOS / Safari / dedup edge cases
  • No EMQ guarantee — it’s “done” when they say so
  • Pixel debugging is not their day job

Option 2

Triple Whale / Hyros / Northbeam

$300–$2,000/month forever

$18K–$120K over 5 years

  • You rent a dashboard — they own your data
  • Cancel and you lose attribution overnight
  • Per-event / per-visitor pricing surprises
  • Still doesn’t fix your underlying tracking
Recommended

Option 3 — us

Done-for-you 1st-party server-side

$400–$1,800one-time

pay once · own the stack forever

  • Live in 2–4 days · accurate data within 7
  • iOS / Safari / dedup all handled by default
  • Meta EMQ 8+ guaranteed in writing
  • You own everything — server, container, runbook

We’re upfront: if you have a senior in-house dev with capacity and 4 weeks, hiring is fine. If you spend $1M+/yr on ads and want a SaaS dashboard layered on top, Triple Whale works. For most paid-ad advertisers between, we’re the math that makes sense.

From the founder’s desk
Ariful Islam — Founder
Available now

Ariful Islam

Founder & lead engineer

  • Experience8+ years in tracking
  • Engagements300+ DTC brands shipped
  • Specialty1st-party sGTM · CAPI
  • PartnerStape Pro · Meta Tech

“I’ll personally walk through your tracking on the call. No SDR. No sales pitch.”

I’ve spent 8 years rebuilding tracking for DTC brands, SaaS founders, agencies, and one thing I’ve learned: most tracking problems aren’t technical — they’re trust problems. You don’t know who to believe. Your current vendor swears it’s fine. Meta’s reports look great. Stripe says otherwise.

On our call, I’ll personally show you exactly what’s leaking, exactly what it would cost to recover, and whether you should hire us at all. If your current setup is genuinely fine, I’ll tell you. If a $400 browser-side fix is enough, I’ll say so. No upsell pressure.

Book the call. Worst case, you walk away with a free 47-point audit checklist. Best case, we deliver your 1st-party server-side stack in 2–4 days and your data is fully accurate within 7 days.

Arif— Founder

How it works

Built in 2–4 days. Accurate data within 7.

We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.

1Day 1

Kickoff + audit

30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.

2Day 2–3

Build the stack

Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.

3Day 4

QA + go-live

Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.

4Day 5–7

Verify accuracy

Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.

Diagnose it honestly

A launch dip is normal. A flatline means a trigger stopped matching.

Traffic, rankings and engagement genuinely wobble after a replatform, and no tagging work changes that. Conversions dropping to exactly zero on the day of launch is a different animal, and it is always mechanical.

Normal — not a fault

  • Organic sessions dip for a few weeks after a replatform

    New URLs, re-crawled pages and redirects settling. A gradual dip that recovers is search catching up with you. It looks alarming next to a conversion flatline and has nothing to do with it.

  • Landing-page paths in old reports no longer resolve

    Historical GA4 rows still hold the retired URLs, so year-over-year page reports read like everything broke. That's a reporting artifact of changing your URL structure, not lost tracking.

  • Conversion counts shift when the funnel itself changed

    If checkout went from three steps to one, fewer people abandon and the mid-funnel events genuinely stop existing. Compare the money event across the launch, not the step events that were redesigned away.

  • Engagement metrics move after a design change

    Faster pages and different navigation change behavior for real. Bounce and engagement rate moving on the same day as the launch is usually the new site doing its job, not a broken tag.

Actually broken

  • Purchases or leads went to exactly zero on launch day

    Not a dip — zero. A trigger keyed to /thank-you or /order-confirmation stopped matching a path that no longer exists, and nothing in GTM, Google Ads or GA4 will raise an error about it.

  • Events fire but arrive with empty value and currency

    The tag runs, the payload is hollow. The new theme renamed its dataLayer keys — productId where the old one pushed item_id, or ecommerce nested a level deeper — so your variables resolve to undefined.

  • Only the landing page is recorded on the new SPA

    React, Next or a headless storefront changes route without a page load. Without History Change triggers the entire checkout is invisible while the homepage looks perfectly tracked.

  • Conversions doubled instead of dropping

    The old theme's hardcoded gtag or pixel survived the migration alongside the GTM tag. Two tags, one order, and the post-launch report reads like growth right up until you reconcile it.

Diagnostic sequence

An hour in GTM Preview finds most of what the launch broke

Do this before hiring anyone — the list it produces is most of the actual job.

  1. 1

    Walk your own funnel in GTM Preview as a customer

    Open Preview against the live new site and go from ad landing page to confirmation with a real test order. Write down every trigger that doesn't fire and every variable that reads undefined.

  2. 2

    Read the dataLayer at the confirmation step

    Type `dataLayer` into the console on the thank-you page and expand the last push. Compare its key names against what your GTM variables are looking for. Renamed keys show themselves immediately here.

  3. 3

    Search the new page source for stray tags

    View source and search for `gtag(`, `fbq(`, `AW-` and `GTM-`. Any container or pixel ID you don't recognize is either a staging container shipped to production or a leftover the migration carried over.

  4. 4

    Try last quarter's top converting URLs on the new site

    Pull the top converting paths out of GA4 and open each one. Every 404 or unexpected redirect is a trigger that needs rewriting, and it's usually the confirmation page that nobody thought to test.

  5. 5

    Check the console for blocked requests

    Console errors mentioning Content-Security-Policy mean the new site's headers are blocking your own tags. A fresh CSP shipped with a redesign is a very quiet way to kill your tracking.

  6. 6

    Spot-check one product ID against your feed

    Take an item_id from a live purchase event and search for it in Merchant Center and the Meta catalog. Replatforms reissue SKUs and variant IDs far more often than anyone expects them to.

Source-of-truth validation

How we prove the new site is counted like the old one was

The test isn't whether tags fire. It's whether one order produces exactly one conversion, checked against your own order records.

Source of truthYour order table or CRM, for the days since launch
  • Run live test transactions on desktop and mobile and confirm exactly one conversion per order — not zero, and not two.
  • Match a full day of platform-reported conversions to your order table by transaction ID, and account for every difference.
  • Compare the day before launch to the day after on the money event only, ignoring step events the redesign removed.
  • Confirm item IDs in purchase events resolve in Merchant Center and the Meta catalog with no unmatched rows at variant level.
  • Verify the server container's transport URL and the new site's Content-Security-Policy both allow the first-party subdomain.
  • Re-check the full funnel a week after launch, once caching, redirects and the CDN have settled into their final state.

Straight talk

When a post-redesign rebuild isn't warranted

Not every redesign breaks tracking, and some breaks are a one-hour job you should do yourself.

  • The redesign was a visual refresh on the same platform, same URLs, same theme events. Check GTM Preview once and you're probably done.
  • You haven't launched yet. Put the tagging requirements into the build spec and run a container against staging — cheaper and calmer than this.
  • You don't run paid media and don't make decisions off the data. There's no bidding algorithm to starve, so a slower internal fix is defensible.
  • A developer on your team already found and fixed the broken triggers and your orders reconcile. Verify it once; don't pay to redo it.

Got questions?

The honest answers.

No buzzwords, no upsell. If we don’t know, we say so.

01Can I fix this myself?

Often, yes, and here's the fastest route: open GTM Preview on the new site, walk your funnel end to end as a real customer, and write down every trigger that doesn't fire and every variable that reads undefined. That list is most of the job, and it takes an hour. Where it stops being self-serve is a headless build with no page loads, a checkout that moved to another host, or a replatform that changed product IDs — those need developer time and catalog work rather than GTM clicks.

02How urgently do I need to deal with this?

Quickly, but don't panic-buy. The orders and leads are still happening — the new site is fine. What you're losing each day is the record of which campaigns caused them, and Smart Bidding has less to learn from. That compounds, which is why a week is fine and a quarter isn't.

03The agency says they kept the tracking code. Why is it broken?

Because keeping the container ID isn't the same as keeping the triggers. The GTM snippet in the new theme's header will load happily and fire nothing, if the URLs it listens for no longer exist and the dataLayer keys it reads have been renamed. The container is intact. The wiring between it and the site is what got cut.

04Do you work with our developers, or do you need site access?

Either. Most of the GTM and server container work we do ourselves with container access. The dataLayer pushes usually belong in the codebase, so we write the spec and your developers implement it, then we verify. On Shopify or WordPress we can often do the whole thing without touching your repo.

05Can we get the missing days back?

Not the data itself — anything not collected can't be backfilled. The one partial exception is Google Ads offline uploads, which can bring conversions back inside the 90-day click window if a click ID was stored somewhere, typically your CRM. Beyond that, the useful move is reconciling against your order table so you know exactly how large the gap was and can annotate the reports.

06We're replatforming next month. Can you prevent this instead?

Yes, and it's cheaper and calmer before than after. We put the tagging requirements into the build spec, run a container against staging, and give you a pre-launch checklist that gets signed off with everything else. Clients who do this hit launch day with working conversion data instead of a fire drill.

07When do we NOT need this?

If your redesign was a visual refresh on the same platform with the same URLs and the same theme events, check GTM Preview, confirm the purchase or lead event still fires with a real value, and you're done. This page is for replatforms, headless rebuilds and theme swaps — the changes that move URLs, rename dataLayer keys, or reissue product IDs.

Still have questions? Book a 30-min call — bring them all.

The call

What happens on your free 30-min call

No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and your Broken after redesign setup — we’ll work through it together.

Min 1–5

We get the lay of your store

What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.

Min 5–15

We audit your tracking live

Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.

Min 15–25

We map a fix

What needs rebuilding, what stays. The exact Broken after redesign setup we'd ship and what it would recover for you.

Min 25–30

Decide. Or don’t.

If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.

No pitch deckFounder-led, not SDRYou leave with a written planZero commitment
Free · 30 minutes · No commitment

Send me the old site and the new one

I'll compare what fired before against what fires now and send back the list of what broke — triggers, variables, duplicate pixels, catalog mismatches — before you commit to anything.

Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp

95% guarantee · fixed-fee