Bitrix24 to Google Ads Offline Conversion Upload (GCLID) n8n

Send Bitrix24 GCLID offline conversions to Google Ads—automatically

This n8n workflow listens for Bitrix24 deal updates, detects deals that include a GCLID, and then uploads an Offline Click Conversion to the Google Ads API using hashed first-party identifiers—with results written back to the deal timeline.

What this workflow does

• Receives a Bitrix24 webhook when a deal is updated (e.g., ONCRMDEALUPDATE).
• Fetches full deal details from the Bitrix24 REST API and evaluates eligibility, including:
  • GCLID is present
  • “Qualified” field matches your configured requirement
  • Deal hasn’t been sent before
  • A short dedupe window to prevent repeated uploads
• Loads the linked Bitrix24 contact and normalizes customer data (email, phone, and name) according to Google Ads formatting rules.
• Hashes identifiers with SHA-256 and builds a Google Ads UploadClickConversions request using:
  • the GCLID
  • your configured conversion action
  • conversion value
  • optional enhanced conversions identifiers
• Uploads to the Google Ads API, checks for partial failures, and validates the response.
• Logs back to Bitrix24 by adding a success/error comment to the deal timeline; on success it updates the deal to mark it as sent.

Use cases

• Attribute completed CRM deals to Google Ads campaigns by sending offline conversions once a Bitrix24 deal is marked qualified.
• Run reliable conversion uploads with deduplication and audit-friendly logging directly in the Bitrix24 deal timeline.
• Ensure privacy-safe uploads by using hashed first-party identifiers (SHA-256) for enhanced conversion matching.

Technical details

• Integrations: Bitrix24 Webhooks + Bitrix24 REST API, Google Ads API (UploadClickConversions).
• n8n nodes used: webhook, filter, set, code, crypto, sticky note.
• Setup steps: configure the Bitrix24 outbound webhook for deal updates, and fill in Settings with Bitrix24 webhook base URL, Google Ads customer ID, optional login customer ID (MCC), developer token, API version, conversion action ID, plus the Bitrix24 custom field IDs for GCLID and qualified.