Google Ads · Advertising data
Google Ads reporting prepared for project-level analysis
Connect approved Google Ads beta access to discover accounts, select campaigns, and analyze Search, Shopping, Performance Max, and other campaign types by project.
For ecommerce teams and agencies that need Search, Shopping, Performance Max, and other campaign types catalogued by project.
Once external API access is approved, Google campaign data will use the same source and campaign analysis model as Meta Ads.
The integration is available to private-beta accounts with Google Ads API access approved for the configured KPIAds credentials.
What it adds
One source, kept inside the right project
- 01
Keep each Google Ads customer and its selected campaigns attached to the correct project.
- 02
Preserve campaign type and subtype so Search, Shopping, and Performance Max can be analyzed correctly.
- 03
Use one Google OAuth connection to discover the accessible advertising accounts without sharing a password.
Data scope
Know what enters KPIAds before you connect
KPIAds limits each connector to the data required for project-level ecommerce performance reporting.
Data used for reporting
- Customer account, campaign identifiers, names, types, and subtypes
- Spend, impressions, clicks, conversions, and attributed conversion value
- Derived CTR, CPC, CPM, CPA, and provider-attributed ROAS
Not collected for this scope
- Your Google account password
- Store customer records or raw ecommerce orders
- Campaign editing or automated budget changes in the current scope
Before setup
Compatibility and requirements
- OAuth scope
- Google Ads read access
- Campaign assignment
- Multiple per project
- Current scope
- Read-only reporting
- External dependency
- Google Ads API approval
What you need
- Google Ads API production access must be approved for KPIAds.
- The connecting Google user must have access to the required Ads customer account.
- A KPIAds project with capacity for the advertising property.
Connection flow
Guided setup without shared passwords
- 1
Wait until Google Ads API production access is enabled for KPIAds.
- 2
Authorize KPIAds with a Google user that can access the required Ads account.
- 3
Choose the customer account and assign it to the intended project.
- 4
Select the campaigns for that project and start reporting sync.
Questions
What teams usually need to confirm
Does every KPIAds user need a developer token?
No. KPIAds owns and operates the application credentials and developer token. Each user only authorizes access to the Google Ads accounts they are allowed to use.
Are different Google campaign types preserved?
Yes. The data model catalogues campaign type and subtype so Search, Shopping, Performance Max, Video, and other formats are not presented as identical campaigns.
Can I connect Google Ads today?
Not in the public beta. The internal implementation is ready, but production use depends on Google approving KPIAds for the required Ads API access.