Enhanced conversion upload process?

[ppcwithyrv]

You don’t need to pre-hash in Google Sheets — Google does it for you.

Use YYYY-MM-DD HH:MM:SS for conversion time and don’t worry about timezone; it uses your account setting.

[SeriesOutrageous1832]

Yeah, the template is way more confusing than it needs to be. If you’re using Google Sheets, you don’t have to pre-hash anything Google handles that part. For conversion time, just use YYYY-MM-DD HH:MM:SS. You don’t actually enter a timezone anywhere, it just uses whatever your Google Ads account is set to. Took me a bit to figure that out too.

[paul_944]

The supported timezones list is at [https://developers.google.com/google-ads/api/data/codes-formats#timezone_ids](https://developers.google.com/google-ads/api/data/codes-formats#timezone_ids), should be used instead of `insert_timezone` (a 4-digit offset with sign should work too)

Or you can use Able CDP or something similar, which would also handle things like retrieving associations between caller numbers and click IDs from CallRail and sending these GCLIDs to Google for phone-only CRM conversions

[ernosem]

Time zone should be the first line of the CSV like:
Parameters:TimeZone=America/Chicago;
Then sample conversion time:
2025-12-17 09:03:00

so essentially YYYY-MM-DD HH:MM:SS

It’s in ISO format not the US date format.

[Hannah_Mitchell_2082]

yeah google’s docs make this way harder than it needs to be. this matters since one wrong format or hash kills match rates, i set this up for offline sales at a b2b saas and lost a day to the same timezone confusion. do this: hash email or phone with sha256 lowercase trimmed no spaces, set conversion time like 2025 01 15 14 30 00 plus 05 30, timezone goes inside that timestamp not a separate field, the parameters line is just a comment. benchmark wise 30 to 60 percent match rate is normal for clean crm data.