(Conversion API) Google Ads Offline Conversions API

Follow
Avatar
Jonathan Chen
Updated
Conversion Postbacks for Web, PC, and Console events are only available to Singular customers with access to Singular’s Web, PC, and Console game attribution.

Singular’s integration with the Google Ads Offline Conversions API (also known as uploadClickConversions) allows advertisers to send Singular attributed Google Ads click conversions to Google.  This integration is supported for Singular web, PC, and console measurement.  For Singular’s mobile measurement integration with Google Ads, see our help center article on the topic.

How to Configure the Google Ads Offline Conversions API Integration

  1. Ensure you have an integrated web, PC, or console app with Singular
  2. Go to Singular > Attribution > Partner Configuration
  3. Click "Add a Partner", and type and choose "Google Ads Offline Conversions API (S2S)"
  4. Add or select an existing user to authorize Singular
  5. In the dialog, choose your App and App site (platform) to configure. Note that only web, PC, and console apps are supported with this integration
  6. Enter in your Google Ads' Customer ID under "Customer ID". You can find your customer ID in the top-right corner of your Google Ads dashboard. Hyphens are not required.
     
    If you have multiple Google Ads accounts running campaigns for your app, it is required to use the "Customer ID" from a manager (MCC) account via cross-account conversion tracking using a manager (MCC) account. See Google's help center article for a guide to configuring your MCC account.
  7. For PC and Console apps only: In your Google Ads account, create a Conversion Action for the "Install". Copy and paste the created "Install Conversion Action ID". 
  8. In your Google Ads account, create a Conversion Action for any other events you would like to send and map each event to the corresponding "Conversion Action ID".
  9. Click "Save" to finish.

FAQ

How do you create a Conversion Action for the Google Ads Conversions API?
  1. Click on "New conversion action"


  2. Select "Import"


  3. Select "Manual import using API or uploads" -> "Track conversions from clicks"

    Note: You may not see the "Manual import using API or uploads" option in an MCC account. In this case, continue creating the Conversion Action by selecting "Other data sources or CRMs", "Track conversions from clicks", and "Skip this step and set up a data source later"

  4. Continue through Google’s prompts to configure the Conversion details. Click "Create and Continue" when finished

  5. Back in the "Conversion Goals" page, find the conversion action you just created and click on it to view the details


  6. In the Conversion Action "Details" page, copy the "Conversion Action ID" from the URL parameter "ctId="



  7. Paste this "Conversion Action ID" in your Singular partner configuration when prompted to enter the "Conversion Action ID"
How do you create a Conversion Action for the Google Ads Conversions API (updated UI)?
  1. Click Create > "New conversion action"


  2. If not already selected, select Conversions offline > Continue
  3. If you haven't set up any Offline Conversions yet, you may see this screen. Select "Skip this step and set up the Data Source later". 
  4. Select the standard conversion action you want to measure.
  5. Click "Add an event to this category" > "Offline data sources"
Important The App Install conversion action should not be used in this integration. You should create a new conversion action for your Web to App Install using one of the Conversions Offline conversion actions.
  1. Next to the conversion action that was just added, click Settings
  2. Change the name of your conversion action to your desired conversion action name, and update the conversion action settings to align with your desired measurement and optimization goals for this event. Then click Save. 
  3. Click Save and Continue
  4. Click Finish
  5. You should now see your conversion action in the Summary screen. The Conversion source should be "Website (Import from clicks)". It is normal for the status to be Inactive until you've completed the full setup and Singular starts sending attributed events to Google.
  6. Click on the conversion action, then copy the ctld value from the url browser address bar
  7. Add the ctld value to your Singular Google Ads Web event partner configuration
What data does Singular send via Offline Conversions API?
Parameter Details
gclid, gbraid (coming soon), wbraid (coming soon)
  • automatically passed
hashed email
  • Optional
  • Hashed email may be passed as a Singular instrumented event attribute "ehash"
  • Hashed email value must be normalized and SHA 256 hashed
hashed phone number
  • Optional
  • Hashed phone number may be passed as a Singular instrumented event attribute "phashE164"
  • Hashed phone number must be E164 normalized and SHA 256 hashed
Postbacks are failing on "USER_PERMISSION_DENIED"

This error happens if your authorized user doesn't have permissions to the configured MCC account.

To fix it, go to your Google Ads account, and make sure that your authorized user in Singular has full permissions to the configured MCC account.

Postbacks are failing on "CUSTOMER_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS"

This error happens if you didn't agree to Google's enhanced conversions processing terms.

To fix it, go to your Google Ads account, enter Settings in the side menu, choose under "Goals" the "Conversions" screen, and turn on the Enhanced Conversions for leads as shown below:

For more details, see the Google Ads documentation here.

What are the limitations of Google Ads Offline Conversions API?
  • Supports click conversions only
  • Modelling is not supported
Are mobile events supported in Google Ads Offline Conversions API?
  • Google OCI postbacks should only be configured for mobile app sites to send app events when using Singular's Mobile Web to App attribution flow (i.e. Google ad click → Advertiser owned Landing Page with Singular Web SDK → Singular Mobile Web to App click → Install)
  • If a direct ad click to store flow is leveraged in your Google web campaigns (i.e. Google ad click → app store), use the Google Ads Web integration instead
  • This integration should not be used for standard mobile app install and retargeting campaigns. Use the Google Ads Mobile App Campaigns Integration for mobile campaigns.