NeuTargetNeuTarget
Ad Account Sync Guide

Connect Your Google Ads Account to NeuTarget

Bring Google Ads campaign spend into NeuTarget. Match it to your UTM campaigns and review spend alongside confirmed revenue and attribution coverage.

Start with guided Google sign-in, then choose the advertising account to connect. You do not need to create an OAuth app or generate a token for this flow. Manual credentials are an advanced fallback.

Best for

Google Ads spend sync

Connection

Guided Google sign-in

Need first

Google Ads account access

Next step

Review sync and mapping coverage

In this guide

1Sign in with the Google account that has advertising access
2Authorize access and choose your account
3Verify sync before using spend in reports

Before you start

Prepare your account access

What this does

NeuTarget imports Google Ads campaign spend for review alongside recorded outcomes. Campaign mapping connects external campaigns to the exact UTM values observed on your website. Unmapped spend stays visible.

What you need
  • A Google account with access to the advertising account
  • Permission to manage ad connections in your NeuTarget workspace
  • Ad-sync access under your subscription or workspace policy
  • Website tracking and revenue setup for the reports you intend to use
How access is used

Credentials are stored encrypted server-side. NeuTarget uses this connection to read spend and campaign metadata. It does not create campaigns or change your Google Ads settings.

Connect with Google sign-in

1

Sign in with the Google account that has advertising access

Open your website in NeuTarget, then Paid Acquisition → Connected Accounts. Choose Connect Google Ads. Use the Google account that can access the intended advertising account in Google Ads.

You do not need a separate developer project for the guided connection. If your team manages several accounts, confirm which advertising account you want to measure before continuing.

2

Authorize access and choose your account

Choose Connect with Google Ads. Complete Google sign-in in the separate window and review the requested access. Select your advertising account, then review the connection name and sync lookback before saving.

If the window is blocked, use Continue in this tab. If no accounts are returned, check the Google account you used and its advertising-account access. A missing account does not establish why access is unavailable.

For a manager account, choose the accessible account returned by the connection flow. Manual setup has a separate optional Login Customer ID field for a manager or MCC.

3

Verify sync before using spend in reports

Return to Connected Accounts and review the saved account and latest sync result. Use Sync now when available, then open Campaign Mapping to review campaigns that have not been matched to your website's UTM values.

A saved connection does not establish that spend has finished importing. Before interpreting ROAS, check the reporting period and currency, along with confirmed revenue and attribution coverage.

If Google cannot complete sign-in

Follow the recovery message shown in NeuTarget. Cancelled authorization and expired attempts can be retried from Connected Accounts. If Google blocks the application or the intended account remains unavailable, contact support rather than creating an unrelated OAuth app.

Contact support
Advanced: connect using existing Google Ads credentials

Use Advanced / Manual Setup only when guided sign-in is unavailable and an authorized administrator already manages the necessary API credentials. Most customers should use the guided connection above.

Refresh tokens must match the deployment's OAuth client

NeuTarget refreshes Google credentials using the OAuth client configured by its deployment operator. A token created with a different client ID will not work. Creating a new Google Cloud project does not connect that client to NeuTarget. Confirm compatibility with the operator before generating a manual refresh token.

1

Confirm the customer and manager IDs

In Google Ads, copy the 10-digit customer ID for the account you want to sync, such as 1234567890. If access goes through a manager or MCC, also confirm the appropriate manager ID for the optional Login Customer ID field.

2

Use a compatible credential

A refresh token must have been issued for the same OAuth client configured on the NeuTarget deployment, with authorization for the intended advertising account. Do not paste a client secret into the dashboard or send tokens in a support message.

For an operator-managed deployment, enable the Google Ads API and configure the OAuth consent screen for that deployment's client. If the client is in testing, the authorizing Google account must be an allowed test user.

An operator can use Google OAuth 2.0 Playground with that same client and its configured Playground redirect URI to authorize the https://www.googleapis.com/auth/adwords scope, exchange the authorization code and obtain a refresh token. Review the application identity before granting access. Do not bypass an unexpected authorization warning.

The Access Token option accepts an existing valid token for the target account. It expires and is not automatically renewed through this manual flow, so it is unsuitable for unattended ongoing sync.

3

Save the manual connection and verify sync

Enter credentials only in the authenticated Connected Accounts form. They are stored encrypted server-side.

  1. Choose Connect Google Ads, then expand Advanced / Manual Setup.
  2. Enter a display name and the advertising customer ID.
  3. Select the matching credential flow and enter its token.
  4. Add the Login Customer ID if required, then review Sync Lookback Days.
  5. Save the connection, review its sync result and check Campaign Mapping.

After connection

Use imported spend with its reporting context

What the connection imports

Campaign identifiers and names, daily spend and account currency support spend reconciliation. Review the latest sync result to see what is available for your selected reporting period.

What to check before reviewing ROAS

Review unmapped campaigns and keep UTM values consistent. Confirm the available financial evidence and compare spend with revenue in a compatible currency. Missing revenue or attribution remains a reporting gap.

Google Ads connection questions

Do I need to create OAuth credentials?

No. Use Connect with Google Ads for the normal connection flow. Manual refresh tokens require a matching deployment OAuth client and are intended for administrator-managed fallback setup.

Does connecting Google Ads enable complete ROAS?

The connection provides spend. ROAS also depends on recorded revenue and campaign mapping for the same period and currency. Check those coverage details before using a reported ratio to make a decision.