RevenueLancer
Back to integrations
Integration guide

Google Ads integration guide

Connect Google Ads campaign spend to lead source performance so owners can compare spend with captured leads.

Start setupCommon errors

Safe setup rule

RevenueLancer shows only masked credential status in the browser. Keep tokens, secrets, and passwords in secure server-side settings.

What this integration does

  • Tests Google Ads credentials without exposing tokens.
  • Fetches daily campaign spend for the selected sync window.
  • Writes spend only to mapped lead sources and campaign IDs.
  • Shows safe last error messages when Google Ads rejects the request.

Credentials required

  • Google Ads developer token
  • OAuth client ID
  • OAuth client secret
  • OAuth refresh token with Google Ads access
  • Customer ID without dashes
  • Manager customer ID, only when the account is managed under an MCC

Where to get credentials

  • Create or review your developer token in the Google Ads API Center.
  • Create OAuth credentials in Google Cloud Console for the same Google project.
  • Generate a refresh token using the Google Ads OAuth scope.
  • Copy the customer ID from Google Ads. If you use a manager account, copy that ID separately.

How to connect

  • Open RevenueLancer integrations and choose Google Ads.
  • Save the developer token, OAuth client ID, OAuth client secret, refresh token, customer ID, and optional manager customer ID.
  • Keep the integration enabled.
  • Map Google campaign IDs to RevenueLancer lead sources before syncing spend.

How to test

  • Click Test Google Ads connection on the integration page.
  • RevenueLancer exchanges the refresh token server-side and runs a small safe customer query.
  • If the test passes, run manual sync.
  • Review recent safe event summaries and last sync time.

Common errors

  • Invalid or expired refresh token: create a new OAuth refresh token and save the credentials again.
  • Customer ID access denied: confirm the Google account has access to the customer account and manager account, if used.
  • Developer token not approved: use an approved Google Ads developer token for live sync.
  • No mapped campaigns: sync can test successfully, but spend is written only for mapped campaigns.