Jackson

Founder of Taglert
Broken pixels = wasted spend + lost clients
• 24/7 Meta + Google tracking monitoring
• Catch it before your client does

→

[Jackson @jackson_saas]

A broken pixel can quietly waste 23% of your ad budget.

Most agencies find out when the client asks why results dropped. By then the money is gone and the relationship is shaky.

I built Taglert to catch it first.

It checks your Meta and Google ad tracking around the clock and alerts you when a pixel, CAPI, or conversion tag stops working. You fix it before it costs you the client.

Start free, 7 days, no card: https://t.co/zG18PygBMo

[Jackson @jackson_saas]

JOB OPENING: Tracking Health Monitor

Responsibilities: notice when the pixel dies. That's the whole job.

Hours: 24/7. Especially the Tuesday someone updates the theme.

Compensation: roughly 23% of the ad budget, recovered.

Current status: vacant at almost every company running ads.

Applicants: zero, because nobody knows the job exists until it's been empty for a month.

[Jackson @jackson_saas]

Right, and the interesting part is that intent data is only as good as what brands send back. CAPI pipes are leaky in practice: dedup breaks, match rates sag, values go missing. Meta's targeting edge is real, but it's built on infrastructure most advertisers never check again after setup day.

[Jackson @jackson_saas]

@ConnorBenham Good req. One thing worth adding to the interview: ask candidates how they'd verify a CAPI setup is still working three months later, not just how they'd set it up. Everyone can install it. The rare skill is noticing when dedup or match quality quietly breaks after a CRM change.

[Jackson @jackson_saas]

Ad dashboard translation guide:

"Events Manager: 400 purchases"
= everything your site counted. All traffic, every source.

"Ads Manager: 60 purchases"
= what your ads get credit for, inside your attribution window.

"Shopify: 240 orders"
= what actually happened.

Three tools. Three different questions. Zero contradictions.

The panic starts when you assume they're answering the same question. The insight starts when you track the ratios between them.

[Jackson @jackson_saas]

@mrakachukwu Solid, with one catch people miss: running both means dedup has to work. Same event_id on browser and server, or Meta counts everything twice and "better leads" becomes inflated reporting. Both installed is step one. Both agreeing is the real setup.

[Jackson @jackson_saas]

This is the underrated read. Ad units get the headlines but budgets renew on measurement. Worth watching how fast that new pixel/CAPI stack matures though. Every new platform's tracking has a rough first year, and buyers who reconcile against backend numbers early will know the truth before the dashboards do.

[Jackson @jackson_saas]

Step 1 being tracking is the right order, most people run this list backwards. One addition: the audit catches what's broken today, but accounts drift. The dedup that passes this week fails after the next app update. Scaling multiplies whatever the data quality is at that moment, good or bad.

[Jackson @jackson_saas]

Two sentences that sound identical:

"We got 50 conversions last week."
"We tracked 50 conversions last week."

The algorithm only ever hears the second one.

If 20 of your conversions leak — blocked pixel, failed dedup, missing values — Meta isn't optimizing your campaign. It's optimizing a rumor about your campaign.

30 well-tracked conversions train delivery better than 50 leaky ones.

Volume is what you count. Signal is what the machine hears.

[Jackson @jackson_saas]

The 4-ads pattern matches what I see too. One caveat: which 4 you think are carrying depends entirely on attribution being right. Seen accounts where a broken value parameter crowned the wrong winners for months. The concentration is real, but audit the scoreboard before you cut the bottom 90%.

[Jackson @jackson_saas]

Pop quiz.

Your ad platform says 100 sales. Your store says 85.

a) something's broken
b) totally normal
c) depends

Answer: c. And the variable isn't the size of the gap. It's the stability.

A steady 15% gap is attribution physics. Windows, view-through, blocked pixels. Every account has it.

A gap that was 8% last week and 30% this week is a broken pixel wearing a normal gap's clothes.

Don't chase the gap. Watch the change in the gap.

[Jackson @jackson_saas]

The two-receipts framing is right. One addition: the CRM timestamp only settles it if the CRM record actually links back to the click. That's why passing click IDs into the CRM at capture is worth the setup time. Without it you know the platforms double counted, but not which one earned the sale.

[Jackson @jackson_saas]

Good list, and there's a level under it: all three only work if the order data flows through cleanly. Most brands' reporting breaks at the plumbing before the analysis even starts, and then the smart cuts like these get computed on numbers that are quietly wrong. Check the pipes, then run the queries.

[Jackson @jackson_saas]

Saw a founder today offering a $500 bounty to anyone who can figure out why only 5% of their ad clicks register as landing page views.

They'd already rebuilt everything. New Business Manager. New pixel. New ad account. New domain.

The bug was never in the account. It was on the page.

Rebuilding your ad account to fix a tracking bug is buying a new car because the fuel gauge is stuck.

Diagnose before you demolish.

[Jackson @jackson_saas]

@ArifulIslamCSE This is the gap that costs lead gen accounts the most. Optimizing on form fills trains Meta to find people who fill forms. Sending qualified and closed stages back through CAPI trains it to find buyers. Same budget, completely different audience 90 days later.

[Jackson @jackson_saas]

@awpthorp @marclou @ZidaneZ08902030 @nico_jeannen Agreed on CAPI as closest to truth, with one catch: a CAPI setup drifts too. Tokens expire, dedup breaks, checkout apps update. The brands that actually trust their numbers don't just set up server events, they reconcile them against real orders on a schedule.

[Jackson @jackson_saas]

@Joelclark @zachlduncan Makes sense they'd pattern match CR by category. The other reason proxying backfires: even if it slips through, you've trained delivery on a signal that doesn't map to real revenue. You win the workaround and lose the optimization. Clean events beat clever ones.

[Jackson @jackson_saas]

The 5% number is the clue. Landing Page Views only count when the pixel loads on the destination page, so a gap this big lives on the site, not the account. That's why new BMs and pixels changed nothing. Check three things: the pixel actually firing on the landing page, redirects between the ad URL and the final page, and mobile load speed. It's almost always one of those.

[Jackson @jackson_saas]

The third one is the sneaky one because it disguises itself as the first two. A tracking gap makes creative look fatigued and audiences look saturated at the same time. Quick tell: backend sales steady while reported ROAS falls. If those diverge, stop diagnosing ads and go check the data.

[Jackson @jackson_saas]

@jangshern The pixel part is the one people learn too late. If the pixel and its event history live in the agency's BM, the "data" you own is a spreadsheet export, not the trained signal. Always run the pixel in the client's BM and grant the agency partner access, never the reverse.

[Jackson @jackson_saas]

Your CPA doubled overnight. Four suspects:

Creative fatigue - has an alibi. Frequency was 1.8, CTR steady.

The audience - has an alibi. No targeting changes in 30 days.

The algorithm - everyone blames it. Never once convicted.

Your tracking - no alibi. Because nobody even questioned it.

It's always the one nobody questions.