Google Ads Destination
Last updated: 2026-06-10
Sourcesible Product Documentation · Destinations
Overview
The Google Ads Destination sends audience segments from Sourcesible directly to your Google Ads account, enabling highly granular retargeting and lookalike campaigns. You can upload customer lists based on profile attributes, run lookalike audiences using subsets of your users, and continuously fuel Google Ads custom audiences with live data so that data never goes stale.
Before setting up this Destination, ensure you have access to a Google Ads account or Google Ads Manager Account with sufficient permissions to manage customer match audiences.
Credential & Permission Setup
This Destination uses OAuth no manual API keys or credentials are required. Sourcesible will request limited access to your Google Ads account during setup. Your credentials are encrypted, and authorization can be revoked at any time from your Google Account settings.
Ensure the Google account you use to authenticate has direct access to at least one Google Ads Account or Google Ads Manager Account, and permission to manage Customer Match audiences on the target account.
During the OAuth flow, Google may display a "Google hasn't verified this app" warning screen. Click Continue to proceed this warning does not affect the security or functionality of the connection.
Connection Configuration (Inside Sourcesible)
Add a New Destination
In the left navigation, click Destinations. Click Add Destination in the top-right corner. From the Destinations catalog, click the Google Ads card, then click Add Destination to begin the setup wizard.
Authorize Google Ads Connection (Step 1 Connect)
On the Connect to Google Ads screen, click Log in to Google Ads. A Google account chooser will open select the Google account that has access to your Google Ads account, or click Use another account to log in with a different one. If Google displays a "Google hasn't verified this app" warning, click Continue to proceed. On the sign-in confirmation screen, review the access being requested and click Continue to authorize.
You will be redirected back to Sourcesible automatically. The connection indicator will show Authorization Successful your Google Ads account is now connected.
Do not close the browser tab during the OAuth flow. Closing it before the redirect completes will cancel the authentication and you will need to restart the process.
Set Up the Destination (Step 2 Set up Destination)
In the Destination Name field, enter a name for this connection. You can change this at any time under Settings. Optionally enter a Destination Description. Under Advertiser Accounts, select the Google Ads account you want Sourcesible to sync audiences to from the Select Google Ads Account list. The list displays both direct Ads Accounts and Ads Manager Accounts accessible by the authenticated user.
If you leave Advertiser Accounts empty, syncs can use any ad account the authorized user can access. If an account appears at the top level, you have direct access to that account or Manager Account.
Click Save Destination.
Test Your Connection
After saving, Sourcesible confirms the connection is active by displaying a Connected status on the Destinations page. The following are validated during setup: the OAuth token is valid, the selected Google Ads account or Manager Account is accessible, and Sourcesible can communicate with the Google Ads API.
The Sync column on the Destinations page will show until the first audience sync is triggered. The Last Update timestamp reflects when the connection was established.
Next Steps
With your Google Ads Destination connected, you can activate data from Sourcesible.
Sync an Audience to Google Ads Push customer segments for retargeting, suppression, or lookalike campaigns.
Set Sync Frequency Control how often Sourcesible updates the audience in Google Ads.
Monitor Destination Health View sync logs, error rates, and delivery status from the Destinations page.
Tips and Troubleshooting
"Google hasn't verified this app" Warning During OAuth
Symptom: After clicking Log in to Google Ads, Google displays a warning screen saying "Google hasn't verified this app."
Cause: This is a standard Google warning displayed for apps that are still completing Google's OAuth verification process. It does not indicate a security issue with Sourcesible.
Fix: Click Continue on the warning screen to proceed with the authorization. The connection will complete normally.
Google Ads Account Not Appearing in the Advertiser Accounts List
Symptom: After authorization, the Select Google Ads Account list is empty or does not show the expected account.
Cause: The Google account used to authenticate does not have access to the expected Google Ads account, or the account has been suspended or restricted by Google.
Fix: Click Refresh next to the Select Google Ads Account header to reload the account list. If the account still does not appear, confirm in Google Ads that the authenticated account has the correct access level, then click Back and re-authenticate with the correct Google account.
OAuth Token Expired
Symptom: A previously connected Destination shows a failed or disconnected status.
Cause: Google OAuth tokens expire or are invalidated when the user changes their Google password or revokes Sourcesible's access.
Fix: Navigate to Destinations and open the affected Destination. Click Reconnect and complete the OAuth flow again.
Use a shared team or service Google account for this Destination where possible. Tokens tied to personal accounts are invalidated if the account owner changes their password or revokes app permissions.