Google Ads integration

Google Ads reporting and change history feed the same client record as the store and the other platforms.

Request access All integrations

Google Ads

ROASfinity

Read-only firstWrites only after a yes

Stock photos and example labels, not customers.

How the data moves

From Google Ads to your report. Back only with a yes.

The top row is reading, which is all a new connection does. The bottom row is writing, switched on per account only after you grant the rights.

Google AdsReads reports through GAQL
🔑Token vaultRead-only token, encrypted on the server
One recordStored per client, with currency and time zone kept
▦Your reportSource, formula and sync time on every number
✎ProposalA change such as: mutations on allowed resources, after approval
✓Preview and yesBefore and after, then a person with the right role approves
⎙Written onceAn idempotency key, so a retry cannot repeat the change
↻Read back, loggedGoogle Ads is read again, compared and logged

Read: on by default, read-onlyWrite: off until you grant it, then every change needs approval

Google Ads in daily use

What it reads first

Reports through GAQL

What it can change, after a yes

Mutations on allowed resources, after approval

Photos are stock images. App screens show test data.

In numbers

3things it reads

1things it can change, after approval

2things you need to connect

2limits stated

Google Ads: reads, writes and limits

Reports through GAQL
Statuses
Change events from the last 30 days

Mutations on allowed resources, after approval

Always after preview and approval.

A Google Cloud project with OAuth
A developer token and the right access level (Test, Explorer, Basic or Standard)

Change events cover only the last 30 days.
Access levels and permissible use restrict what can be done.

Before you connect

Your ticks stay in this browser only.

Ask for access through a manager account or a user with reporting rights. Keep the list of people who can change bids and budgets short.
Write down the account time zone and currency. Check that they match the store and the other sources.
List every conversion action in the account. Mark which one the client treats as the sale, and whether it counts every conversion or only some.
Note the attribution model and window the account uses, and the ones the client's own reports use. If they differ, write down both.
Pull one closed month of cost and conversions and compare it with the client's ad invoices and sales records. Make no bid or budget change until the gap is written down.

Common data differences

General practice, not a claim about any one account.

Difference

Conversion actions that count differently

One conversion action can count every sale, another can count only some, and a third can be imported from another source. A total in the account can be right for its own rule and still differ from the store total.

Difference

Late conversions and recent days

Recent days often change after the first report. Conversions can arrive late, and refunds and cancellations come later still. Comparing the last few days with the store will show a gap that is not a real problem. Compare closed periods only.

Difference

Currency and shared budgets

Cost is shown in the account currency, and store revenue may be in another currency. Shared budgets and campaigns that span more than one account split numbers in ways that are hard to match. Confirm the currency on both sides first.

Modules that use Google Ads

Each module page says what it reads and what it will not claim.

Reports

Client, channel, campaign and product reports where every figure shows its source, formula and update time.

Budget allocation

Scenarios for moving budget between campaigns, with limits and a record of expected versus actual.

Change log

Every change with before and after, author, reason, time, API response and what happened next.

Signals

Alerts for inactive accounts, rejected ads, CPM and CPA jumps, weak spend, broken URLs and stale connectors.

AI insights

Checks for drops, anomalies, frequency and missing new creatives, explained with numbers you can verify.

Questions about Google Ads

Is the Google Ads connection read-only?

It starts read-only. Changes are added only where the platform grants the permission, and each one is previewed, approved, sent once, read back and logged.

Where is the token stored?

In an encrypted vault on the server, never in the browser, in logs or in an AI prompt.

Is the Google Ads connector available now?

Not yet. It goes live after the platform access is in place. Request access to be told when it does.