Agency Guide: Enhanced Conversions Without a Developer
Most agencies know they should have Enhanced Conversions set up for B2B clients. Most don’t. The reason is almost always the same: “we need a developer for that.”
That’s not entirely wrong. Native Enhanced Conversions implementation for offline conversions requires a CRM webhook endpoint, normalization and SHA-256 hashing logic, Google API authentication, and retry handling for delivery failures. That’s developer work — if you’re building it from scratch.
Most performance agencies don’t have a developer. They have media analysts, Google Ads specialists, account managers. Data infrastructure gets deprioritized while Smart Bidding keeps optimizing toward form fills instead of the leads that actually progress in the CRM.
What Enhanced Conversions Actually Does
Enhanced conversions for leads let Google Ads receive conversion data that happens outside the browser — in the CRM, days or weeks after the click — and match it to the original ad interaction.
For B2B clients, the use case is sending meaningful CRM milestones back to Google Ads. The flow:
- A prospect clicks an ad. The Google Click ID (GCLID) is in the URL.
- The lead form captures the GCLID and stores it in the CRM alongside the contact record.
- The sales cycle runs — qualification, meetings, proposal.
- The deal reaches a configured milestone, for example “qualified lead”.
- A conversion event is sent to Google Ads with the GCLID and the hashed email and phone.
- Smart Bidding learns which clicks produced leads that progressed, not just leads that filled a form.
Without this, Smart Bidding sees only the form fill from step 2 — and only if the tag fired. A server-side upload arrives regardless of the browser, after the milestone happens. Why the browser-side event is unreliable in the first place is the subject of server-side tracking vs. pixel tracking.
Why Native Implementation Stalls Agencies
What native implementation concretely requires:
CRM webhook — when a deal changes stage, the CRM needs to make an HTTP call to an endpoint. That endpoint needs to exist somewhere. Someone needs to build, host, and secure it.
PII normalization and hashing — Google requires email and phone to be normalized (trimmed, lowercased, Gmail dots removed, E.164 for phone) and then SHA-256 hashed. A normalization error produces a different hash than the one Google can match, and the upload succeeds while matching nothing.
Google API integration — the event must reach the right API with the right parameters and valid OAuth2 authentication. Google now directs new conversion integrations to the Data Manager API (in Portuguese), which needs its own OAuth scope. Tokens expire and need to be refreshed.
Retry and deduplication — if the API returns a transient error, the conversion needs to be retried with the same transaction ID. If the webhook fires twice for the same deal and stage, the conversion must not be duplicated.
That is weeks of focused work for a developer new to these APIs, multiplied by every CRM variant across the agency’s clients.
The usual escape hatch is to wire it together in Zapier. It works, up to a point — but the task costs and silent failures of DIY CRM-to-Google pipelines tend to surface only once several clients are running on it.
What Middleware Replaces
A dedicated middleware — like True Conversions — already has this infrastructure built. The agency configures the integration, not the code.
What the setup requires from the agency:
1. Connect the CRM — each supported CRM has its own connector:
- RD Station CRM: paste the API token; True Conversions registers the deal webhooks and loads pipelines and stages for you to pick from a list.
- Pipedrive: authorize through OAuth; the deal-change webhook and a
GCLIDperson field are created automatically. - ActiveCampaign: enter the API URL and key; True Conversions registers the
deal_updatewebhook and creates aGCLIDcontact field. - Any other system (custom software, CRMs without a connector): send events to the account’s generic webhook URL and map the fields in the dashboard.
HubSpot and Kommo have no native connector; they go through the generic webhook, with the real payload validated before activation.
2. Get the GCLID into the CRM — the Pipedrive and ActiveCampaign connectors create the GCLID field, but your form or tracking layer has to fill it. True Conversions’ tc.js script captures the GCLID (and wbraid, gbraid, fbclid) on the site, fills hidden form fields when they exist, and sends the click ID with a browser-side email hash so it can be joined to the CRM event later.
3. Configure the Journey — choose which CRM stages are sent. Exactly one stage is Optimize (the milestone Google should bid on); other useful stages are Measure; everything else is Do not send. For the sale on RD Station CRM, use the separate “Venda realizada” milestone, which follows RD’s explicit won status rather than a stage name.
4. Connect Google Ads — OAuth authorization, then pick the account from the Conta encontrada (Account found) list. Criar e salvar conversões creates the missing actions as click imports set to Secondary; promote the Optimize action to Primary when you want Google to bid on it. Measure actions stay Secondary.
The account also needs enhanced conversions for leads turned on, with the customer data terms accepted. The enhanced conversions setting lives in the Google Ads conversion settings:

5. Test — move a test deal through two configured stages. Each should appear in True Conversions as its own delivery, then in Google Ads diagnostics a few hours later (Google’s processing delay, not the middleware’s).
A Conceptual Walkthrough: What Happens at Each Step
Step 1: GCLID Capture
Verify that the landing page keeps the gclid URL parameter and that it reaches the CRM record the milestone webhook reads. Most form tools (HubSpot Forms, Typeform, RD Station Forms) support hidden fields populated from URL parameters; asynchronous forms are where naive scripts fail. Without the GCLID, matching falls back to hashed email and phone only. The diagnosis is in offline conversion match rate: how to diagnose and improve it.
Step 2: Webhook Reception
With a native connector, this step is invisible: the connector registered the webhook and knows the CRM’s payload. For a generic webhook, mapping happens in a table — each field in the payload the CRM sends is bound, via dropdown, to the corresponding True Conversions field:

Step 3: PII Hashing
The middleware normalizes and SHA-256 hashes email and phone before anything is sent. Google and Meta normalize differently (Google strips Gmail dots and wants the + in phone numbers; Meta does neither), so each platform gets its own correctly normalized hash. Only hashes leave the middleware.
Step 4: Submission to Google
Since July 2026, True Conversions sends Google uploads through the Data Manager API on connections that granted its scope, falling back to the Google Ads API for older connections. Each event carries:
- the conversion action selected for that Journey stage;
- the GCLID, when the lead has one;
- the time the CRM milestone happened;
- hashed email and phone;
- a deterministic transaction ID derived from the deal, stage, platform, and destination, so a retry cannot create a second conversion.
No monetary value is sent by default. Real CRM revenue is optional, only on an eligible won stage, and only when the deal holds a positive value.
What to Expect in the First Weeks
First days: events arriving. Check delivery status per event in True Conversions and acceptance in the Google Ads diagnostics for each conversion action. A successful upload confirms receipt, not matching or attribution.
Following weeks: look at identifier coverage — how many paid leads carry a GCLID, email, and phone — rather than at a target match percentage. There is no universal “good” number; trends and missing-identifier patterns are what matter.
Bidding: how quickly Smart Bidding reacts depends on how often the Optimize milestone happens, how long after the click it happens, and the strategy in use. Google may need one to two conversion cycles to adapt after you change which action is Primary. Reported conversion volume may drop when you move from form fills to a qualified milestone; compare cost per qualified lead or per deal, not raw conversion counts.
The most consequential decision in the setup is which milestone to make Primary. The framework for choosing it is in Primary vs. Secondary conversion actions in Google Ads (in Portuguese).
A Note on Conversion Action Setup
The conversion action in Google Ads must be an offline click import. If it’s set to “Website” or “App”, the API rejects the upload instead of recording it — an error that’s easy to miss if nobody reads the API response. True Conversions only lists click-import actions in the Journey, which prevents this mistake.
Check this manually if you create actions yourself: in Google Ads, go to Goals → Conversions, open the action, and confirm its source is an import from clicks.
Next Step
True Conversions replaces weeks of development with a configuration: connect the CRM, connect Google Ads, choose the Optimize and Measure milestones — and they arrive in Google Ads as server-side offline conversions with correct hashing and the GCLID included. The trial is 60 days free with no card required; plans start at R$49/month.
Frequently Asked Questions
Do I need a developer to set up Enhanced Conversions?
No. A native implementation requires a CRM webhook receiver, normalization and SHA-256 hashing, Google API authentication, and retry and deduplication logic. With a middleware, the agency configures an integration instead of a codebase: connect the CRM, connect Google Ads, and choose which CRM milestones are sent — one to optimize, the others to measure.
How long does the setup take?
Typically under 30 minutes for a media analyst following the setup documentation. Pipedrive connects through OAuth; RD Station CRM takes a pasted API token; ActiveCampaign takes its API URL and key. No terminal and no server to host.
Do I need to create the conversion action in Google Ads myself?
No. The "Criar e salvar conversões" (Create and save conversions) button creates the missing conversion actions in Google Ads as click imports, set to Secondary, so bidding does not change until you promote the Optimize action to Primary. Creating them in Google Ads first, as type "Import", is optional.
When do results start showing up in campaigns?
First, confirm delivery in True Conversions and acceptance in Google Ads diagnostics. How fast bidding reacts depends on the volume and delay of the Optimize milestone, the bid strategy, and the conversion window. There is no universal monthly threshold or fixed timeline, and correct delivery does not guarantee a performance change.