Google Ads Call Conversions

Track Phone Calls From Google Ads as Offline Conversions

Edesy captures the gclid of every Google Ads click on your website, shows that visitor a tracking number, and matches their phone call to the click. Download the calls as a Google Ads offline-conversion CSV and upload it in Google Ads, so calls count as conversions. It is a CSV export, not an automatic upload.

gclid

Captured per click

30 s

Default minimum call

CSV

Google Ads import format

Rs 0

Tracking fee

gclid, gbraid, wbraid captured

Google Ads import format

IST conversion times

Manual upload, you stay in control

Google Ads call conversion export spec

Click IDs captured gclid, gbraid, wbraid (plus fbclid, msclkid and UTM tags)
In the export Calls on tracking numbers whose visit had a gclid
Minimum call length 30 seconds by default (min_duration, set 0 for every call)
Columns Google Click ID, Conversion Name, Conversion Time, Conversion Value, Conversion Currency
Time zone Parameters:TimeZone=Asia/Calcutta header row; times in IST
Conversion name Set per pool to match your Google Ads conversion action; default Phone call
Conversion value Left blank; add values before upload if you use them
Currency INR
File google-ads-call-conversions.csv, up to 50,000 rows, from the reports page or GET /v1/call-tracking/exports/google-ads.csv?pool_id=...
How it reaches Google Ads You upload the CSV in Google Ads. Edesy does not connect to your Ads account
Not included Automatic upload, GA4 or dataLayer sync, calls with only gbraid or wbraid
Price No tracking fee or export fee. Calls Rs 1.00/min plus number rental

Prices exclude 18% GST.

From ad click to call conversion in Google Ads

Set up once, then export and upload on a schedule

  1. Step 1 of 6: Turn on auto-tagging in Google Ads

    Ad clicks then land on your site with a gclid in the URL.

  2. Step 2 of 6: Create an import conversion action

    In Google Ads, create a conversion action for phone calls imported from clicks, and note its exact name.

  3. Step 3 of 6: Create a pool and install the script

    In forwarding.edesy.in, open Call tracking, create a pool (paid traffic only works well), enter the conversion name and paste the script tag on your site.

  4. Step 4 of 6: Ad visitors see a tracking number

    The script stores the gclid with the visit and shows that visitor their own number.

  5. Step 5 of 6: Calls are matched to the click

    When the visitor calls, the call is forwarded to your team and credited to the visit and its gclid.

  6. Step 6 of 6: Export the CSV and upload it

    On the reports page, download the Google Ads export for the pool and date range, then upload it in Google Ads under offline conversion uploads.

What the file looks like

Parameters:TimeZone=Asia/Calcutta
Google Click ID,Conversion Name,Conversion Time,Conversion Value,Conversion Currency
Cj0KCQiA...,Phone call,2026-11-14 11:42:07,,INR
Cj0KCQiB...,Phone call,2026-11-14 12:05:51,,INR

Each row is one call of 30 seconds or more from a visit that arrived with a gclid. The conversion time is when the call started, in IST, which Google Ads reads from the time zone row.

Why calls with only gbraid or wbraid are not in the file

On some iOS traffic Google sends gbraid or wbraid instead of a gclid. Edesy captures both and shows them on the visit, and they count as paid traffic, but the offline-conversion CSV only carries rows with a gclid. Those calls are still in your reports and calls CSV.

Upload routine

Google Ads only accepts conversions for clicks inside its import window, so export on a regular schedule, for example every Monday for the previous week, and avoid overlapping date ranges.

Export from your own scheduler

The same file is available through the API with your API key, so a weekly cron job can fetch it for you before you upload.

# Last 7 days of Google Ads call conversions for one pool
curl -o google-ads-call-conversions.csv \
  "https://voice-api.edesy.in/v1/call-tracking/exports/google-ads.csv?pool_id=$POOL_ID&min_duration=30&from=2026-11-07T00:00:00%2B05:30&to=2026-11-14T00:00:00%2B05:30" \
  -H "Authorization: Bearer $EDESY_API_KEY"

Why import calls into Google Ads

Bidding works best when it can see the calls your ads produce

Credit the right keyword

Each call is tied to the click, so Google Ads reports calls against the campaign, ad group and keyword that drove them.

Count real conversations

Only calls of 30 seconds or more are exported by default, so hang-ups and wrong numbers don't train your bidding.

Review before you upload

Because it is a file, you can check rows, drop spam calls or add conversion values before Google sees them.

Paid traffic only pools

Show tracking numbers only to ad clicks, so a small pool covers your Google Ads traffic and organic visitors keep your normal number.

Reports beyond Google

The same calls appear in Edesy reports by source, medium, campaign, site and day, with Meta and Microsoft click IDs too.

Webhook per call

call_tracking.call.completed carries the gclid and UTM tags, so your CRM can store the source of every call.

Google Ads call tracking: FAQ

Running Google Ads that drive calls?

Tell us your monthly ad clicks and where calls should ring. We'll help you set up the pool and your first export.

Count phone calls as Google Ads conversions

Capture the gclid, match the call, export the CSV. New accounts get a Rs 20 welcome credit; no card needed. No tracking fee.