Setup

1 destination per platform. Each starts in check mode: real validation, nothing counted. Go live once the checklist is done and a few runs look right.

Google Ads

Connected Oct 1, 2026

Google Ads customer IDConversion actionCreated by a person in Google Ads, type import from clicks, secondary to start.Value per qualified lead (CAD)What a qualified lead is worth to this client. Never negative.Which labels sendWhich leadsWebsite lead conversion (for spam retraction)

Retract spam from the website lead conversionOnly works where the site's Google Ads tag sends tracking.js's event ID as the transaction ID, within 54 days. Stops bidding from chasing spam.

Checklist4 of 5 done

Catch's manager account has access

The client account is linked under Catch's MCC, so uploads run as Catch.

Customer data terms accepted

Google Ads, Goals, Settings. Required before Google takes hashed contact data.

Enhanced conversions for leads turned on

1 setting since April 2026. Lets Google match on email and phone when there is no click ID.

"Qualified lead" action created as secondary

Type: import from clicks. Keep it secondary for 2 to 3 weeks, then a person decides whether bidding uses it.

Forms on tracking.js 7.3

Adds the PostHog IDs and event ID. Needed for journeys and spam retraction.

A person ticks each item after doing it in the ad account. Unticking one drops a live destination back to check.

Microsoft Ads

Connected Oct 1, 2026

Microsoft Ads account IDOffline conversion goalCreated by a person in Microsoft Ads.Value per qualified lead (CAD)What a qualified lead is worth to this client. Never negative.Which labels sendWhich leads

Checklist3 of 3 done

Catch's manager account has access

The client account is linked under Catch's Microsoft Ads manager account.

Offline conversion goal created

Wait 2 hours after creating the goal before the first upload.

Forms on tracking.js 7.3

Not strictly needed for Microsoft, but keeps every platform on the same lead record.

A person ticks each item after doing it in the ad account. Unticking one drops a live destination back to check.

What Website OS sends

A conversion for each qualified lead: a person's label at the next hourly run, a confident AI label after 24 hours.
Every identifier the lead carries: ad click IDs, and email, phone, name and postal code as SHA-256 hashes.
A retraction when a sent lead is relabeled not qualified or spam (Google and Microsoft; Meta cannot withdraw).
Spam retractions on the website lead conversion, where the setting is on.

What it never does

Touch campaigns, ads, keywords, budgets, bids, bidding goals, audiences or conversion actions.
Send raw contact details, or anything to Claude.

Ad sync

Setup

1 destination per platform. Each starts in check mode: real validation, nothing counted. Go live once the checklist is done and a few runs look right.

Google Ads

Connected Oct 1, 2026

Retract spam from the website lead conversionOnly works where the site's Google Ads tag sends tracking.js's event ID as the transaction ID, within 54 days. Stops bidding from chasing spam.

Checklist4 of 5 done

Catch's manager account has access

The client account is linked under Catch's MCC, so uploads run as Catch.

Customer data terms accepted

Google Ads, Goals, Settings. Required before Google takes hashed contact data.

Enhanced conversions for leads turned on

1 setting since April 2026. Lets Google match on email and phone when there is no click ID.

"Qualified lead" action created as secondary

Type: import from clicks. Keep it secondary for 2 to 3 weeks, then a person decides whether bidding uses it.

Forms on tracking.js 7.3

Adds the PostHog IDs and event ID. Needed for journeys and spam retraction.

A person ticks each item after doing it in the ad account. Unticking one drops a live destination back to check.

Microsoft Ads

Connected Oct 1, 2026

Checklist3 of 3 done

Catch's manager account has access

The client account is linked under Catch's Microsoft Ads manager account.

Offline conversion goal created

Wait 2 hours after creating the goal before the first upload.

Forms on tracking.js 7.3

Not strictly needed for Microsoft, but keeps every platform on the same lead record.

A person ticks each item after doing it in the ad account. Unticking one drops a live destination back to check.

What Website OS sends

A conversion for each qualified lead: a person's label at the next hourly run, a confident AI label after 24 hours.
Every identifier the lead carries: ad click IDs, and email, phone, name and postal code as SHA-256 hashes.
A retraction when a sent lead is relabeled not qualified or spam (Google and Microsoft; Meta cannot withdraw).
Spam retractions on the website lead conversion, where the setting is on.

What it never does

Touch campaigns, ads, keywords, budgets, bids, bidding goals, audiences or conversion actions.
Send raw contact details, or anything to Claude.

Google Ads

Meta

Microsoft Ads

Google Ads

Meta

Microsoft Ads

Before the first live send