Google Ads

Before you start

• A Google identity authorized for the intended Ads customer accounts and Data Weaver source-management access.
• Have the customer accounts you want to analyze ready to select. If you use a manager account, choose the relevant customers explicitly after authorization.

Set up the connection

1. In the target client's Sources, connect Google Ads and review Google consent.
2. Explicitly select accessible customer accounts and save. Selecting none syncs none.
3. Sync and inspect account readiness. If a selected customer is no longer accessible, update the selection before syncing.

Permissions requested

• Access is needed to discover authorized customers and read campaign reports and account currency. Data Weaver's integration does not create ads, change budgets or edit campaigns.
• Google presents the requested access during authorization. Review the consent screen, approve access and return to Data Weaver to select the customer accounts to include.

Data read and actions performed

• The sync reads a recent 90-day window of daily campaign cost, impressions, clicks, conversions and conversion value, retaining customer/campaign identity and currency.
• Supported scoped questions can request campaign rankings and spend over time. Conversion value is Google's attributed value, not verified store revenue.

Refresh and sync

• Default cadence is hourly; manual Sync is available. Provider quotas and processing delays can postpone refreshes or revise recent attributed results.

Limitations

• Do not blend incompatible account currencies. Ads attribution and GA4 attribution are not interchangeable.
• No complete lifetime backfill is promised. Campaign management and automated budget changes are not supported by this connector.

Troubleshooting

• If customers are missing, confirm direct or manager-linked access for the connected Google identity.
• Check saved selection, currency evidence and sync history. Reconnect for expired authorization; temporary API/quota failures should be retried, not treated as lost consent.

Disconnect and delete

• Remove the connection in Sources to stop Data Weaver access and request remote Nango cleanup.
• Revoke the provider grant separately through Google Account third-party connections. Removing the local connection does not guarantee deletion of historical answers; use Data deletion for application-data requests.

Privacy and help

You stay in control of what you connect. Review how we handle information, request deletion, or contact us.

Back to all documentation