Skip to content
home

Analytics implementation · 2 min read

Enhanced conversions and offline conversion imports

How to send ad platforms the outcomes that matter, and what each approach needs.

By WebIQ Analytics · 30 July 2026

Ad platforms optimise towards whatever you tell them is a conversion. If that's a form fill, they'll find more form fills, good or bad. Sending them better outcomes, accurately matched, is one of the most effective improvements most advertisers can make.

Two approaches

  • Enhanced conversions add hashed first-party data (such as an email address or phone number, hashed before it's sent) to conversion tags, so the platform can match more conversions to ad interactions.
  • Offline conversion imports send outcomes that happen later, in your CRM, such as qualified leads or closed deals, back to the platform, matched by click ID or hashed customer data.

Google, Microsoft and Meta all offer versions of both, under different names (Meta's server-side route is the Conversions API). Requirements change, so check each platform's current documentation.

From click to qualified outcome, sent back to the ad platform.ClickClick ID captured withconsentForm or checkoutHashed email or phone(enhanced conversions)CRMLead qualified, dealwonUpload or APIOffline conversionswith valueAd platformBids towards realoutcomesPlatforms then optimise towards qualified leads or revenue, not form fills. Consent and your privacy notice must cover it.Simplified; check each platform's current requirements.
From click to qualified outcome, sent back to the ad platform.

What you need

  1. Click IDs captured on landing and stored with the lead or order, where consent allows.
  2. Consent and a privacy notice that cover sharing hashed data with ad platforms for measurement.
  3. A reliable CRM process that marks leads as qualified or won, with dates and values.
  4. An upload route: scheduled file uploads, an API integration or a connector.
  5. Deduplication, so the same conversion isn't counted from both the tag and the import.

Choosing what to send

  • Send the outcome closest to value that arrives in a useful time. Qualified leads often work better than closed deals, which may arrive too late or too rarely for bidding.
  • Include values where you can, so bidding can favour higher-value outcomes.
  • Keep the definitions consistent with your reporting.

Common pitfalls

  • Importing too long after the click, beyond the platform's matching window.
  • Sending unhashed personal data, or hashing it inconsistently.
  • Changing the definition of a qualified lead without telling anyone.

Remember what it doesn't do

Better conversion data improves platform optimisation and reporting. It doesn't make platform-reported results incremental. For budget decisions, use mix models and tests.

Tracking you can trust, with consent handled properly

We implement GA4, server-side tagging and Consent Mode v2, with an event specification your team can maintain.