Google Ads Offline Conversion Import from Google Sheets: Keep the Sheet Filled Automatically

Quick Summary
Google Ads offline conversion import tells Google which ad clicks turned into sales or qualified leads after the visitor left your website. You save the Google Click ID (GCLID) with each lead, and when that lead becomes a customer you send Google the GCLID, the conversion time and optionally a value. Without a developer, the simplest route is a Google Sheet that Google Ads reads on a schedule: either through Data Manager, which Google now recommends and which runs at most daily, or through the older scheduled file upload, which Google labels legacy. Each scheduled run reads conversions from the last 90 days. The hard part is keeping that sheet correct: one row per sale, an exact click ID, an unambiguous time with a time zone, no duplicates and no rows without a click ID. In WorkflowMitra, powered by ChatMitra, a workflow watches the status column of your lead sheet and adds a correctly formatted row to the conversions sheet the moment a deal is won.
Your Google Ads account knows who clicked. It doesn’t know who bought. A lead fills in your form on Monday, your sales team calls on Tuesday, and the deal closes on the phone two weeks later. Google records a form submission, if you track one, and nothing more. Smart Bidding then optimises for form fills, including the ones that never answer the phone.
Offline conversion import fixes that by sending Google the sales that happened after the click. The simplest version needs no developer: a Google Sheet that Google Ads reads on a schedule. This guide covers what that sheet must contain, the 2026 changes to how Google reads it, the time-zone and duplicate traps that cause most import errors, and a workflow that adds a correct row the moment a deal is won. Examples use WorkflowMitra, powered by ChatMitra, but the sheet rules come from Google’s own documentation and apply to any setup.
Quick answer: Turn on auto-tagging, save the GCLID with every lead, and create an offline conversion action in Google Ads. Keep a separate conversions sheet with the headers in row 1: Google Click ID, Conversion Name, Conversion Time, Conversion Value, Conversion Currency and Order ID. Connect it through Data Manager (Google's recommended route, runs at most daily) or the older scheduled upload (labelled legacy). Write every time with a time zone, skip leads with no click ID, and check the Order ID before adding a row. Google reads the last 90 days on each run. A workflow that watches your lead sheet's status column keeps the conversions sheet filled for you.
How offline conversion import works
Offline conversion import connects four moments that happen in different systems:
- The click. With auto-tagging on, Google Ads adds a
gclidparameter to your landing page URL. It’s a long, case-sensitive ID for that one ad click. - The lead. Your form saves the GCLID in a hidden field, next to the person’s name and phone number. Google’s GCLID setup guide describes exactly this: a hidden form field, a small script that keeps the ID in a cookie, and a custom field in your lead system.
- The sale. Days or weeks later, the lead becomes a customer. That happens in your CRM, your sheet or your sales team’s heads, not on your website.
- The import. You send Google the GCLID, the conversion action, the time of the sale and optionally its value. Google matches the click ID to the original click and credits the campaign, ad group and keyword that produced it.
Steps 1 and 2 are covered in our guide to tracking lead source automatically, and for Google Ads lead form ads the click ID arrives in the webhook as gcl_id (see Google Ads lead form webhook). This guide is about step 4, and about the sheet that makes it reliable.
What changed in 2026
Google has been moving offline conversions to a newer system, and three facts matter if you are setting this up now:
- File imports are “legacy”. Google’s help page for importing conversions from files is now titled Import conversions from ad clicks into Google Ads using files (legacy). It still works, including scheduled imports from a linked Google Sheet, but it says you should import conversions using Google Ads Data Manager instead.
- Data Manager reads Google Sheets. Data Manager can connect a Google Sheet directly as a source for conversions, map your columns to Google’s fields and import on a schedule.
- The API path moved. Google’s overview of offline conversion imports says imports are migrating to the Data Manager API and being blocked in the Google Ads API. The Google Ads API deprecations page dates the restriction to 15 June 2026: developer tokens that sent no offline conversion uploads between 17 December 2025 and 15 June 2026 now get an error and must use the Data Manager API instead.
For a business without a developer, the practical conclusion is simple: keep a clean Google Sheet and let Google read it. There is no developer token, no API version to track and no code to maintain. What remains is keeping the sheet correct, which is what the rest of this guide is about.
Two ways Google Ads can read your sheet
| Data Manager connection (recommended) | Scheduled upload (legacy) | |
|---|---|---|
| Where you set it up | New conversion action → Import → CRMs, files, or other data sources → Google Sheets → Direct connection | Goals → Conversions → Uploads → Schedules → link an existing Google Sheet |
| Column headers | Your own, in row 1, mapped to Google's fields in dropdowns | Google's template names, such as "Google Click ID" |
| Which tab is read | Only the first sheet in the spreadsheet | The linked file |
| Time zone | In the data, or a fallback time zone set in the import; rows without either are not imported | In the "Parameters:TimeZone" row, the Conversion Time column, or both |
| Schedule | Manual or scheduled, at most once a day | Frequency and time chosen in the schedule |
| How far back each run reads | Conversions from the last 90 days | Upload an extra day's data with each import, as Google advises |
| Email and phone for enhanced conversions | Supported; Data Manager normalises and hashes them | Enhanced conversions for leads needs Data Manager files |
Sources: Google Ads Help pages on Data Manager’s Google Sheets source, preparing data for import, managing connections and legacy file imports, read on 19 October 2026.
Use Data Manager for a new setup. The sheet design below works for both routes, because it uses Google’s template column names in row 1, which Data Manager lets you map and the legacy route expects.
Which conversions to import
Before you build anything, decide which moments count. Most lead-generation businesses have three or four stages after the form: contacted, qualified, visit or demo, won. Import the ones that really separate good leads from bad ones.
Import “Won” with a value if most deals close within a few weeks. It’s the signal Smart Bidding needs most, and the value lets value-based bidding favour the campaigns that bring bigger deals.
Add an earlier milestone if your cycle is long. For Google Sheets sources, each run reads conversions from the last 90 days, and Google’s GCLID guide says the click-to-conversion cycle must stay within that window. A property developer whose sales close four months after the enquiry would lose most of them. Importing “Site visit done” as a separate conversion action gives Google a signal it can still use.
Decide primary or secondary carefully. Google’s setup guide warns that marking an offline action as primary changes what Smart Bidding optimises for. A common pattern is to make the deepest stage you can import reliably the primary action and keep the others secondary for reporting.
Create each conversion action in Google Ads before the workflow writes rows for it, and, as Google’s GCLID guide advises, wait four to six hours after creating an action before the first upload for it.
Design the conversions sheet
Keep conversions in their own spreadsheet, separate from your lead sheet. Your team edits the lead sheet all day; Google should only ever see clean, finished rows. Data Manager reads only the first tab, so give each conversion action its own spreadsheet, for example “Ads conversions – Won” and “Ads conversions – Site visit”.
Put these headers in row 1 of the first tab:
| Column | Example | Notes |
|---|---|---|
| Google Click ID | Cj0KCQjw… | Required for offline import. Copy exactly; it's case-sensitive |
| Conversion Name | Won deal | Exactly the conversion action's name in Google Ads |
| Conversion Time | 2026-10-19T08:35:00Z | With a time zone; see the next section |
| Conversion Value | 125000 | Optional. Digits only: no ₹ sign, no commas |
| Conversion Currency | INR | Optional. Three-letter currency code |
| Order ID | L-2026-0418 | Optional for Google, essential for you: one unique ID per conversion |
The account that connects the sheet in Google Ads needs Editor access to the file, and Data Manager’s headers must start with a letter or underscore. Leave the rest of the tab empty: no notes rows, totals or merged cells.
If you advertise to people in the European Economic Area, Google’s legacy template also has Ad User Data and Ad Personalization consent columns. Fill them from your own consent records; don’t guess.
Getting the conversion time right
Most failed imports come down to the time column, so it’s worth being precise.
Always include a time zone. Data Manager says that rows without a time zone need a fallback time zone in the import settings, and that without one those rows aren’t imported. The legacy route takes the time zone from a Parameters:TimeZone row, from the Conversion Time values, or both. Putting it in every value is the one approach that works the same on both routes.
Never write DD/MM dates. Google reads an ambiguous date such as 02/01/2026 as 1 February, not 2 January. Data Manager’s data preparation guide says that if a row is identified as DD/MM/YYYY, the import fails to prevent incorrect processing. Indian spreadsheets default to DD/MM, which makes this the most common trap for teams here. Use the year-first ISO format.
Write the time as text, not as a sheet date. If Google Sheets turns your value into a date, it displays it in the spreadsheet’s own format, which may be the DD/MM format you were trying to avoid. Writing values “exactly as written” keeps the text intact.
In WorkflowMitra, now() returns the current time in UTC. Two expressions turn it into the formats Google documents:
| Route | Expression | Result (tested 19 October 2026) |
|---|---|---|
| Data Manager | {{ substring(now(), 0, 19) }}Z | 2026-10-19T01:33:20Z |
| Legacy scheduled upload | {{ replace(substring(now(), 0, 19), "T", " ") }}+0000 | 2026-10-19 01:33:20+0000 |
UTC with an explicit marker is unambiguous everywhere: Google converts it to your account’s time zone, so a sale at 2:05 pm in India appears at 2:05 pm in your reports. It also avoids depending on the time zone of whatever server runs your workflow. Separate the arguments with commas; in our tests, semicolons silently returned an empty value.
The time should be when the conversion happened. A workflow that reacts to the status change within a minute or two is close enough. If your team updates statuses in a batch at the end of the week, the conversion time should come from a “closed on” column instead, and the Data Manager import’s “Convert date and time” transformation can read it, as long as the format is year-first or month-first.
Before you start
You need four things in place:
- Auto-tagging on in your Google Ads account settings.
- GCLIDs captured with each lead: a hidden form field filled from the URL, or
gcl_idfrom Google’s lead form webhook. - A lead sheet with at least
lead_id,gclid,statusanddeal_valuecolumns, plus an emptyads_statuscolumn for the workflow to write to. Use a dropdown forstatusso “Won” is always spelled the same way. - The conversion action created in Google Ads, and the empty conversions spreadsheet with its header row.
Build the workflow step by step
The workflow watches the lead sheet. When a row’s status changes to Won, it checks the row, adds one correctly formatted line to the conversions sheet, and marks the lead so you can see what was sent.
1. Watch the status column
Create a workflow with the When a sheet row changes trigger (Google Sheets integration). Connect your Google account, pick the lead spreadsheet and its tab, set Use column headers as IDs of the columns to Yes with lead_id as the ID column, and under Run when… choose One column changes and tick only status.
The first check records the sheet as it is and starts nothing, so leads that were already Won aren’t sent. From then on, each status change starts a run with that row’s values under their column names.
2. Continue only for won deals with a click ID
Add an IF step with two conditions joined by AND:
{{ $trigger.status }}Equal to, ignore caseWon{{ $trigger.gclid }}Is not empty
“Ignore case” accepts “won” and “WON”, but it doesn’t trim spaces, which is another reason to use a dropdown for status.
3. Mark won deals that can’t be imported
On the IF step’s Else branch you get every other status change, including Won deals without a click ID. Add a second IF that checks for the second case: {{ $trigger.status }} Equal to, ignore case Won. On its yes branch, add Google Sheets → Update row on the lead sheet, matching lead_id to {{ $trigger.lead_id }}, and set ads_status to Not imported: no click ID.
That row is now visible instead of silently missing. A cluster of these points to a broken hidden field or a campaign without auto-tagging, which is worth knowing long before you wonder why the numbers look low.
4. Check for an existing row
On the main IF’s yes branch, add Google Sheets → Find row on the conversions spreadsheet: Key column Order ID, Key value {{ $trigger.lead_id }}. Then add an IF step: {{ found }} Is no.
This is what stops duplicates. If someone changes a deal from Won to Negotiation and back to Won, the trigger fires twice. Google would treat the second row as a new conversion, because its time is different, so the workflow must not write it. The duplicate rows guide explains the find-then-add pattern in more detail.
5. Add the conversion row
On the yes branch of that IF, add Google Sheets → Add row(s) on the conversions spreadsheet, first tab, in Single Row mode. Map each column:
| Column | Value |
|---|---|
| Google Click ID | {{ trim($trigger.gclid) }} |
| Conversion Name | Won deal (typed, exactly as in Google Ads) |
| Conversion Time | {{ substring(now(), 0, 19) }}Z |
| Conversion Value | {{ replace(trim($trigger.deal_value), ",", "") }} |
| Conversion Currency | INR |
| Order ID | {{ $trigger.lead_id }} |
Open Advanced and set Write values to Exactly as written (no formulas). With the default, “Like typing it in”, Google Sheets may turn the time into a sheet date in your locale’s format and the value into a formatted number, and a click ID is stored as you’d expect only by luck. Add new columns only after the last mapped one, because Add row(s) writes by column position.
The value expression strips Indian-style separators: in our test, ” 1,25,000 ” became 125000, and a number cell came through unchanged. An empty value stays empty, which is allowed: Google lists Conversion Value as optional.
6. Record what was sent
After Add row(s), add Google Sheets → Update row on the lead sheet, matching lead_id, and set ads_status to Queued for Google Ads. Your sales team can now see, row by row, which deals have been passed to Google. On that IF’s Else branch (the row already exists), you can set ads_status to Already queued or simply do nothing.

Connect the sheet in Google Ads
With the first few rows in place, connect the conversions spreadsheet. On the Data Manager route, Google’s Google Sheets source guide lists the steps:
- In Google Ads, go to Goals, then Summary, and create a new conversion action (or open the offline action you created).
- Choose Import, then CRMs, files, or other data sources, and the tracking method.
- Connect a new data source, search for Google Sheets and select Direct connection.
- Select Conversions as the use case, accept the customer data policy, sign in to Google Drive and allow access.
- Select the conversions spreadsheet.
- Map the fields: your Google Click ID column to the click ID field, Conversion Time to the conversion date and time, and Value and Order ID to theirs. Check the time transformation and set a fallback time zone as a safety net.
- Name the connection and save it, then set its schedule. Data Manager runs scheduled imports at most once a day; because the workflow writes rows as deals close, the sheet is always up to date before the run.
On the legacy route, go to Goals → Conversions → Uploads, open Schedules, choose Google Sheets as the source, link the spreadsheet, pick a frequency and time, and save. Use the +0000 time expression on this route.
Test before you rely on it
- Use a real recent click. Find a lead from the last few days with a GCLID, ideally one that truly converted. A made-up click ID will be rejected.
- Change its status to Won in the lead sheet and check the run in WorkflowMitra: the IF steps should take the yes branches, and the conversions sheet should have one new row with the exact GCLID, a
…Ztime and the Order ID. - Change the status away and back. The Find row check should stop a second row.
- Try a Won lead with no GCLID. It should be marked “Not imported: no click ID” and never reach the conversions sheet.
- Run the import manually in Google Ads and read the result. Google says conversions can take 24 to 48 hours to fully appear in reports, and a click that is less than a day old may not be recorded yet; the next run reads it again, because each run reads the last 90 days.
Our guide to testing an automation workflow has a wider checklist.
Timing, duplicates and what Google ignores
- Re-reading old rows is expected. Each scheduled run reads the last 90 days, so last week’s rows are read again tomorrow. Google says it won’t count duplicate conversions, judged by the conversion action, the time and the click ID, and the legacy upload report names the duplicates. That’s normal noise, not a fault.
- Rows older than 90 days stop mattering. You can archive them to another spreadsheet every quarter to keep the sheet small.
- Edits to a row after import don’t change the conversion. To correct a value or retract a sale, use Google’s conversion adjustments, not an edit in the sheet.
- A new conversion action needs four to six hours before its first import, according to Google’s GCLID guide.
If your leads live in a CRM
The same pattern works when the status lives in a CRM rather than a sheet. Replace the Sheets trigger with an On webhook call trigger and point your CRM’s stage-change webhook at it, or use your CRM’s own trigger in WorkflowMitra where one exists. Zoho CRM’s webhooks, for example, need Zoho’s Professional edition or higher. The CRM must store the GCLID in a field on the lead, deal or contact, and the workflow reads it from the webhook payload instead of $trigger.gclid. Everything after the trigger stays the same. CRM automation covers stage-change triggers more broadly.
Add email and phone for enhanced conversions
Google recommends enhanced conversions for leads as the upgrade to click-ID imports. Instead of relying only on the GCLID, Google matches the hashed email address or phone number of the lead. If your lead sheet has them, add Email and Phone columns to the conversions sheet and map them in Data Manager. Data Manager normalises and SHA-256 hashes them for you, so write them in plain form: email in lower case, and phone in E.164 format such as +919876543210, with no spaces or dashes. Turn on enhanced conversions in your Google Ads account first, following Google’s guide.
Keep these columns only in a sheet that just the people who need it can open. Hashing protects the data on its way to Google; it doesn’t protect the spreadsheet.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Rows not imported, no clear error | No time zone in the value and no fallback time zone in Data Manager | Use the …Z expression and set a fallback time zone |
| Whole import fails on dates | A DD/MM date in the time column | Write year-first ISO text, values "exactly as written" |
| Rows rejected for their click ID | GCLID changed on the way (case, spaces, truncated), or the click is from another account | Copy it exactly; trim spaces; check the hidden field |
| Same sale counted twice | Status changed twice, two rows with different times | Find row on Order ID before Add row(s) |
| Conversions missing for long sales cycles | Click older than 90 days at conversion time | Import an earlier milestone as its own action |
| Data Manager ignores rows | Data is on the second tab, or headers aren't in row 1 | One spreadsheet per action, data on the first tab |
| Value missing or wrong in reports | ₹ sign or commas in the value | Write digits only (the replace expression) |
| Workflow never runs | Trigger watches a different column or tab | Re-check Run when… and the ticked column |
What it costs
| Step | Credits per run |
|---|---|
| When a sheet row changes (each status change) | 1 |
| IF steps | 0 |
| Find row, Add row(s), Update row | 1 each, only on the branches that run |
A won deal with a click ID costs 4 credits: the trigger, Find row, Add row(s) and Update row. A status change that isn’t “Won” costs 1. Plans and credit prices are on the WorkflowMitra pricing page.
What this setup can’t do
- It can’t create a click ID. Leads without a GCLID can’t be matched by click; collect email and phone for enhanced conversions instead.
- It doesn’t report Google’s import result back. WorkflowMitra writes the sheet; Google Ads shows whether each run succeeded in its upload or connection history. Check it weekly at first.
- It isn’t instant. Data Manager runs at most daily, and conversions can take 24 to 48 hours to appear. That’s fine for bidding, which works on trends, but don’t expect a sale to show up in the dashboard within the hour.
- There’s no built-in Google Ads step. The workflow talks to Google Sheets, and Google Ads reads the sheet. If you need to call the Data Manager API directly, that needs your own developer setup.
Feed Google the sales it can’t see
Offline conversion import is how Google Ads learns which clicks became customers. Since 2026, the low-maintenance way to do it is a Google Sheet that Google reads on a schedule. The sheet only works if every row is right: an exact click ID, a time with a time zone and no DD/MM dates, a unique Order ID, no rows without a click ID, and nothing older than the click window can carry.
WorkflowMitra, powered by ChatMitra, keeps that sheet right without anyone copying rows. It watches the lead sheet or CRM, checks each Won deal, formats the time and value, prevents duplicates and marks what was sent, with IF steps that cost no credits. If your CRM already has a native Google Ads offline-conversion integration that you trust, use it. This approach fits teams whose sales data lives in sheets or in tools without one.
Build it on a WorkflowMitra trial: 14 days, 10,000 credits, no card needed. To do the same for Meta campaigns, see Meta Conversions API offline conversions, and for the sheet side, the Google Sheets automation guide. If your leads also reach you on WhatsApp, ChatMitra handles that channel.
Sources: Google Ads Help, About offline conversion imports, Set up offline conversions using GCLID, Import conversions using files (legacy), Google Sheets (Data Manager source) and Data Manager with enhanced conversions for leads; Google Ads Data Manager Help, Prepare your data for import and Manage your connections; Google for Developers, Google Ads API deprecations, all read on 19 October 2026. WorkflowMitra behaviour was checked against the product's source code on that date (Google Sheets trigger and operations, Write values option, Find row output, IF operators, credit rates); the time and value expressions were executed in the product's workflow engine. Google Ads screens were not opened from a live account, so menu names follow Google's help pages. The leads, values and IDs are examples.
Frequently Asked Questions
Short answers to common questions about importing offline conversions into Google Ads from Google Sheets.
Yes. Google Ads can read a Google Sheet on a schedule in two ways: a Data Manager connection, which Google now recommends, and the older scheduled upload under Conversions, Uploads, Schedules, which Google labels legacy. Data Manager schedules run at most once a day. Either way, something still has to add a correct row to the sheet for every sale, which is the part a workflow automates.
Automate the work between your apps
Build workflows with triggers, conditions and actions, then test them before they go live. Try WorkflowMitra free for 14 days, no card required.
