Google Ads Destination

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.

2. 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
• Permission to manage Customer Match audiences on the target account

3. Connection Configuration (Inside Sourcesible)

3.1 Open the Destinations Catalog

1. In the left navigation, click Destinations.
2. Click Add Destination in the top right corner.
3. From the Destinations List, click the Google Ads card.

3.2 Review Features and Overview

1. On the Google Ads detail page, review the Feature section, which lists what this Destination enables:
   • Upload lists to Google Ads based on attributes within your database
   • Run lookalike audiences using subsets of your users
   • Continuously fuel Google Ads custom audiences with live data
2. Click Add Destination to begin the setup wizard.

3.3 Authorize Google Ads Connection (Step 1 — Connect)

1. On the Connect to Google Ads screen, click Log in to Google Ads.
2. 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 account.
3. If Google displays a "Google hasn't verified this app" warning, click Continue to proceed.
4. On the sign-in confirmation screen, review the access being requested and click Continue to authorize.
5. You will be redirected back to Sourcesible automatically. The connection indicator will show Authorization Successful — your Google Ads account is now connected to Sourcesible.

3.4 Set Up the Destination (Step 2 — Set up Destination)

1. In the Destination Name field, enter a name for this connection (e.g., Google Ads). You can change this at any time under Settings.
2. Optionally, enter a Destination Description to help your team identify this connection.
3. 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.

4. Click Save Destination.

Sourcesible will return you to the Destinations page, where the new connection will appear with a Connected status and a confirmation banner: Your destination has been connected successfully.

4. 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:

• ✅ OAuth token is valid and the Google account is authorized
• ✅ The selected Google Ads account or Manager Account is accessible by the authenticated user
• ✅ Sourcesible can communicate with the Google Ads API

5. Next Steps

With your Google Ads Destination connected, you can:

• 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

6. 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 from their Google Account.

Fix:

1. Navigate to Destinations and open the affected Destination.
2. Click Reconnect and complete the OAuth flow again.