IMPLEMENTATION SERVICE
Enhanced Conversions for Leads, wired to revenue.
Datahash connects qualified lead stages from your CRM to Google Ads with hashed first-party data, then puts values on those stages so bidding optimizes toward revenue. Datahash is a selected Google Implementation Partner (EMEA).
WHEN THIS IS YOU
The signs teams bring to us.
- You optimize for leads and get volume; sales says quality collapsed.
- Enhanced Conversions is "enabled" but nobody ever verified anything matches.
- Your CRM knows which leads became customers; Google never finds out.
- Every lead is worth the same to bidding, which is obviously false.
Every part of the EC4L setup, verified.
User-provided data tag and Conversion Linker in GTM, verified against every form touchpoint.
Hashing that matches
Lowercase and trimmed, phones in E.164, SHA-256, per Google's spec. Country, state, city, and zip stay unhashed by design.
The ingestion path that fits your stack
Google Ads Data Manager CRM connectors, scheduled files (Sheets, SFTP, HTTPS), or the Google Ads API with the consent field populated on every upload. Up to five identifiers per conversion, order IDs for dedupe, GCLID where available.
EC4L Diagnostics reviewed until status reads excellent.
MIGRATION METHODOLOGY
Keeping performance stable through the switch.
- Not on OCI today: EC4L actions created as secondary, GCLID+PII and PII-only rows flowing, a learning period of 2 weeks or 3 conversion cycles, then promotion to primary.
- Already on OCI: The existing action overridden in place, category changed, enriched flow started, optimization strategy untouched. No learning reset.
- Parallel run: EC4L secondary alongside OCI through learning, migrated campaign by campaign, then account default.
- Data rules: Send every combination you have, GCLID only, GCLID plus PII, and PII only; the PII-only rows are the ones teams forget. Google's thresholds for performance benefits: 2+ attributed conversions per action per day, 20+ valid PII-imported conversions per day, GCLIDs captured for reporting eligibility.
Values that bid toward revenue.
We map stage values to your lead economics (qualified, SQL, closed, expected LTV where you have it) and configure value rules so tROAS bids toward revenue rather than lead count.
No double counting
GA4 imports, the Ads tag, and EC4L uploads reconciled to one source of truth per conversion action before values go live.
Evidence, not assertion
Google's diagnostics show conversions received, matched, and accepted, read before and after, alongside the lead-quality trend.
Expected effect
Google's published medians for Enhanced Conversions show roughly 5% uplift on Search and 17% on YouTube measured conversions.
Conversions received, matched, and accepted.
Google's diagnostics, read before and after, next to the lead-quality trend.
Illustrative. No invented client numbers.
Discover, scope, implement, hand over.
3-4 weeks from tech approval.
-
Discover
CRM, identifiers, and conversion signals mapped; website, GTM, and forms reviewed on screen-share.
-
Scope
Business case and OCI status assessed; migration posture picked; expectations set on data completeness.
-
Implement
Step-by-step setup with your team, QA to fully active, match-rate issues resolved before go-live.
-
Handover and support
Structured report, 3-month support window, on-call for edge cases.
IN ONE SENTENCE
Enhanced Conversions for Leads (EC4L) is Google's privacy-safe method for lead-gen measurement: hashed first-party identifiers captured on lead forms are matched to CRM outcomes and sent back to Google Ads, so campaigns optimize on qualified and converted leads rather than form fills.
Adjacent moves on the same stack.
Implementation services
All nineteen builds.
Learn moreServer-side CAPI consultation
Decide the architecture first.
Learn moreGoogle EC for Leads offering
The product this service builds on.
Learn moreGoogle OCI
The offline import path EC4L upgrades.
Learn moreLead funnel events offering
Send CRM outcomes back to the platforms.
Learn moreQuestions your team will ask.
How is EC4L different from Offline Conversion Import?
OCI matches offline conversions to clicks using the GCLID alone. EC4L adds hashed first-party identifiers to the match, so conversions still attribute when the GCLID is lost and cross-device measurement improves. If you run OCI today, EC4L is the upgrade path, not a parallel system.
Do we need a GCLID for every lead?
No. Rows with hashed PII and no GCLID still match and should be uploaded. GCLIDs improve accuracy and reporting eligibility, so we implement Conversion Linker capture anyway, but a lost click ID no longer means a lost conversion.
We already send lead events. Why add values?
Volume optimization finds more of whatever you send; value optimization finds the leads worth more. Once stage values reflect your economics, Smart Bidding can trade ten cheap unqualified leads for three that close. Values without clean stages optimize noise, which is why the stage pipeline comes first.
Will switching disturb campaign learning?
It should not; the migration posture exists for exactly this. Overriding an existing OCI action keeps optimization history; new actions run as secondary through a learning period before promotion.
Is this compliant with GDPR and our privacy policy?
EC4L sends SHA-256 hashed identifiers with a consent field on every upload, only for users whose consent your CMP recorded. We review the consent flow in discovery; your counsel owns the interpretation.
Our CRM is not on Google's connector list.
Scheduled files over Sheets, SFTP, or HTTPS cover most stacks, and the Google Ads API covers the rest. Connector, file, or API is a scoping decision, not a blocker.
NEXT STEP
Book an EC4L working session.
Scoped with a consultant, not a sales script. We map your stack, name the dependencies, and give you the plan whether or not you run it with us.