Google Ads
by Google
Google Ads keeps campaign, ad group, keyword and search term data for Search, YouTube, Display, Shopping and Performance Max, along with clicks, cost and conversions. Those conversions are only as reliable as the tag that fires them. With the same data in your own Lake, clicks and cost meet CRM deals and booked revenue, so bids can follow profit instead of form fills.
- Category
- Advertising
- Type
- Search ads
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0
02Data
What you can sync.
- Campaigns
- Ad groups
- Keywords
- Search terms
- Campaign stats
- Conversions
Put Google Ads campaigns beside revenue from your own systems, and let DataPrism BI and AI Minds show which campaigns pay back.
Need more? Name any other Google Ads data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
Google Ads uses OAuth 2.0 (client ID, client secret, refresh token). You add the credentials once, when the AI asks for them, and it tells you where to create them in Google if you need help.
04Questions
Questions you can answer.
Once Google Ads data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- Which search terms produce leads that become closed-won deals within 90 days, and at what cost per deal?
- What share of spend goes to branded keywords, and how do those clicks compare with organic clicks for the same queries?
- Which keywords have rising cost per click but flat conversion rate over the last quarter?
- What is cost per acquired customer by campaign when conversions come from orders rather than the Google tag?
- Which search terms should become negatives because they spend without ever producing a sale?
05How it works
How it works in DataMind.
-
Pick Google Ads.
Open Lake, pick Google Ads in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Google Ads API docs.
-
Answer a few questions.
The AI reads the Google Ads documentation, then asks which credentials you will use, which data to sync (for example campaigns and ad groups), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Google Ads data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Write back
Write data back to Google Ads.
Send call conversions, conversion adjustments and ad group ads from your Lake and Warehouse to Google Ads, on a schedule or when you run it. The AI reads the Google Ads API docs, asks you a few questions and builds the destination with you.
Write to Any API
What you can send.
- Call conversions
- Conversion adjustments
- Ad group ads
- Ad group bid modifiers
- Ad group criteria
- Ad groups
- Ads
- Asset groups
A sync can create Google Ads records from your rows and update the ones it finds by a key you choose.
Once you turn deletes on, it can also mark or delete the records whose rows left the source.
Send call conversions from the Warehouse to Google Ads on a schedule, so targeting follows the customers your own data picks.
Credentials
Credentials for writes.
- OAuth 2.0 (client ID, client secret, refresh token)
- A service account key
Google Ads takes OAuth 2.0 (client ID, client secret, refresh token) or a service account key for writes. You add the credentials once, when the AI asks for them, and it tells you where to create them in Google if you need help.
-
Add Google Ads in Writeback.
Open Writeback, click Add destination, choose Write to Any API and name the destination. Then tell the AI it sends to Google Ads and point it at the Google Ads API docs.
-
Answer a few questions.
The AI reads the Google Ads documentation, then asks which credentials you will use, which Google Ads objects to fill (for example call conversions and conversion adjustments) and whether to create, update or delete records.
-
Preview, test, then send.
Choose a Lake table, a Warehouse table or your own SQL, map the fields and preview the requests. Send one test record, approve the first run, and the sync keeps Google Ads current on your schedule.
07Pairs
Works well with Google Ads.
Sources teams join with Google Ads in the Warehouse, each one connected the same way.