Bring offline revenue back into Google Ads
We upload your CRM, POS and warehouse conversions to Google Ads and GA4, then reconcile every batch so you see exactly what Google accepted, rejected, and silently ignored.
Built for agencies running real client data
Any source, one pipeline
A Sheet, a BigQuery query, a CRM or site webhook, a CSV, or a direct Exact Online or Lightspeed connection. Map the fields once (or auto-detect them) and every source runs through the same normalize, dedupe and consent checks.
Consent-safe by default
EEA consent is enforced per row: a row without ad_user_data granted is dropped, never defaulted to granted. Email and phone are hashed (SHA-256) before they go to Google.
Reconciliation you can act on
Per-batch accepted, rejected and processing counts, grouped rejection reasons, and a specific fix for each. Plus an email alert when a client's match rate drops.
Three steps, then it runs itself
Point it at a Sheet, BigQuery, a CRM webhook, Exact or Lightspeed, and map the conversion fields. For a webhook we hand the developer a ready-to-paste spec and a live test page.
Conversions go to Google Ads and GA4 on a schedule, consent-checked and deduped by transaction id, so nothing double-counts.
Every batch comes back reconciled: what was accepted, what was rejected and why, and what to change to lift the match rate.
The same real batch: every rejection grouped by Google's reason, with what it means.
Before you book a call
Who runs it?
We do. New North Digital sets it up on your accounts and runs it. You get the conversions back in Google Ads and the reconciliation that shows what Google did with them.
Which sources can it read?
A Google Sheet, a BigQuery query, a CRM or website webhook, a CSV upload, or a direct Exact Online or Lightspeed connection. Every source runs through the same checks.
Where do the conversions go?
To Google Ads and, if you want, GA4, through Google's Data Manager API. The same hashed identifiers can feed Customer Match lists, and conversions can also go to Meta as offline events through the Conversions API.
How do you tie an invoice to an ad click?
With the click id a tag on your site stores at the visit, matched to the order number or a hashed email on the invoice. Where no click id was captured, a hashed email address does the matching. The full explanation is on how matching works.
What happens to email addresses and phone numbers?
They are hashed (SHA-256) before they go to Google or Meta, and so are names. The only readable copy is the raw webhook or CSV payload as you sent it, which is encrypted at rest and deleted on a schedule, 30 days by default and never later than three times that period or 90 days, whichever is longer. Postal code and country go to Google unhashed, because its matching needs them. The details are in the privacy policy.
What about consent?
For people in the EEA, a row without consent for ad user data is dropped, never defaulted to granted. A source can instead run on a documented legal basis, which is recorded on the source and logged on every run. The legal basis stays yours as the controller.
Where is the data stored?
Currently in the United States (Vercel, and Neon in us-east-1), with EU Standard Contractual Clauses. EU hosting can be arranged before onboarding. The full list is on sub-processors.
Is there a data processing agreement?
Yes. We process your conversion data as your processor under our DPA.
Running Google Ads on offline conversions?
We will set it up on your accounts and run it. You get the conversions back in Ads and the reconciliation to prove it.
- Sends to
- Google Ads, GA4, Meta
- Email, phone, names
- Hashed before upload
- EEA consent
- Gated per row by default