LogoLogo
  • 🦩Overview
  • 💾Datasets
    • Overview
    • Core Concepts
      • Columns & Annotations
      • Type & Property Mappings
      • Relationships
    • Basic Datasets
      • dbt Integration
      • Sigma Integration
      • Looker Integration
    • SaaS Datasets
    • CSV Datasets
    • Streaming Datasets
    • Entity Resolution
    • AI Columns
      • AI Prompts Recipe Book
    • Enrichment Columns
      • Quick Start
      • HTTP Request Enrichments
    • Computed Columns
    • Version Control
  • 📫Syncs
    • Overview
    • Triggering & Scheduling
    • Retry Handling
    • Live Syncs
    • Audience Syncs
    • Observability
      • Current Sync Run Overview
      • Sync History
      • Sync Tracking
      • API Inspector
      • Sync Alerts
      • Observability Lake
      • Datadog Integration
      • Warehouse Writeback
      • Sync Lifecycle Webhooks
      • Sync Dry Runs
    • Structuring Data
      • Liquid Templates
      • Event Syncs
      • Arrays and Nested Objects
  • 👥Audience Hub
    • Overview
    • Creating Segments
      • Segment Priorities
      • Warehouse-Managed Audiences
    • Experiments and Analysis
      • Audience Match Rates
    • Activating Segments
    • Calculated Columns
    • Data Preparation
      • Profile Explorer
      • Exclusion Lists
  • 🧮Data Sources
    • Overview
    • Available Sources
      • Amazon Athena
      • Amazon Redshift
      • Amazon S3
      • Azure Synapse
      • ClickHouse
      • Confluent Cloud
      • Databricks
      • Elasticsearch
      • Kafka
      • Google AlloyDB
      • Google BigQuery
      • Google Cloud SQL for PostgreSQL
      • Google Pub/Sub
      • Google Sheets
      • Greenplum
      • HTTP Request
      • HubSpot
      • Materialize
      • Microsoft Fabric
      • MotherDuck
      • MySQL
      • PostgreSQL
      • Rockset
      • Salesforce
      • SingleStore
      • Snowflake
      • SQL Server
      • Trino
  • 🛫Destinations
    • Overview
    • Available Destinations
      • Accredible
      • ActiveCampaign
      • Adobe Target
      • Aha
      • Airship
      • Airtable
      • Algolia
      • Amazon Ads DSP (AMC)
      • Amazon DynamoDB
      • Amazon EventBridge
      • Amazon Pinpoint
      • Amazon Redshift
      • Amazon S3
      • Amplitude
      • Anaplan
      • Antavo
      • Appcues
      • Apollo
      • Asana
      • AskNicely
      • Attentive
      • Attio
      • Autopilot Journeys
      • Azure Blob Storage
      • Box
      • Bloomreach
      • Blackhawk
      • Braze
      • Brevo (formerly Sendinblue)
      • Campaign Monitor
      • Canny
      • Channable
      • Chargebee
      • Chargify
      • ChartMogul
      • ChatGPT Retrieval Plugin
      • Chattermill
      • ChurnZero
      • CJ Affiliate
      • CleverTap
      • ClickUp
      • Constant Contact
      • Courier
      • Criteo
      • Crowd.dev
      • Customer.io
      • Databricks
      • Delighted
      • Discord
      • Drift
      • Drip
      • Eagle Eye
      • Emarsys
      • Enterpret
      • Elasticsearch
      • Facebook Ads
      • Facebook Product Catalog
      • Freshdesk
      • Freshsales
      • Front
      • FullStory
      • Gainsight
      • GitHub
      • GitLab
      • Gladly
      • Google Ads
        • Customer Match Lists (Audiences)
        • Offline Conversions
      • Google AlloyDB
      • Google Analytics 4
      • Google BigQuery
      • Google Campaign Manager 360
      • Google Cloud Storage
      • Google Datastore
      • Google Display & Video 360
      • Google Drive
      • Google Search Ads 360
      • Google Sheets
      • Heap.io
      • Help Scout
      • HTTP Request
      • HubSpot
      • Impact
      • Insider
      • Insightly
      • Intercom
      • Iterable
      • Jira
      • Kafka
      • Kevel
      • Klaviyo
      • Kustomer
      • Labelbox
      • LaunchDarkly
      • LinkedIn
      • LiveIntent
      • Loops
      • Mailchimp
      • Mailchimp Transactional (Mandrill)
      • Mailgun
      • Marketo
      • Meilisearch
      • Microsoft Advertising
      • Microsoft Dynamics
      • Microsoft SQL Server
      • Microsoft Teams
      • Mixpanel
      • MoEngage
      • Mongo DB
      • mParticle
      • MySQL
      • NetSuite
      • Notion
      • OneSignal
      • Optimizely
      • Oracle Database
      • Oracle Eloqua
      • Oracle Fusion
      • Oracle Responsys
      • Orbit
      • Ortto
      • Outreach
      • Pardot
      • Partnerstack
      • Pendo
      • Pinterest
      • Pipedrive
      • Planhat
      • PostgreSQL
      • PostHog
      • Postscript
      • Productboard
      • Qualtrics
      • Radar
      • Reddit Ads
      • Rokt
      • RollWorks
      • Sailthru
      • Salesforce
      • Salesforce Commerce Cloud
      • Salesforce Marketing Cloud
      • Salesloft
      • Segment
      • SendGrid
      • Sense
      • SFTP
      • Shopify
      • Singular
      • Slack
      • Snapchat
      • Snowflake
      • Split
      • Sprig
      • Stripe
      • The Trade Desk
      • TikTok
      • Totango
      • Userflow
      • Userpilot
      • Vero Cloud
      • Vitally
      • Webhooks
      • Webflow
      • X Ads (formerly Twitter Ads)
      • Yahoo Ads (DSP)
      • Zendesk
      • Zoho CRM
      • Zuora
    • Custom & Partner Destinations
  • 📎Misc
    • Credits
    • Census Embedded
    • Data Storage
      • Census Store
        • Query Census Store from Snowflake
      • General Object Storage
      • Bring Your Own Bucket
        • Bring your own S3 Bucket
        • Bring your own GCS Bucket
        • Bring your own Azure Bucket
    • Developers
      • GitLink
      • Dataset API
      • Custom Destination API
      • Management API
    • Security & Privacy
      • Login & SSO Settings
      • Workspaces
      • Role-based Access Controls
      • Network Access Controls
      • SIEM Log Forwarding
      • Secure Storage of Customer Credentials
      • Digital Markets Act (DMA) Consent for Ad Platforms
    • Health and Usage Reporting
      • Workspace Homepage
      • Product Usage Dashboard
      • Observability Toolkit
      • Alerts
    • FAQs
Powered by GitBook
On this page
  • Connect your Google Ads Account
  • Supported Objects and Sync Behaviors
  • Sync Offline Click and Call Conversions with Census
  • 1. Create or find your custom conversion event in Google Ads
  • 2. Create your Census Model for the Conversion Action
  • 3. Create your Sync
  • 4. Confirm the conversions are now in Google Ads
  • Sync Enhanced Conversions with Census
  • 1. Create or find your custom conversion event in Google Ads
  • 2. Create your Census Model for the Conversion Action
  • 3. Create your Sync
  • 4. Confirm the conversions are now in Google Ads
  • Conversion Adjustments
  • Digital Markets Act (DMA)

Was this helpful?

  1. Destinations
  2. Available Destinations
  3. Google Ads

Offline Conversions

Optimize your ad spend to find your best leads and customers.

PreviousCustomer Match Lists (Audiences)NextGoogle AlloyDB

Last updated 1 month ago

Was this helpful?

Connect your Google Ads Account

Follow the

Supported Objects and Sync Behaviors

Object

Behaviors

Identifier

Click Conversion

Update or Create

Click ID, WBRAID, GBRAID

Call Conversion

Update or Create

Caller ID

Enhanced Conversion

Update or Create

Order ID

Conversion Adjustment

Send

N/A

Sync Offline Click and Call Conversions with Census

1. Create or find your custom conversion event in Google Ads

  1. Create a new conversion action.

  2. Select the data source for this conversion action as Import.

  3. Select Other data sources or CRMs.

  4. Select Track conversions from clicks or Track conversions from calls.

  5. Under the Data Source section you can select Skip this step and set up a data source later

  6. Enter a name for the conversion action that you're creating. Hold onto this name exactly as entered -- spelling and capitalization will be important when syncing these conversions via Census!

  7. Complete the set-up for this conversion event, selecting your desired conversion window (we recommend using the maximum 90-days) and ads attribution model.

Important: After creating a new conversion action, Google recommends waiting 6 hours before syncing conversions for that conversion action. If you sync conversions during the first 6 hours, it can take two days for those conversions to appear on your reports.

2. Create your Census Model for the Conversion Action

Here you can write SQL queries that contain the conversion action you want to send to Google Ads.

Google Ads Offline Click and Call Conversions require a specific set of properties. We'll want a model that has the following three required fields:

  • One of: the Google Click ID (also often known as the gclid), WBRAID, or GBRAID value.

  • The Conversion Name, spelled exactly as it is found in Google Ads

  • The Conversion Timestamp, with timezone specified -- either using your warehouse's "timestamp with timezone" datatype, or hard-coded in a string (e.g. '2021-03-04 09:23:57+0000').

Optional properties include:

  • Order ID, a unique reference in your systems for this conversion action

  • Conversion Value, positive non-zero decimal values accepted (e.g. 1.00 USD = 1.00)

  • External Attribution Credit and Model, calculated outside Google Ads

Once you have created your model, click save.

3. Create your Sync

In the "What data do you want to sync?" section

  • For the Connection, select the data warehouse you connected in the Prerequisites Step 2

  • For the Source, select the model you created in step 2 of this section

Next up is the "Where do you want to sync data to?" section

  • Pick Google Ads as the Connection

  • For Object, pick Click Conversion or Call Conversion

For the "How should changes to the source be synced?" section

  • Send will be selected by default

  • Pick the right mapping key, the Google Click ID in your model

Finally, select the fields you want to update in the Mapper in the "Which Fields should be updated?" section. Here simply map the fields from your model to the properties of the Click or Call Conversion.

The end result should look something like this:

Click the Next button to see the final preview which will have a recap of what will happen when you start the sync.

4. Confirm the conversions are now in Google Ads

Sync Enhanced Conversions with Census

Essentially, Google will compare the person's email or phone number to its database of Google users and ad clicks, and give credit for the Conversion to an ad campaign when it finds a match.

1. Create or find your custom conversion event in Google Ads

2. Create your Census Model for the Conversion Action

Here you can write SQL queries that contain the conversion action you want to send to Google Ads, plus the data Google needs to track the conversion via the Enhanced Conversion mechanism.

Google Enhanced Conversions require a specific set of properties.

A. Minimum Conversion Parameters

We'll want a model that has the following three required fields:

  • The Order ID

    • If you are tracking the conversion solely as an Enhanced Conversion, any unique ID will do

    • If you are supplementing existing conversion tracking, use the same Order ID that you're already sending to Google Ads

  • The Conversion Name, spelled exactly as it is found in Google Ads

  • The Conversion Timestamp, __ with timezone specified -- either using your warehouse's "timestamp with timezone" datatype, or hard-coded in a string (e.g. '2021-03-04 09:23:57+0000').

B. User Identifiers

You also must supply user identifier parameters so that Google can match this conversion to its records of users and ad click.

You may choose to use a pre-hashed value (if you have one), or for Census to perform the hashing for you:

  • Email, normalized with the following transformations:

    • Remove leading/trailing whitespaces.

    • Convert the text to lowercase.

    • Remove all periods (.) that precede the domain name in gmail.com and googlemail.com email addresses.

C. Optional Parameters

  • Google Click ID (recommended)

Once you have created your model, click save.

3. Create your Sync

In the "What data do you want to sync?" section, select the model you created in step 2 of this section, or an existing table that contains this data.

Next up is the "Where do you want to sync data to?" section

  • Pick Google Ads as the Connection

  • For Object, pick Enhanced Conversion

Finally, select the fields you want to update in the Mapper in the "Set Up Field Mappings" section. Here simply map the fields from your model to the properties of the Enhanced Conversion.

The end result should look something like this:

Click the Next button to see the final preview which will have a recap of what will happen when you start the sync.

4. Confirm the conversions are now in Google Ads

Conversion Adjustments

A conversion adjustment requires exactly one of the following sets of properties in order to identify which conversion to adjust.

  • Order ID or

  • Google Click ID (GCLID) and exact conversion date time

Digital Markets Act (DMA)

Learn more about all of our sync behaviors in our documentation.

if you want Census to support more Google Ads objects and/or behaviors

Google Ads has extensive documentation on . The main steps are:

Choose your for the conversion action, either One conversion or Every conversion. Many offline conversions occur only once (e.g. "Reached onboarding milestone X"). In this case, select the counting option One conversion to protect yourself from accidentally syncing duplicate conversions.

Navigate to the page.​

Currency Code, the (e.g. 'USD')

Now head to the and click the Add Sync button

It may take around 3 hours for synced offline conversions to show up in your Google Ads account. When they do, they'll appear in reporting on these conversion actions. To learn more about reporting on these conversions, you may wish to visit .

Google Ads also supports conversion tracking on the web if you only know your prospect or customer's email or phone number, using . These conversions can be used in place of, or as a supplement to, Click Conversions.

Setting up a conversion in Google Ads is . However, Enhanced Conversions require slightly different data points so that Google can match a person to your conversion, and avoid duplication if you also track this conversion using other methods.

Navigate to the page.​

Phone Number, formatted to the .

Currency Code, the (e.g. 'USD')

Important: Any Conversion Value mapped here will be ignored by Google. If you want to adjust these values, create a separate sync with as the object.

Now head to the and click the Add Sync button

It may take around 3 hours for synced offline conversions to show up in your Google Ads account. When they do, they'll appear in reporting on these conversion actions. To learn more about reporting on these conversions, you may wish to visit .

Once a conversion has already been reported to Google Ads, you can at a later point in time using Census.

When syncing Conversions to Google Ads, you can include consent information to ensure compatibility with . Google Ads objects now support two additional fields: Consent for ad user data and Consent for ad personalization, which can be set to one of the following values: UNKNOWN, UNSPECIFIED, GRANTED, DENIED. See Google's for more information on the behavior of different options.

🛫
Syncs
Contact us
creating offline conversion events
counting option
Models
ISO 4217 3-character currency code
Sync page
this Google Ads help article
"Enhanced Conversions"
exactly the same as traditional Click Conversions
Models
E164 standard
ISO 4217 3-character currency code
Sync page
this Google Ads help article
adjust the conversion
Google's EU User Consent Policy
documentation
Conversion Adjustments
set-up instructions here!