Most offline conversion upload failures come from a short list of causes: Google cannot match the click, the timing is wrong, the conversion action is set up incorrectly, or the file is formatted wrong. For a dealership, each failure means sold vehicles never get credited to the campaigns that produced them, so your vendor's reports and your DMS tell different stories. This guide shows how to read the error, fix it and confirm the sales are counted. It also covers the 2026 change that moved offline imports to a new interface.
TL;DR
- Start with the error report, not the file. Google shows exactly why each row failed, and most errors map to one fix.
- A click identifier (GCLID) older than 90 days, a conversion time before the click time, and a name that does not match the conversion action are the usual culprits.
- An upload with no errors can still show fewer conversions in reports. Reports credit the date of the original click, and processing can take 24 to 48 hours.
- Since June 15, 2026, new offline imports are routed to the Data Manager API, and the Google Ads API path is blocked for accounts that were not already using it.
- If your vendor says the numbers match and your DMS says they do not, the upload pipeline is the first thing to verify.
Table of Contents
- Why dealerships hit upload problems more than most advertisers
- Step 1: Find the exact error before changing anything
- Step 2: Sort the error into one of three groups
- The common errors and what fixes them
- When there is no error but conversions are missing
- What changed in 2026: the Data Manager API
- A weekly checklist for the person who owns the number
- Why an independent view of the pipeline matters
- Marketing Intelligence Review for dealership leaders
- Our perspective
- FAQ
- Sources
Why dealerships hit upload problems more than most advertisers
An offline conversion is a result that happens outside your website: a showroom visit, a phone sale, a financed deal booked in the DMS. To credit that result to a Google ad, you send Google the click identifier captured when the shopper submitted a lead, plus the conversion name, time and, optionally, value. Google matches it to the original click.
Dealerships make this hard in three ways. Sales cycles run from days to weeks, so the click is often old by the time the deal closes. The data passes through several systems: website forms, a CRM, the DMS and usually a vendor that handles the upload. And no one person owns the pipeline end to end. When a vendor reports 400 conversions and your DMS shows 90 matched sales, the gap often starts at an upload step nobody has inspected. Our GA4 audit for dealerships covers the CRM import side of this chain.
Step 1: Find the exact error before changing anything
Where you look depends on how the data is sent.
File uploads. Go to Goals, then Conversions, then Uploads. The Results column explains why a file failed, and Download errors gives a spreadsheet of failed rows with messages. Google removes those download links 30 to 60 days after the upload, so save the report if you need it for a vendor conversation.
API, Data Manager or CRM connections. Open the Conversion summary page, hover over offline data quality in the conversion action's status column, and click Go to diagnostics. Alerts are grouped by error type in order of how much data is affected, and the History panel shows uploaded events and events with errors over time.
Two thresholds help you triage. Google marks Review row errors as Urgent when 75% or more of rows fail and Needs attention when more than 25% but less than 75% fail. If Data import failed persists for more than three days, Google directs you to its support team.
If the whole file failed, read the first error in the file. A single account-level problem, such as a missing conversion action, stops every row.
Step 2: Sort the error into one of three groups
Before fixing, decide what kind of problem it is:
- Not yet: timing. The click is too recent, or the conversion action is new. Wait and resend.
- Final: the click is too old or cannot be found. The row will not be accepted, and the fix is upstream, so future rows do not repeat it.
- Problem with what was sent: a formatting, naming or account error. Correct the file or the connection and resend.
This prevents wasted effort. Reformatting a file will not rescue a click that is past the 90-day limit.
The common errors and what fixes them
Google's help center lists the frequent causes: identifiers that are too old, the wrong account for the clicks, unknown clicks, inactive conversion actions, user data that was not hashed, invalid conversion times and clicks less than 6 hours old. The table maps the messages dealers see most to their fixes, drawing on Google's FAQ.
| What you see | What it means | Fix |
|---|---|---|
| No Google Ads conversion types were defined | No import-type conversion action exists | Create a conversion action with the source Import from clicks (or calls) |
| Cannot find this conversion name in the target account | The name does not match, or the click belongs to another account | Match the name exactly, including capitalization; confirm the click came from the account you upload to; for accounts under a manager account, enable cross-account conversion tracking |
| Conversion date precedes click date | The conversion time is earlier than the click time, often a time zone mistake | Fix the time zone, or add a day or two to the conversion time |
| This click is too old | Click identifiers are retained for 90 days | Upload more often, or upload an earlier event that occurs within 90 days |
| Still processing this click's information | The click is too new | Wait about 6 hours for scheduled uploads |
Click too old: the dealership-specific problem
This is the error that matters most in automotive. Per Google, if a GCLID is older than 90 days or older than the conversion action's window, the fix is to upload more frequently or to upload a different offline event that happens within 90 days. For a shopper who clicked in week one and bought in week twelve, the sale cannot be credited, but the appointment set or the credit application approved can be.
That suggests a practical design: send several milestones, such as lead, appointment shown and sold, each as its own conversion action. Changing the lookback window later does not recover clicks already past it, per the API troubleshooting guide.

Name and account mismatches
The name in the file must match the conversion action exactly. Confirm the target account has a conversion action with that name and that its source is Import from clicks, which you can see in the Conversion source column on the Conversions page. Multi-rooftop groups using a manager account should check which child account the click landed in, since sending to the wrong one produces the account error. For API uploads, this appears as INVALID_CUSTOMER_FOR_CLICK, where the customer ID does not match the click's account.
Format and time zone errors
Missing or incorrectly formatted time zone information is a frequent cause of upload errors. Google recommends setting the time zone with a time zone ID such as Parameters:TimeZone=America/Chicago, which avoids daylight saving problems, or a GMT offset such as -0500. Supported conversion time formats include MM/dd/yyyy HH:mm:ss Z and yyyy-MM-dd HH:mm:ssZ.
Other format rules from the same page and Google's error guidance:
- Use the correct template and include every required header.
- Avoid extra columns.
- Never send unhashed personal information.
- If enhanced conversions for leads is on, use the template that includes the user-provided data columns. A plain GCLID template can cause errors.
For API uploads, exactly one of gclid, gbraid or wbraid must be set, and the conversion time must be after the click time, in the format yyyy-mm-dd hh:mm:ss+|-hh:mm, according to Google's own code example.
Timing errors that fix themselves
Google may not record conversions within one day of the click, so include an extra day of data in uploads. After creating a new conversion action, wait 4 to 6 hours before the first upload. The API returns TOO_RECENT_CONVERSION_ACTION if you do not. Automated uploads that fire the moment a deal is entered in the CRM often trip these errors, so schedule them with a delay.
Duplicates
Google does not count duplicates, and uniqueness is determined by the conversion action name, the conversion time and a unique identifier. Re-sending the same deal with the same details therefore adds nothing. If you use an order ID, make it unique per conversion and use a deal or invoice number, not a phone number or email address.
When there is no error but conversions are missing
This is the most common frustration for dealership leaders, because the upload report looks clean and the numbers still disagree. Check these in order.
- Wait. Imported data can take 24 to 48 hours to be fully processed and reflected in reports.
- Check the date range. Uploaded conversions are reported against the date of the original click, not the upload date or the sale date. A report limited to this week will not show sales uploaded this week from last month's clicks. Google's API support team explains this and adds that the columns labeled by conversion time report by the conversion date.
- Expect differences. Google's API team also notes that the number of successfully uploaded conversions does not necessarily equal the number of reported conversions. Attribution and reporting windows are separate from upload success.
- Look at alert severity. Some API errors are warnings. A warning-level error still counts in the successful event count in diagnostics, unless it happens with the majority of conversions.
- Check the status field. At account and conversion action level, the API exposes a status and counts of total, successful and pending events for the most recent full calendar day. If the status is not Excellent, the alerts list tells you what to fix.
A useful reconciliation: take last month's sold deals in the DMS that originated from a paid search lead, then compare against conversions credited by the offline action, using click dates. If the match rate is low and diagnostics are clean, the gap is likely upstream, in whether the click identifier was captured on the lead form and carried into the CRM. Our paid search audit walks through proving DMS sales before touching bids.
What changed in 2026: the Data Manager API
If your uploads suddenly started failing and nothing in the file changed, this is the first thing to check.
Google states that starting June 15, 2026, offline conversion imports and enhanced conversions for leads uploads migrated to the Data Manager API and were blocked in the Google Ads API. Developer tokens that had not sent a request between January and June 2026 were not allowlisted for legacy access. Google's May 15, 2026 announcement says developers who had not imported offline conversions between December 2025 and May 2026 receive the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when calling the click conversion upload service. Existing users can keep using the Google Ads API while they integrate with the Data Manager API.
For a dealership, this matters most when you switch vendors or CRM platforms. A new vendor setting up uploads under a new developer token may be unable to use the old route.
Two related points from the same Google page:
- As of April 2026, enhanced conversions for web and for leads were combined into one setting, and Google Ads accepts user-provided data from website tags, Data Manager and API connections at the same time.
- Google recommends upgrading existing offline conversion imports to enhanced conversions for leads using Data Manager, citing durability, more accurate reporting, engaged-view conversions and cross-device conversions.
For imports from Google Cloud Storage, S3, HTTP, SFTP and Google Sheets, Data Manager imports conversions from 90 days back in every run. Salesforce and HubSpot connections import the last 14 days on the first run, then all changes between runs. If you accept customer data terms, you avoid errors such as CUSTOMER_NOT_ACCEPTED_CUSTOMER_DATA_TERMS, which appear in API logs along with CUSTOMER_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS when the account setting is off.
A weekly checklist for the person who owns the number
You do not need to read error codes yourself. You need to know that someone does, on a schedule, and that you can verify it.
- Open diagnostics for each offline conversion action weekly. Confirm the status and note any Urgent or Needs attention alert.
- Save the error report from each failed file upload before the download link expires.
- Ask who owns each conversion action and which developer token or connection sends the data.
- Confirm which milestones are uploaded, and that at least one falls inside the 90-day click window.
- Reconcile uploaded sales against DMS sold deals by click date each month.
- Check that the right account receives the data for every rooftop under a manager account.
If you manage Performance Max, imported conversions feed its optimization, so upload errors distort it too. See our Performance Max audit for how to verify what that campaign is being credited with.
Why an independent view of the pipeline matters
Upload errors are a technical problem with a business consequence. When the vendor that runs your campaigns also reports on them and manages the upload, the same party is grading its own work. A failed upload under-reports sales, which can lead to budget moves based on partial data. A pipeline problem is also easy to describe as a platform quirk.
AutoROIQ does not sell advertising, manage campaigns or take commissions from vendors. That lets a review check the chain from click to sold deal without a stake in the result, and put the findings in terms a general manager can act on.
Marketing Intelligence Review for dealership leaders
If your vendors' conversion counts and your DMS sales do not reconcile, our Marketing Intelligence Review is built for that situation. It is an independent analysis of vendor performance and marketing channels, delivered as executive-level recommendations. We also offer ongoing strategic advisory services for dealerships that want that oversight to continue. Details are on the AutoROIQ site.

Our perspective
Offline conversion uploads are where dealership marketing reporting is most likely to go quietly wrong. The ad platform only knows what it is sent. If the click identifier was not captured, the sale was uploaded after the 90-day window, or a vendor changed its connection method, the sale does not exist in the platform. Decisions about spend then follow the incomplete picture.
We do not sell advertising and we take no commissions from vendors, so our only interest is whether the numbers are defensible. In our view, leadership should be able to see, for every conversion action, who sends the data, how often, which milestones are included and how the count compares with sold deals in the DMS.
The fix is rarely complicated once someone looks. The harder part is having an independent party ask the question before budgets are renewed. That is the purpose of our reviews and advisory work: clear, vendor-agnostic evidence that a dealership executive can take into a vendor meeting.
AutoROIQ
FAQ
Why does my offline conversion upload show success but no conversions in my reports?
Reports credit the date of the original click, not the upload or sale date, so check that your date range covers the click dates. Processing can take 24 to 48 hours. Google's API team also says successfully uploaded counts do not necessarily match reported counts.
How old can a click be for a dealership sale to be credited?
Google retains click identifiers for 90 days, and the conversion action's own window can be shorter. If your sales cycle is longer, upload earlier milestones such as an appointment shown or a credit application, and upload more frequently so you do not hit the limit.
Where do I see which rows failed and why?
For file uploads, go to Goals, Conversions, Uploads and download the errors, before the link expires after 30 to 60 days. For API, Data Manager or CRM connections, open the Conversion summary page and use Go to diagnostics on the offline data quality status.
Why did my uploads stop working in mid-2026?
Google migrated offline imports to the Data Manager API on June 15, 2026 and blocked the Google Ads API route for developer tokens that had not recently used it. A CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE error points to this. The connection needs to be moved to Data Manager.
Do I need enhanced conversions for leads?
Google recommends upgrading existing offline imports to it through Data Manager, citing greater durability and more accurate reporting. If it is enabled on the account, use the template with user-provided data columns, and make sure personal data is hashed.
Sources
- Fix discrepancies and errors in offline conversion imports, Google Ads Help
- Offline conversion imports FAQs, Google Ads Help
- About offline data diagnostics, Google Ads Help
- Import conversions from ad clicks into Google Ads, Google Ads Help
- Configure the Google tag for enhanced conversions for leads, Google Ads Help
- Troubleshooting, Google Ads API
- Monitor offline data diagnostics, Google Ads API
- Changes to Offline Click Conversion Import Support in the Google Ads API
- How long does it take for offline conversion data to be reported, Google Ads API forum
- UploadOfflineConversion example, Google Ads Java library
