Google Data Manager API
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | Ad platform (conversions) | One click: approve bubbl3 on Google Data Manager API's own page |
Google Data Manager API isn't offered yet. This page says what it will do and what you can use meanwhile: a Lead URL, or Zapier, Make or n8n.
What it does
When a lead from your Google ads qualifies, books or buys, bubbl3 can record it as a Google Ads conversion. Each conversion event you choose is sent to a conversion action with:
- the click ids Google gave the lead (
gclid,gbraidorwbraid), when the contact has one; - the event's time, value and currency;
- the contact's email and phone, hashed with SHA-256 before they leave bubbl3.
Setup
You need full access to integrations in bubbl3, and access to the Google Ads account.
- In Google Ads, create an "Import from clicks" conversion action and note its id and your customer id.
- In bubbl3, open Settings, Integrations, choose Google Data Manager API, then Connect, and approve bubbl3 with your Google account.
- In Settings, Events, open an event and add a destination: this connection, the customer id (and manager account, if you use one) and the conversion action id.
Disconnect
Disconnect from the connection page in Settings, Integrations.
- Stops at once: conversion uploads to Google. Deliveries still waiting are not sent.
- Deleted at once: bubbl3's Google tokens (Google is asked to revoke them).
- Kept: your conversion events and their delivery log in bubbl3. Uploaded conversions stay in Google Ads.
Data shared
From bubbl3 to Google: for each conversion: the conversion action, customer, time, value, currency, a transaction id Google uses to drop duplicates, click ids, and SHA-256 hashes of the email and phone. Never the raw email or phone, and never anyone who opted out or has no consent record.
From Google to bubbl3: your Google account's email (to name the connection) and Google's answer to each upload.
Scopes and permissions
| Scope | Why bubbl3 needs it |
|---|---|
openid | Identify the Google account you connected |
email | Name the connection after that account |
https://www.googleapis.com/auth/datamanager | Upload conversions through the Data Manager API |
Events
What bubbl3 receives
Nothing: Google only receives conversions from bubbl3.
What bubbl3 writes back
| What | Where it shows in Google Ads |
|---|---|
| Conversions | An offline conversion on the conversion action you chose |
Sending rules that still apply
Google Data Manager API never causes a text. bubbl3 sends it conversion events only for contacts who haven't opted out and have a consent record, and stops for a contact who opts out later. Emails and phone numbers are hashed with SHA-256 before they leave bubbl3.
Limits and known gaps
- bubbl3 sends no EU consent signals for ad data. If you advertise to people in the EU or EEA, check Google's requirements before turning this on.
- Google allows 300 uploads a minute per project; bubbl3 paces each connection well below that and retries when Google says to.
Troubleshooting
- A delivery failed with a permission error. The Google account you connected can't reach that customer or conversion action. Check the ids and the account's access.
- Conversions don't attribute. They attribute best when the contact carries a Google click id from a lead form or landing page.