First-Party CRM Data as a Moat for the Post-Cookie Algorithm
The Algorithmic Shift That Changes the Competitive Landscape
Google Ads has been moving from manual bidding to automated bidding for a decade. Performance Max replaced Smart Shopping, and conversion-based strategies such as Maximize Conversions and Target CPA are the default choice for most lead-generation search campaigns.
That shift has a specific implication: the bidding algorithm can only optimize toward the conversions you tell it about. When bidding was manual, the limiting factor was the analyst’s judgment and bandwidth. When bidding is automated, a large part of the outcome depends on which conversion events reach the platform, how complete they are, and whether they represent business value or just activity.
A word on “post-cookie”: Chrome did not remove third-party cookies, and this article does not depend on that happening. The browser-side signal has been eroding for other reasons that are already in place — Safari and Firefox tracking protections, ad blockers, consent choices, and the simple fact that a B2B deal is qualified and won in a CRM, not in a browser session. First-party CRM data is useful regardless of what happens to cookies.
What “Clean Data” Means in Practice
The Google Ads algorithm optimizes toward whatever it is told is a conversion. Clean data means three things:
Completeness — the milestones that matter reach Google Ads consistently, without gaps from ad blockers, cookie restrictions, or forgotten manual uploads. Those gaps are the structural weakness of browser-side measurement, covered in server-side tracking vs. pixel tracking.
Meaning — the conversion represents real commercial progress. A form fill is lead generation; a qualified lead or a sales-accepted opportunity is a stronger statement about the click that produced it. For most B2B accounts, the practical bidding signal is one qualification milestone that happens often enough, with the deal won measured separately. The trade-offs are covered in Primary vs. Secondary conversion actions in Google Ads (in Portuguese).
Accuracy — identifiers are normalized correctly, event times reflect when the milestone happened, and any value sent is real CRM revenue rather than an invented proxy.
When those conditions are met, Smart Bidding learns from the leads that actually progress instead of the ones that only fill forms. That is a better input; it is not a guarantee of a specific performance change.
The Mechanics of SHA-256 Hashing
Sending email or phone to Google for conversion matching requires SHA-256 hashing of normalized values. Hashing is Google’s technical specification; it does not by itself make the processing lawful — consent or another legal basis under LGPD or GDPR is still required at collection.
Normalization happens before hashing, and a different input produces a different hash. Wrong normalization does not produce an upload error; it produces an identifier that matches nothing. It is one of the first things to check when offline conversion match rate looks low.
Email Normalization
Input: " [email protected] "
Step 1: Trim whitespace → "[email protected]"
Step 2: Lowercase → "[email protected]"
Step 3: Gmail only: remove dots in the local part → "[email protected]"
Hash: sha256("[email protected]")
Google’s rule removes the periods before the @ for gmail.com and googlemail.com addresses. True Conversions applies that dot removal to gmail.com and keeps the +tag as received. Meta is different: its Conversions API expects the email only trimmed and lowercased, with Gmail dots kept, so one shared hash cannot serve both platforms. True Conversions derives a separate Meta-normalized value from the raw email for that reason.
Phone Normalization
Input: "(11) 99123-4567"
Step 1: Remove formatting → "11991234567"
Step 2: Add country code → "+5511991234567" (E.164)
Hash: sha256("+5511991234567")
The country code is mandatory: Google expects E.164 with the leading +. Meta expects the same digits without the +, which is another reason to keep platform-specific normalization tested and versioned.
What True Conversions Does With This
True Conversions receives the CRM event, normalizes each identifier per platform, computes the SHA-256 hashes, and sends only the hashes to Google Ads and Meta. Neither the raw email nor the raw phone leaves the integration for the ad platforms. Google uploads go through the Data Manager API on connections that granted its scope, with the Google Ads API as fallback for older connections.
Audience Signals and Customer Match
Performance Max uses audience signals as a starting point for where to look; it is not limited to them. Customer Match lists — hashed emails and phones of existing customers, uploaded with consent and under Google’s Customer Match policy — remain a valid audience signal.
Two corrections to a common pitch. First, Google retired similar audiences (“lookalikes”) in 2023, so a Customer Match list no longer seeds a separate lookalike segment; it informs the campaign’s own audience expansion. Second, a conversion log is not automatically a Customer Match list. Customer Match has its own eligibility, consent, and upload requirements, and True Conversions does not create or upload audiences — it sends conversion events.
The durable advantage comes from the conversion events themselves: each month of clean, qualified milestones gives Smart Bidding a more accurate record of which clicks produced real progress.
RD Station, Pipedrive and ActiveCampaign: Platform-Specific Notes
RD Station CRM
RD Station CRM has a native connector in True Conversions: paste the API token, and True Conversions validates it, registers the deal webhooks, and loads the pipelines and stages. Pick stages from a list; they are matched by stable stage ID, so renaming a stage does not break routing.
For the sale itself, use the separate Venda realizada milestone (RD CRM: marked as won). It is driven by RD’s explicit won status and its closing timestamp, not by the current pipeline stage. A stage named “Ganho” is just another stage and does not prove a win. The full setup is in RD Station CRM to Google Ads (in Portuguese).
Pipedrive and ActiveCampaign
Both have dedicated connectors. Pipedrive connects through OAuth; ActiveCampaign through its API URL and API key. In both cases True Conversions registers the deal webhook automatically and creates or reuses a GCLID custom field — no generic webhook or CRM automation to build. Details are in the ActiveCampaign and Pipedrive guide.
For contacts without a GCLID (organic leads, referrals), matching relies on the hashed email and phone. Those conversions still upload; whether they match depends on Google recognizing the identifiers.
Building the Data Advantage
There is no universal monthly conversion threshold or fixed learning timeline that applies to every account. What is true everywhere: Smart Bidding can only learn from history it has, and history starts accumulating the day the pipeline is correct.
The alternative is to keep optimizing on form fills, which are not revenue, and hope the algorithm infers what a good lead looks like without being told.
The data pipeline is infrastructure. Like any infrastructure, its value accumulates over the time it has been running correctly.
Next Step
True Conversions sends qualified CRM milestones server-side to Google Ads and Meta as hashed, deduplicated conversion events — one Optimize stage for bidding, the others for measurement, no Zapier and no CSV uploads. The trial is 60 days free with no card required; plans start at R$49/month.