Generate an offline conversion upload file
Turns a list of click IDs, timestamps and values into an upload-shaped CSV, and counts the rows that can never match because they carry no click identifier. That count is the number worth paying attention to: it's the ceiling on your whole offline import, and it's almost always the real problem rather than anything about the upload itself.
Free30 minutesNo obligation
Generate an offline conversion upload file
Turns a list of click IDs, timestamps and values into an upload-shaped CSV, and counts the rows that can never match because they have no click identifier. That count is the number worth paying attention to — it's the ceiling on your whole offline import, and it's usually the real problem rather than the upload.
Must match the conversion action configured in the platform.
Fill in Destination, Conversion name, Records — click ID, time, value (one per line) to generate the output.
Offline CSV · what breaks
What this tool is for — Offline CSV
- 01
You're setting up offline import
And want the file shape right.
- 02
Your uploads match poorly
Usually a click ID coverage problem.
- 03
You export outcomes manually
And want it formatted consistently.
Offline CSV · the fix
What you get out of it — Offline CSV
An upload-shaped CSV
Downloadable.
A count of unmatched-by-construction rows
The rows with no click ID.
An explicit instruction to verify the format
Against the platform's current template.
Offline CSV · architecture
Why offline import fails upstream of the upload
Everyone debugs the file. The problem is nearly always that the click ID never reached the record.
- 1
No click ID, no match
The upload can only reference a click the platform recognises. A record without one can never be sent, however clean the CSV.
- 2
Multi-step forms lose the parameter
Captured on step one, gone by step three, unless deliberately persisted.
- 3
CRM lead conversion drops unmapped fields
The value is on Lead, the Opportunity has nothing, and nothing errors.
- 4
A successful upload is not a successful match
The file processes, the rows don't match, and only the match rate tells you.
Offline CSV · diagnose
What this tool cannot tell you — Offline CSV
Stated up front, because a tool that implies more confidence than it has is worse than no tool. These are checks you have to run yourself.
- 01
Whether the format is current
Platform templates change. It produces the common shape and tells you to verify against the vendor.
- 02
Whether your click IDs are valid
It checks presence, not validity.
- 03
Whether the clicks are inside the import window
Google's window is 90 days from the click. Rows outside it fail silently.
- 04
Whether the upload succeeded
Read the match rate, not the success message.
Offline CSV · prove
How to confirm the result — Offline CSV
Against your own records, not against the tool's output.
Source of truth
your CRM records, matched on click identifier
- The share of records carrying a click identifier, measured before uploading.
- All four click parameters captured, not just gclid.
- Click IDs confirmed present on live records after full lead conversion.
- Match rate read after the upload rather than the success message.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked after your next site release, which is when most breaks happen.
Offline CSV · free audit
What we check in the free audit
- Whether the format is current
- Whether your click IDs are valid
- Whether the clicks are inside the import window
- Whether the upload succeeded
Checked against
your CRM records, matched on click identifier
Free30 minutesNo obligation
Offline CSV · when not to buy
Why this isn't gated — Offline CSV
There's no email form in front of it, and that's deliberate.
- A tool you have to pay for with your contact details is a lead form wearing a costume. If this is useful, it should be useful without a transaction.
- Everything it does runs in your browser. There is no endpoint, so there is nothing for us to collect even if we wanted to — open your network tab and check.
- It will tell you when you don't have a problem. That outcome costs us a sale and happens regularly, which is the point of publishing it rather than putting it behind a call.
- If it does find something and you'd rather fix it yourself, the reference pages on this site cover the how. Hiring us is one option, not the conclusion.
Offline CSV · what we deliver
What it checks — Offline CSV
Click ID presence per row
Rows without one can never match.
Row count
So you know what you're uploading.
Header shape
The common format, with a warning to verify it.
The 90-day window
Flagged as a constraint on which rows can match at all.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
If the tool found something and you'd rather not fix it yourself: we repair the root cause in your existing setup and verify it on a live conversion.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than the instance. Money events from your own records through a first-party container on your subdomain.
- First-party server container on your own subdomain
- Events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Offline CSV questions, answered
Because those can never match, and that count is usually the actual problem. Fixing capture matters more than fixing the file.
No, and it says so. Platform templates change — verify against the vendor's current documentation before uploading.
Clicks older than Google's import window can't be matched. Rows outside it will fail as unmatched without much explanation.
No. The CSV is generated in your browser and downloaded locally. There is no endpoint.
Free · 30 min
Close the loop from your CRM to your bidding
Free30 minutesNo obligation
