Google Ads Integration with Bitrix24

The Problem with Blind Ad Spend

Your Google Ads budget is 300,000 RUB per month. CRM receives 90 leads tagged "from the internet". Without integration, you can't tell how many came from ads or which campaigns convert best. The marketer's typical answer: "We called — most say they found us via search." That's not analytics; it's guessing. Integrating Google Ads with Bitrix24 gives clear numbers: campaign spend, lead count, deal conversion, revenue, and ROI. No manual copying into spreadsheets.

A common scenario: a company spends 500,000 RUB across several campaigns (brand search, display network, retargeting). Without integration, you can't see which one pays off. After linking to CRM, you find retargeting has a CPL 3x higher than brand search and ROI of only 50%. The decision: reallocate the budget.

How the Integration Works

Bitrix24 supports integration through the module CRM → Marketing → Ad Accounts. The sequence is:

1. Authorize using the Google account linked to the ad account.
2. Select the Google Ads account (if using a manager account, choose the specific client account).
3. Map campaigns — Bitrix24 pulls the list of active campaigns.
4. Import costs automatically, once per day.

After setup, CRM analytics shows Google Ads spend data alongside CRM data: leads, deals, revenue.

UTM Tagging and gclid

The connection "click → lead" works through two mechanisms. UTM tags — manual URL markup in ads:

utm_source=google utm_medium=cpc utm_campaign={campaignid} utm_content={creative} utm_term={keyword} 

Google Ads supports tracking templates at the account level — UTM tags are added automatically to all ads.

gclid (Google Click ID) — an automatic parameter that Google adds to the URL on click. It's a unique click identifier, critical for offline conversions.

When a lead is created in Bitrix24, both types are saved:

• UTM fields — in standard fields (UTM_SOURCE, UTM_CAMPAIGN, etc.)
• gclid — in a custom field UF_CRM_GCLID

Building ROI Reports

CRM analytics groups leads and deals by UTM tags. For Google Ads, the following detail is available:

For accurate attribution, UTM tags must reach CRM without loss. Typical loss points: site redirects, SPA without server-side parameter handling, forms without hidden fields for UTM.

Offline Conversions for Smart Bidding

Google Ads supports server-side conversion upload. This allows Smart Bidding algorithms to optimize bids based on real sales, not just intermediate actions (e.g., form submissions).

The data flow:

1. Visitor clicks an ad → Google adds gclid to the URL.
2. Website saves gclid in a cookie and passes it to CRM when creating a lead (hidden form field).
3. In Bitrix24, gclid is stored in a lead custom field and inherited by the deal when converting.
4. Deal is closed as successful → script sends data via Conversion Upload API (Google Ads API Docs): gclid, conversion name, date, value.
5. Google Ads receives the data and uses it for bid optimization and reporting.

Requirements: a conversion action in Google Ads (type "Import → CRM"), access to Google Ads API via a service account or OAuth.

Enhanced Conversions

If gclid could not be saved (user came from another device, cleared cookies), Google supports Enhanced Conversions — sending conversions via hashed user data (email, phone). Bitrix24 stores this data in the contact card — it's hashed (SHA-256) and sent to Google Ads API.

Advanced Analytics via API

For detail beyond standard Bitrix24 capabilities, we use Google Ads API:

• Search query reports: search_term_view — actual user queries that led to clicks. Matching with CRM conversions shows which queries drive sales.
• Device-level spend: mobile vs. desktop — which has higher deal conversion?
• Geo-level spend: which regions produce paid deals.
• Performance Max: detailed reporting through API reveals asset and audience data unavailable in the interface.

Data is exported via script to Bitrix24 BI builder or external BI systems (Google Looker Studio, Power BI).

Common Pitfalls and Fixes

• gclid not saved. SPA site doesn't pass GET parameters to the form. Solution: JavaScript handler that reads gclid from URL on page load and stores it in a hidden form field + cookie.
• Duplicate conversions. One deal sent to Google Ads twice. Solution: unique order_id (deal ID in Bitrix24) in each upload — Google deduplicates.
• Timezone mismatch. Google Ads uses account timezone, Bitrix24 uses server time. Daily reconciliation may show discrepancies. Solution: reconcile over full weeks or months.
• API block. Google Ads API requires a Developer Token with at least "Basic" access. To obtain it, apply via Google Ads Manager.

What We Deliver

Contact us for an audit of your integration — we evaluate the project in one business day. Order a turnkey setup and get accurate attribution to boost your ROI.