Short answer
To import conversions through the native Google Ads call-import route, confirm eligibility and prepare the official template with the required data. Review a small batch and reconcile processed rows, errors and retries; this route differs from a GCLID-based upload.
Key verification: Check that a confirmed sale is imported once into the correct conversion action.
Sources and limitationsTo import call conversions into Google Ads, first identify which calls are eligible, create the corresponding action, and prepare the official template with the caller number and call start. Then review which rows have been processed and reconcile them with your sales record. The following guide uses the native import call path.
Part of a confirmed business result, such as an accepted order. If you're still deciding which call ended up on sale, complete the CRM attribution record first. Here the deliverable is a verified upload within Ads.
Check which method corresponds to your data
Native import requires calls that Google can relate to your measurement using forwarding numbers and a supported configuration. It is not used to indiscriminately increase the sales received by your usual telephone. See the origin and country requirements in the official description of importing calls .
An integration that preserves a GCLID or uses enhanced lead conversions can take another path. In 2026 Google documents changes from offline imports to Data Manager. Before hiring automation, identify the method it uses and its current support. Offline imports and interface updates .
Inventory fields. An opportunity reference and amount may be sufficient for your internal reporting, but they are not a substitute for the identifiers required by your chosen upload method. Keep transactions without association data separate and record the reason.
Define the action and what result it will represent
Use a stable name and a written definition. For example, "order confirmed by call" may mean an order accepted by the customer, with an agreed amount and currency. Don't change that definition between files to increase volume.
Top actions can be used in bidding if their objective is used for optimization; The secondary ones are normally used for observation. Actions included in a custom objective can be used in bids even if they are secondary. Also review the objectives of each campaign. Primary and secondary actions .
During validation, separates the sell signal from a previous duration-based conversion. Decide which business objective you want to optimize and document the change. A sum of long conversations and orders alone does not represent the number of sales.
Prepare the fields of the official template
| Column | Data you must check |
|---|---|
| Caller's phone number | Caller's phone number, in a supported format |
| Call start time | Call start, with correct time and time zone |
| Conversion name | Exact name of the created action |
| Conversion time | Result date; optional field |
| Conversion value | Defined value for that result; optional field |
| Conversion currency | Currency of the value; optional field |
Download the template from Conversions → Uploads and keep its headers. Google details the formats, time zone, and a minimum wait of four hours after creating the action before the first import. Template and upload instructions .
Fictitious example of your control record: opportunity OP-018, call LL-041 started on September 24 at 10:15 in Europe/Madrid, order confirmed on September 26, value 420 EUR. The operational file would use the actual verified number. These internal references serve to reconcile; They are not columns that you should automatically add to the template.
Check a small batch before repeating the process
- Select actual and eligible results with evidence of closure.
- Check the target count, action, and format of each row.
- Store a copy of the batch and its commercial references in an authorized place.
- Use the available preview and check for errors before applying the upload.
- Queries the processed result and records the accepted and rejected rows.
The telephone numbers in the file are identifying data. Limit access and use only the data required by the authorized method and processing. A CSV open to the public for easy upload would also expose that data.
Reconcile quantities, errors, and retries
Fictional example: Your selection has ten sales, two without an eligible call and eight candidates. The processing reports six accepted and two with errors. The control should show the ten original sales, the two excluded by method, and the status of the eight candidates. “Six conversions” does not prove that four sales were lost.
Review the specific reasons for rejection: account, phone, time zone or applicable window. Google indicates a maximum window of 90 days for this import, configurable in the action. Call import errors .
Save the batch, date, result and next intervention. Prevents two connectors from handling the same action without a shared rule. Automate when you can explain how each conversion is identified and how to recover from an error without rebuilding the entire history.
Sources and limitations
Documentary review: . Content type: Procedure with fictional example.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- official description of importing callssupport.google.com
- Offline imports and interface updatessupport.google.com
- Primary and secondary actionssupport.google.com
- Template and upload instructionssupport.google.com
- Call import errorssupport.google.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
HubSpotOfficial plan catalogueThese links lead to official pages without affiliate identifiers. We do not yet have an active affiliate link for these options. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.