The Signal Repair guarantee

If conversion events per 1,000 clicks recorded in Campaign Manager don't rise at least 15% over your trailing 30-day pixel-only baseline, you pay nothing.

Measured in your own Campaign Manager against your own trailing baseline. You pay $1,800 in advance at kickoff; if we miss the threshold, you receive a full refund.

Payment and timing

$1,800

Paid in advance at project kickoff

Repair delivered
Day 14
Measurement closes
Day 44

Threshold to clear

Conversion events per 1,000 clicks

+15%

If we miss the threshold, the full $1,800 is refunded within ten business days of the final export. Day numbers count from kickoff; the comparison covers the first 30 full days after delivery.

Guarantee terms · Revised 2026-09-06

01 · The four parts

What each part of the term means

1
The measurement systemrecorded in Campaign Manager

Campaign Manager. Your account, your numbers. Not our dashboard, not a third-party attribution tool, not a report we generate. If your Campaign Manager says the rate didn’t rise 15%, the guarantee pays. There is no version of this where we adjudicate.

2
The unitconversion events per 1,000 clicks

A rate, not a volume. A spend cut or a seasonal dip shrinks clicks and events together, so neither can trigger the refund — and we can’t inflate the result by spending more of your money. The unit is deliberately the one nobody can game from either side of the table.

3
The baselineyour trailing 30 days, pixel-only

Captured at kickoff, before anything changes — the account’s leaky state measured honestly, exported and dated so both sides hold the same starting number. Your account must be pixel-only at kickoff; we confirm that in the free check before either of us commits.

4
The thresholdat least 15%

A floor we will put in writing, not a forecast. The repair adds back events the browser loses — ad blockers, iOS privacy changes, cookie expiry, cross-device behavior — and 15% is the minimum recovered volume we’ll stake payment on. Most accounts leak more than that; we don’t promise your account’s number before measuring it.

02 · How it’s measured

The measurement, end to end

01
Baseline capture
Day 0–1

We export your trailing 30-day pixel-only conversion events and clicks from Campaign Manager, date it, and hand you the export. Both sides hold the same number before any work starts.

02
The repair
Days 2–14

Conversions API, deduplicated against the pixel — the same conversion counted once, never twice. Offline conversion import from HubSpot or Salesforce. Full schedule on the Signal Repair page.

03
The comparison window
First 30 full days after delivery

The post-repair rate over the first 30 full days after delivery, against the baseline rate. Symmetric windows — 30 days against 30 days.

04
The read
End of the window

You compute it, or we hand you the export format and you check our arithmetic. Events per 1,000 clicks, post-repair window vs. baseline. Under 15%, you pay nothing.

The conversion rules are the ones already in your account. Nothing is redefined, no new rules are added, and deduplication is enforced — a bigger number achieved by double-counting would be the CPL theater we started this business over.
Run the arithmetic yourselfIllustrative

rate = conversion events ÷ clicks × 1,000

18.4
Baseline rate
4,122 ÷ 224,000 × 1,000
21.2
Post-repair rate
4,622 ÷ 218,000 × 1,000
+15.2%
Change against baseline
21.2 ÷ 18.4 − 1

That account clears the threshold by 0.2 points. Pull both windows from Campaign Manager → Campaigns with the Conversions and Clicks columns showing, set the date range to each window in turn, and you have every number the term needs. Illustrative figures — yours come from your own export.

The export we hand you carries four columns: date range · conversion rule · events · clicks. Nothing else is needed to check our arithmetic.

The term measures recovered conversion volume, not campaign performance and not revenue. Those move on your sales cycle, which is the point of the repair rather than the point of the term.

03 · If it misses

What happens if we miss?

The full $1,800 is due in advance at project kickoff, before work begins. If the comparison window comes in under 15%, the full amount is refunded within ten business days of the final export — no clawback negotiation, no credit toward the pilot, cash.

You pay at kickoff, the repair is delivered on day 14, and the comparison window closes on day 44. If the guarantee is missed, the refund follows within ten business days of the final export. “You pay nothing” means the full fee is returned if we miss the threshold.

The conditions that keep the term honest, both directions: your account is pixel-only at kickoff (confirmed in the free check), Campaign Manager admin access and CRM API permissions arrive within five business days, the conversion rules in the account don’t change during the measurement, and campaign structure holds — new audiences, budget consolidation or campaign merges change the population of clicks the rate is computed on, so the window restarts from the next full 30 days. Change the ruler mid-measurement and the measurement is void — that clause protects you as much as us.

If the check finds you are already running Conversions API with healthy match rates, there is no leak to repair and nothing to guarantee. We say so on the call and you owe nothing but the twenty minutes.

These are the same words on every page and the same words in the contract. If the wording ever changes, this page takes a new revision date and the version you agreed to stays online at its own address — terms are not edited in place here.

Fix my tracking
When the money moves
Day 0–1$1,800 paid in advance at kickoff, before work begins. Baseline exported and dated.
Day 14Repair delivered. The 30-day comparison window begins after delivery.
Day 44Comparison window closes — 30 full days after delivery.
RefundOn a miss, the full $1,800 is refunded within ten business days of the final export.
Paid asCash. No clawback negotiation, no credit toward the pilot.

Day numbers count from kickoff. The refund clock starts at the final export, not at the end of the window.

Questions about the term

Couldn’t you double-count events to beat the threshold?

Deduplication against the pixel is part of the build — the same conversion counts once. And you read the result in your own Campaign Manager. A number we could inflate would defeat the reason the guarantee exists.

What if I cut spend during the measurement window?

That’s what the unit is for. Conversion events per 1,000 clicks is a rate: less spend means fewer clicks and proportionally fewer events, and the rate holds. A spend cut can’t trigger the refund. Neither can a seasonal dip.

What if I restructure campaigns mid-window?

Creative rotation is fine. Structural changes — new audiences, budget consolidation, campaign merges — change the population of clicks the rate is computed on, so the window restarts from the next full 30 days. We say this up front because it’s the clause you’d otherwise find in the fine print later.

When is the guarantee actually judged?

At the end of the comparison window — the first 30 full days after delivery — against the trailing 30-day pixel-only baseline captured at kickoff. Not at day 14. Day 14 is when the repair ships. The $1,800 payment is due in advance at kickoff.

Does the guarantee cover campaign performance?

No. It measures recovered conversion volume, not cost per lead, CPA, or revenue. Two different clocks: recovered volume shows in Campaign Manager within days; performance shifts need roughly 50 conversion events per campaign per month and run 30 to 60 days behind the repair.

Why only 15%?

Because it’s a number we’ll stake payment on in your account, not a forecast of your account. The browser-pixel leak is real — ad blockers, iOS privacy, cookie expiry — but its size varies by audience and setup. We measure your leak for free before either of us commits, then commit to a floor.