Troubleshooting Offline Conversion Import Errors in Google Ads Understanding Offline Conversion Imports Offline conversion imports in Google Ads are designed to connect what happens in your sales process after the ad click with the campaign data inside Google Ads. For many US advertisers, that means importing qualified leads, closed-won opportunities, signed contracts, store visits, or phone-qualified sales that occurred outside the browser. The promise is simple: better attribution for revenue that a standard browser-based pixel can miss. In practice, the part that breaks most often is not the import concept itself, but the quality and structure of the file you upload. When a conversion row is rejected, the problem is usually a mismatch between the identifiers in your CRM export and the format Google Ads expects. This article focuses on the failure points that matter most: mismatch errors and formatting issues. That distinction matters. A formatting problem usually means the file structure, date, time, value, currency, or identifier format is wrong. A mismatch error means Google Ads received the row, but could not reconcile it with a click or with the conversion action settings you configured. Prebo Digital sees this most often when teams export from HubSpot, Salesforce, Shopify, WooCommerce, or a spreadsheet, then assume the Google Click ID or enhanced identifier will import cleanly without standardization. It often does not. The fastest way to reduce import errors is to treat offline conversion uploads like a data engineering task, not a media task. Small inconsistencies in date parsing, casing, or column names can stop an otherwise valid row from matching. The Importance of Accurate Data Accurate offline import data is the difference between optimizing for lead volume and optimizing for actual revenue. If your Google Ads account sees only form fills, it will usually push budget toward the cheapest leads, not the highest-value opportunities. If your offline import includes qualified sales or paid invoices, bidding signals become much more useful. That said, bad imports can be worse than no imports. A file filled with malformed timestamps, missing identifiers, duplicated rows, or wrong conversion action names can create false confidence and muddy your bid strategy. For US-based teams running lead generation or eCommerce-assisted sales, this accuracy also affects reporting across GA4, CRM systems, and call tracking tools. A single inconsistent field, such as “USD” in one row and “US dollars” in another, can create downstream confusion even if Google Ads accepts the file. The most reliable workflow is to define one source of truth for each field before the file is ever exported. That means matching your CRM time zone, Google Ads conversion action name, and click identifier rules from the start. 1 bad column can invalidate an entire offline import batch if the values no longer map to the configured conversion action. Common Formatting Issues The most common formatting issues appear in fields that seem harmless. Date formats are a classic example. A spreadsheet might contain 07/08/2026, but if the account team assumes that means July 8 while the system interprets it as August 7, the conversion can land outside the click window or appear on the wrong day. Time zone mismatches are equally common. Google Ads expects conversion timestamps to align with the account time zone, while your CRM may store timestamps in UTC or local sales-office time. If the import file ignores that conversion, rows can fail or misattribute. Another recurring issue is identifier formatting. GCLID values should be copied exactly as stored, with no extra spaces, line breaks, or transformations. When CRMs normalize or truncate fields, a valid click ID may no longer match the original ad interaction. This becomes especially common when teams build workflows in Zapier, make.com, or internal ETL tools and accidentally trim characters during field mapping. Even the conversion action name must match exactly. A trailing space or alternate capitalization can be enough to break a row. Warning: if your spreadsheet auto-formats GCLIDs, campaign IDs, or timestamps, do not upload directly. Excel and Google Sheets can silently alter values, especially long alphanumeric strings. Identifying Mismatch Errors Mismatch errors are usually more frustrating than obvious formatting errors because the file may upload successfully while the conversions still fail to attribute. In Google Ads, a row can look “clean” from a spreadsheet perspective but still not match a click, conversion action, or eligible date range. That makes diagnosis harder because the issue is not visual. It is relational. Something in the uploaded row does not line up with the account’s conversion setup or with the original click record. Types of Mismatch Errors Mismatch issues generally fall into a few categories. The first is click identifier mismatch, where the imported GCLID, GBRAID, or WBRAID cannot be matched to a recorded ad interaction. The second is conversion action mismatch, where the upload references a conversion label that does not exist or is not active in the account. The third is timing mismatch, where the conversion happened too far after the click or the imported timestamp falls outside the allowable conversion window. There is also value and currency mismatch, where the conversion value is present but not aligned with the currency configured in the account or upload. A practical example: a home services company in Texas might capture form submissions in HubSpot, then manually mark “booked estimate” in a CRM note field. If the upload process uses a generic deal stage instead of a defined Google Ads conversion action, the rows may pass review but still not map to the intended optimization goal. The same problem appears in B2B SaaS when sales teams rename lifecycle stages mid-quarter. What the dashboard sees as “SQL - Demo Held” may not match the label the import script expects. Diagnosing the Root Cause To diagnose mismatch errors, work backward from the row that failed. Start by checking whether the click ID exists in the source system exactly as exported. Then confirm that the conversion action in Google Ads is active, properly named, and configured for offline imports. Next, verify that the conversion time is after the click time and within the conversion window. If you are importing enhancements like enhanced conversions for leads, confirm the user identifiers are hashed properly and consistently, because partial hashing or mixed casing can prevent matching in some workflows. The best debugging process is systematic. Review one failed row at a time and compare it with the source record in your CRM, your export template, and the Google Ads conversion settings. In many cases, the issue is not a single typo but a chain of small inconsistencies introduced by handoffs between marketing, sales ops, and analytics. For teams with multiple spreadsheets, the root cause is often version drift: sales exports one file, ops edits another, and the upload uses a third. Standardizing the upload file removes that ambiguity. Step-by-Step Troubleshooting Guide A reliable troubleshooting process should eliminate uncertainty in layers. First confirm the raw data. Then confirm the identifier mapping. Finally confirm the Google Ads settings that control import behavior. This order matters because teams often spend time adjusting the platform when the file itself is broken. If you fix the export first, the platform becomes much easier to diagnose. Checking Your Data Format Begin by comparing your export against the exact column requirements in Google Ads Help. Verify that each row contains the required identifier and that values are not wrapped in quotes, reformatted by formulas, or truncated by the export tool. Watch for tabs, commas, and delimiters if you are using CSV files, because one hidden delimiter can shift every column to the right. If the file came from a CRM, inspect whether formulas converted IDs into scientific notation or dates into month/day variations. For high-volume advertisers, it is worth creating a locked export template with fixed headers and validation rules. That reduces the number of ways a human can accidentally break the file. If your process involves multiple tools, make sure the output from each one lands in the same schema before upload. A consistent schema is more valuable than a long list of ad-hoc manual edits. Validating Customer Identifiers Customer identifiers are where many uploads fail silently. GCLIDs must be preserved from the moment the click occurs through the final offline conversion file. If your landing page, CRM, or webhook does not capture the parameter reliably, there is nothing for Google Ads to match later. For enhanced conversions for leads, email addresses and phone numbers should be normalized before hashing, and the same normalization rules should be used every time. Lowercase, trim spaces, and avoid alternate spellings or punctuation when possible. If you are troubleshooting a specific row, check whether the identifier survived all intermediate systems. A common failure pattern is that the lead form records the click ID, but a sales rep manually copies the record into another system and omits the hidden field. Another is that a CRM integration imports the field but changes the label, so the export no longer finds it. The solution is to verify field persistence at each handoff, not just at the final upload. Reviewing Import Settings Import settings can be just as important as the file itself. Confirm that the correct conversion action is selected, that the attribution window fits your sales cycle, and that the time zone settings match your account and source records. If your business has long sales cycles, such as B2B services or enterprise software, a too-short window can make valid leads appear missing even though the data is correct. Also confirm whether Google Ads should count each conversion once or multiple times, depending on your reporting model. At Prebo Digital, the common pattern we see is this: the file is technically valid, but the account is set up to optimize for a different stage than the team intended. For example, a business wants to optimize for booked demos but is importing only form fills into a lead conversion action. In that case, the upload is not “broken,” but the data is being used against the wrong goal. Matching the import settings to the buyer journey is essential.
Read more 
