Kommo–Google Ads Integration Setup
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted3 hours ago
Build an integration between:
Website → Kommo CRM → Make.com → Google Sheets → Google Ads
The purpose of this integration is to track actual closed sales as Offline Conversions / Enhanced Conversions for Leads in Google Ads and attribute each completed sale to the original Google Ads click.
Workflow
1. Capture Click Data from the Website
When a visitor lands on the website through a Google Ads campaign, the website must capture and store:
GCLID
Customer information
Phone number
Email address, if available
Lead creation date and time
This information must be passed when the customer submits the website lead form.
2. Store Data in Kommo CRM
When a Lead or Deal is created in Kommo, the following information must be stored:
Lead / Deal ID
GCLID
Customer name
Phone number
Email address
Lead creation date
Lead source
A custom field must be created in Kommo to store the GCLID and keep it linked to the deal until the deal is closed.
3. Phone Number Processing
Before the phone number is used for Google Ads conversion data, the integration must normalize it according to Google Ads requirements.
All phone numbers must be converted to the:
E.164 format
The required format is:
+[Country Code][Phone Number]
Example:
+971501234567
The phone number must not contain:
Spaces
Hyphens
Parentheses
Unnecessary symbols
The system must also ensure that the correct country code is added.
For example, if the customer enters a local UAE number:
050 123 4567
It must be converted to:
+971501234567
The phone number normalization process should be handled within Make.com or at the appropriate stage before preparing the Google Ads conversion record.
If hashed customer data is required for Google Ads Enhanced Conversions, the normalized phone number must be prepared using:
SHA-256
according to Google Ads requirements.
4. Send Data to Google Sheets
Make.com should create or update a dedicated row for each Lead inside Google Sheets.
Each record should contain:
Kommo Lead ID
Kommo Deal ID
GCLID
Customer name
Original phone number
Normalized phone number in E.164 format
Email address
Lead creation date
Deal status
Deal value
Currency
Conversion Date & Time
Google Ads conversion upload status
It is recommended to keep both the original phone number and the normalized phone number for troubleshooting and data validation purposes.
5. When the Deal Is Closed
When a deal inside Kommo changes to:
Won / Closed Won / Successful
Make.com should detect the status change and retrieve the following data:
GCLID
Phone number
Email address, if available
Deal value
Currency
Deal closing date and time
Kommo Deal ID
The corresponding row in Google Sheets must then be updated.
6. Prepare the Google Ads Conversion Data
The system must prepare all required conversion data for Google Ads, including:
GCLID
Conversion Action
Conversion Date & Time
Conversion Value
Currency
Phone number in a Google Ads-compatible format
Email address, if available
Deal ID
The:
Conversion Date & Time
must represent the actual date and time when the deal was closed or the sale occurred, not the date and time when the ad click happened.
7. Prevent Duplicate Conversions
The system must include a mechanism to prevent the same deal from being sent to Google Ads more than once.
The:
Kommo Deal ID
can be used as the unique deal identifier.
A dedicated Google Sheets field such as:
Conversion Sent
can also be created.
After a conversion is successfully sent to Google Ads, the value should be changed to:
YES
This will prevent duplicate conversion uploads.
Final Data Flow
The complete workflow should be:
Google Ads Click
↓
Capture GCLID
↓
Website Lead Form
↓
Phone Number + Customer Data + GCLID
↓
Kommo CRM
↓
Store GCLID with the Lead / Deal
↓
Make.com
↓
Normalize Phone Number to E.164
↓
Google Sheets
↓
Wait for Deal Closure
↓
Kommo Deal = Won
↓
Deal Value + Sale Date & Time + Customer Data
↓
Google Ads
↓
Offline Conversion / Enhanced Conversion for Leads
Expected Result
The final objective is to allow Google Ads to identify which advertising click resulted in an actual completed sale.
Google Ads should receive the real conversion value and the actual conversion date and time, allowing the advertising account to use real sales data for:
Conversion tracking
Revenue attribution
Campaign optimization
Smart Bidding
ROAS optimization
Important Technical Requirement
The implementation must not simply send the phone number as entered by the customer.
The developer must specifically implement:
Normalize the phone number to E.164 format before preparing the Google Ads conversion record.
The system should also retain and use the following customer identifiers whenever available:
GCLID + Phone Number + Email Address
This will provide stronger conversion matching and attribution than relying on GCLID alone.
Website → Kommo CRM → Make.com → Google Sheets → Google Ads
The purpose of this integration is to track actual closed sales as Offline Conversions / Enhanced Conversions for Leads in Google Ads and attribute each completed sale to the original Google Ads click.
Workflow
1. Capture Click Data from the Website
When a visitor lands on the website through a Google Ads campaign, the website must capture and store:
GCLID
Customer information
Phone number
Email address, if available
Lead creation date and time
This information must be passed when the customer submits the website lead form.
2. Store Data in Kommo CRM
When a Lead or Deal is created in Kommo, the following information must be stored:
Lead / Deal ID
GCLID
Customer name
Phone number
Email address
Lead creation date
Lead source
A custom field must be created in Kommo to store the GCLID and keep it linked to the deal until the deal is closed.
3. Phone Number Processing
Before the phone number is used for Google Ads conversion data, the integration must normalize it according to Google Ads requirements.
All phone numbers must be converted to the:
E.164 format
The required format is:
+[Country Code][Phone Number]
Example:
+971501234567
The phone number must not contain:
Spaces
Hyphens
Parentheses
Unnecessary symbols
The system must also ensure that the correct country code is added.
For example, if the customer enters a local UAE number:
050 123 4567
It must be converted to:
+971501234567
The phone number normalization process should be handled within Make.com or at the appropriate stage before preparing the Google Ads conversion record.
If hashed customer data is required for Google Ads Enhanced Conversions, the normalized phone number must be prepared using:
SHA-256
according to Google Ads requirements.
4. Send Data to Google Sheets
Make.com should create or update a dedicated row for each Lead inside Google Sheets.
Each record should contain:
Kommo Lead ID
Kommo Deal ID
GCLID
Customer name
Original phone number
Normalized phone number in E.164 format
Email address
Lead creation date
Deal status
Deal value
Currency
Conversion Date & Time
Google Ads conversion upload status
It is recommended to keep both the original phone number and the normalized phone number for troubleshooting and data validation purposes.
5. When the Deal Is Closed
When a deal inside Kommo changes to:
Won / Closed Won / Successful
Make.com should detect the status change and retrieve the following data:
GCLID
Phone number
Email address, if available
Deal value
Currency
Deal closing date and time
Kommo Deal ID
The corresponding row in Google Sheets must then be updated.
6. Prepare the Google Ads Conversion Data
The system must prepare all required conversion data for Google Ads, including:
GCLID
Conversion Action
Conversion Date & Time
Conversion Value
Currency
Phone number in a Google Ads-compatible format
Email address, if available
Deal ID
The:
Conversion Date & Time
must represent the actual date and time when the deal was closed or the sale occurred, not the date and time when the ad click happened.
7. Prevent Duplicate Conversions
The system must include a mechanism to prevent the same deal from being sent to Google Ads more than once.
The:
Kommo Deal ID
can be used as the unique deal identifier.
A dedicated Google Sheets field such as:
Conversion Sent
can also be created.
After a conversion is successfully sent to Google Ads, the value should be changed to:
YES
This will prevent duplicate conversion uploads.
Final Data Flow
The complete workflow should be:
Google Ads Click
↓
Capture GCLID
↓
Website Lead Form
↓
Phone Number + Customer Data + GCLID
↓
Kommo CRM
↓
Store GCLID with the Lead / Deal
↓
Make.com
↓
Normalize Phone Number to E.164
↓
Google Sheets
↓
Wait for Deal Closure
↓
Kommo Deal = Won
↓
Deal Value + Sale Date & Time + Customer Data
↓
Google Ads
↓
Offline Conversion / Enhanced Conversion for Leads
Expected Result
The final objective is to allow Google Ads to identify which advertising click resulted in an actual completed sale.
Google Ads should receive the real conversion value and the actual conversion date and time, allowing the advertising account to use real sales data for:
Conversion tracking
Revenue attribution
Campaign optimization
Smart Bidding
ROAS optimization
Important Technical Requirement
The implementation must not simply send the phone number as entered by the customer.
The developer must specifically implement:
Normalize the phone number to E.164 format before preparing the Google Ads conversion record.
The system should also retain and use the following customer identifiers whenever available:
GCLID + Phone Number + Email Address
This will provide stronger conversion matching and attribution than relying on GCLID alone.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.