Offline Conversion Import Audit
Offline Conversion Import Audit
A read-only review of whether CRM-based conversion data sent into ad platforms matches the verified business records it came from.
What an offline conversion import audit is
Your ad platform shows offline conversions. The question is whether those conversions match what your CRM, your booked calendar, and your closed-won records contain.
An offline conversion import audit reviews whether offline or CRM-based conversion data sent back into ad platforms matches the business records it came from. It checks whether the imported events, values, timestamps, identifiers, and stages support the platform-reported conversions, CPA, conversion value, and ROAS.
This is not a setup review. The question is not whether offline conversions are configured. The question is whether the imported events, values, stages, timestamps, and identifiers match the verified business records they came from.
It belongs to the broader category of bad conversion tracking, and it sits alongside duplicate conversion counting as a related finding category.
Why offline imports are necessary, but still need verification
Offline imports are not a problem by default. For many businesses they are the only practical way to connect paid media to outcomes that happen after the click.
If you sell over the phone, book appointments, run a long B2B cycle, close high-ticket deals, or qualify leads inside a CRM, the sale does not happen on a landing page. It happens later. Importing that outcome back into the ad platform is how the platform learns which clicks led to downstream outcomes.
So offline imports are often necessary. That is not in dispute.
The audit question is accuracy. An import is a signal you send back to the platform. The platform reports what you send. If the imported event, stage, value, timestamp, or identifier does not match the business record behind it, the platform will still report it as configured. The report reflects the import. It does not independently confirm the underlying outcome.
What the audit compares
The audit compares what the platform reports against what the business records show. Six things get checked.
Imported events
Whether each imported conversion event maps back to a corresponding entry in the source system. The audit checks that an imported event ties to a record in the CRM, call log, or booking system it claims to come from.
Imported stages
A CRM has stages. Lead, MQL, SQL, booked appointment, closed-won. The audit checks which stage was imported as the conversion, and whether that stage matches the outcome the business is paying to acquire.
Imported values
When a value is attached to an imported conversion, the audit checks whether that value matches the verified revenue or recorded deal value in the business records. A static value, an estimated value, and a confirmed value are not the same thing.
Imported timestamps
The conversion time the platform sees comes from the import. The audit checks whether the imported timestamp reflects when the outcome occurred, because timing changes how the platform attributes and reports the conversion.
Imported identifiers
Offline imports rely on identifiers to match a conversion back to a click. On Google Ads that means GCLID, GBRAID, or WBRAID. On Meta it means matched customer fields such as a hashed email or phone number. The audit checks whether those identifiers are present, correctly matched, and consistent between systems.
Conversion actions
The audit checks which conversion actions are configured, which are marked Primary, and which are Secondary. Smart Bidding follows Primary conversion actions as configured. Which action carries that designation changes what the platform optimizes toward.
Common offline import findings
These are patterns the audit looks for. Finding one does not mean every import is wrong. It means one specific mismatch is documented and explained.
Wrong CRM stage imported
The conversion imported into the platform represents an earlier stage than the outcome the business cares about. A top-of-funnel lead gets imported as the conversion while the business is trying to measure booked appointments or closed deals.
MQL vs. SQL vs. booked appointment vs. closed-won mismatch
The stage the platform counts and the stage the business treats as the outcome are different stages. The platform may optimize toward the configured stage rather than the revenue-tied outcome.
One lead counted online and imported again offline
A single lead fires an online conversion at form submission and is then imported again from the CRM as an offline conversion. The same person is represented twice. This overlaps with duplicate conversion counting.
Duplicate offline imports
The same offline outcome is imported more than once, through a re-upload, an overlapping automation, or two systems sending the same event.
Wrong imported value
The value attached to the imported conversion does not match the value in the business record. An estimated or placeholder value stands in for a figure that was never reconciled against verified revenue.
Wrong imported timestamp
The imported conversion time does not reflect when the outcome occurred, which shifts the conversion into a different window than the one the business record supports.
Missing or mismatched identifiers
The identifiers needed to tie a conversion back to a click are absent, partial, or inconsistent between systems, so the match the platform reports cannot be confirmed against the source.
Primary vs. secondary conversion action misuse
A conversion action carries a Primary designation that does not match the outcome the business is bidding to acquire, so Smart Bidding optimizes toward a signal that does not represent the goal.
How import issues affect platform-reported CPA, ROAS, and conversion value
Here is why these mismatches matter to the numbers you use to make decisions.
The platform reports against the signal it was given. So when the import does not match the business record, the reported metrics describe the import, not the outcome.
Platform-reported CPA may measure the cost of the configured import signal rather than the cost of a verified downstream outcome. If the imported conversion is a lead stage rather than a closed deal, the reported CPA may appear to describe cost per sale when it describes cost per lead.
Platform-reported conversion value may reflect the values that were imported. If those values do not match recorded deal values, the reported value may appear higher or lower than the verified figure.
Platform-reported ROAS may not support a budget decision when imported values do not match verified revenue. ROAS is reported value divided by spend. When the value side comes from imports that were never reconciled, the ratio may appear to justify a budget that the verified revenue does not.
None of this means the platform is doing anything other than reporting what it received. It means the report should not be read as confirmation of the outcome until the import is checked against the record. This is the same gap covered in platform-reported ROAS vs. verified revenue.
What the audit examines
The audit examines the import path end to end, as it exists, without changing anything.
That includes the conversion actions configured in the ad platform, whether that platform is Google Ads or Meta, along with their Primary and Secondary designations and what each one is set to count. It includes the offline import itself, whether by file upload, scheduled import, API, or a connector through a tool like Zapier. It includes the source system the data came from, whether that is a CRM such as HubSpot or Salesforce, a call tracking platform, or a booking system. And it includes the business records that should sit behind each imported event: the deal record, the booked appointment, the call outcome, the recorded value, and the timestamp.
The comparison runs in one direction. What does the platform report, and do the records behind the import support it?
What a documented finding means
A finding is not a hunch. A documented finding exists only when the audit can support the mismatch with records.
That means the verdict shows the imported signal, shows the business record it should match, and shows where the two diverge. If that evidence is not available, it does not become a finding. It stays an open question, named as one.
Spend is treated the same way. Associated spend is mentioned only when there is a documented spend basis tying that spend to the affected conversion action or import. No documented basis, no spend figure.
The term potentially recoverable waste is used only when a finding supports identifiable, addressable inefficiency. It describes documented inefficiency that may be corrected, reallocated, or eliminated going forward depending on client action. It does not mean prior spend comes back or that a platform issues anything back.
Where this fits inside a Paid Media Verdict
This page describes one finding category. A Paid Media Verdict is the full written deliverable it appears in.
Inside a verdict, an offline conversion import finding sits under the broader bad conversion tracking section, next to related categories like duplicate conversion counting and page-load conversions. Each documented finding is written the same way: the signal, the record, the gap, and the spend basis when one exists.
The verdict is the product of an independent paid media audit. You can see how a finding reads in a sample verdict, and you can read how the review is conducted in the method.
This is not an implementation service
To be clear about what this is not.
This is a read-only review. BUT DID YOU WIN does not manage your campaigns. It does not rebuild your dashboards. It does not fix your imports. The deliverable is the finding and the evidence behind it.
What you do next is a separate decision. Once a finding is documented, fixing the import, changing the conversion action, or correcting the value is implementation, and implementation is yours to decide and execute or assign. The verdict tells you what the records show. It does not touch the systems.
FAQ
For questions beyond offline imports, see the full FAQ.
Request a verdict
If you spend meaningfully on ads and your imported numbers have never been checked against your records, that gap is worth documenting before the next budget decision.