Google Ads Enhanced Conversion Tracking

Pipedrive Utilities integrates with the Google Ads API to upload offline conversion data as deals progress through your pipeline. This allows you to attribute real revenue back to the ad clicks that generated your leads.

  1. A visitor clicks a Google ad and lands on your site. The click carries a GCLID (Google Click ID) in the URL.
  2. Your form or landing page captures the GCLID and stores it on the Pipedrive deal (via a custom field).
  3. As the deal reaches key milestones, Pipedrive Automations fire a webhook to this application with the deal ID and conversion name.
  4. The server extracts the GCLID from the deal, constructs a conversion payload, and uploads it to the Google Ads API.

Google Ads then attributes the conversion value back to the original ad click, closing the loop between ad spend and actual revenue.

  1. Open Settings in the Pipedrive Utilities panel.
  2. Navigate to the Google Ads pane.
  3. Click Connect Google Ads.
  4. You will be redirected to Google’s OAuth consent screen. Authorize the application to access your Google Ads account.
  5. After authorization, the status badge will show Connected along with the authorized email address.

The OAuth token is stored per-company and refreshed automatically. If the token cannot be refreshed (e.g., access was revoked), a failure notification is sent and the status will show disconnected.

The Google account you authorize must have access to the MCC (Manager) account that manages your ad accounts. The MCC account ID is configured separately in Configuration.

The integration uses a Manager (MCC) account architecture:

  • The MCC account ID is used as the login-customer-id header for all Google Ads API requests.
  • Conversion actions are discovered by enumerating child accounts under the MCC and checking each account’s conversion tracking settings (including cross-account tracking).
  • Uploads target the child account where clicks originate, even when the conversion action is owned by the MCC via cross-account tracking.

The webhook endpoint uses HTTP Basic Authentication. Each company has a unique username/password pair generated automatically. Configure your Pipedrive Automation webhook action with these credentials. See Configuration for details.

Previous Mailchimp Integration Next Configuration