Google Ads Configuration

All Google Ads settings are managed in Settings > Google Ads within the Pipedrive Utilities panel.

These settings apply to all conversion actions for your company.

The Google Ads Manager (MCC) account ID. This is sent as the login-customer-id header on all API requests and is required for the integration to function.

Format: 123-456-7890 or 1234567890 (dashes are stripped automatically).

The Pipedrive deal field that contains the Google Click ID. The field value can be in any of the following formats – the GCLID is extracted automatically:

  • Full URL – https://example.com/landing?gclid=abc123&utm_source=google
  • Query string – gclid=abc123&utm_source=google or ?gclid=abc123
  • Bare GCLID – abc123 (alphanumeric string, 20+ characters)

If your form captures the full landing page URL, you can store that directly in the deal field. The integration will parse the gclid parameter from the URL automatically.

The ISO 4217 currency code used for all conversion values (e.g., USD, EUR, GBP). This is a global setting that applies to all conversion actions. Default: USD.

How long to keep retrying when a GCLID is too new for Google Ads to recognize. Google can take several hours to process new clicks before they become available for conversion uploads. If a conversion fails with CLICK_NOT_FOUND, it is automatically queued and retried every 30 minutes until the TTL expires. Default: 12 hours.

See Retry Queue for details.

A single webhook URL is used for all conversion actions. The webhook is secured with HTTP Basic Authentication.

Each company has a unique username and password pair, automatically generated on first use. These are displayed in the Webhook section of the settings page.

  • Webhook URL – https://<your-worker-url>/webhook/adwords
  • Username – Auto-generated 16-character identifier
  • Password – Auto-generated 40-character secret

Click Regenerate Credentials to generate a new username/password pair. This will invalidate any existing Pipedrive automations using the old credentials.

Use the webhook URL as the target in your Pipedrive Automation webhook action. Configure HTTP Basic Auth with the credentials shown in settings. The webhook expects a POST request with the following JSON body:

{
  "dealId": {{ deal.id }},
  "conversion": "Inquiry"
}
Field Description
dealId The Pipedrive deal ID. Use the {{ deal.id }} variable in Pipedrive Automations.
conversion The name of the conversion action (must match one configured below).

Each conversion action maps to a single Google Ads conversion action. When a webhook fires with a matching conversion name, the system uploads the conversion to Google Ads with the configured value.

Field Description
Name The conversion name used in the webhook body (e.g., Inquiry, Enrolled). Must be unique within the company.
Conversion Action The Google Ads conversion action to report to. The dropdown is populated from your connected Google Ads account.
Value The monetary value reported for this conversion.

The conversion name is case-sensitive and must match exactly what you send in the webhook body. Use simple, descriptive names like Inquiry, Application, or Enrolled.

Previous Overview Next Conversion Tracking