Google Ads and Meta recognise their own click in a sale by its click ID: gclid for
Google, fbclid for Meta. It arrives in the address of the page the person opened from the
ad, and KO stores it with the visit. This setting copies it into a field of the Kommo
deal — where the sale actually happens.
Why: so that a sale from Kommo can be uploaded to the ad account as an offline conversion. Without the click ID, the ad account cannot match the sale to its ad. KO does not do the upload itself — it is set up separately, in the ad account or in another service.
What KO can write
Each value goes into its own field, and each one is turned on separately.
| Setting | What goes into the deal |
|---|---|
| GA field (gclid) | the Google Ads click ID |
| FB field (fbclid) | the Meta ad click ID |
| FB field (fbc) | the _fbc cookie — the Meta click as the browser stores it |
| FB field (fbp) | the _fbp cookie — the visitor’s browser for Meta |
| GA field (cid, client_id) | the Google Analytics visitor ID |
The values come from what the KO tracker collected on the site. If the tracker did not
store a gclid, KO looks for it in the address the visit started from.
Set it up in KO
- In Kommo, add a text field to deals for each value you want to receive. KO does not create these fields.
- In Connects, open the Kommo connection.
- Find the Leads markup in CRM group.
- In GA field (gclid), choose the deal field you added for
gclid. By default it is set to (not selected), and nothing is written. - Fill in FB field (fbclid) and any other fields from the table the same way.
- Save the connection settings.
KO does not check the field type: the list shows every deal field. Choose a text field — a number or list field will not take the value.
When the field is filled
- KO creates the deal from a lead — when Sending leads to CRM is on in the connection. The field is filled at once, together with the deal.
- The deal was created in Kommo — by a Kommo form, a call or by hand. KO fills the field during sync, once it links the deal to its lead and visit.
KO only writes to an empty field. A value that is already there is not overwritten.
Check that it works
Open a recent Kommo deal that came from a Google Ads ad. After the next sync, the field you
chose for gclid holds a long string of letters and digits.
If it doesn’t add up
The field is empty on a deal from a Google ad. The address the visit started from had
no gclid. Usually auto-tagging is off in Google Ads, or a redirect on the site drops the
address parameters. The ”… Google Ads visits … have no gclid” line in Diagnostics
shows how widespread it is.
Some deals from iPhones come without gclid. Some Google Ads clicks from Apple devices
carry gbraid or wbraid instead of gclid. KO does not write those into the field.
The field holds an old value. KO only writes to an empty field. If someone else filled it first — a manager or another integration — KO’s value does not go in.
No deal ever gets the field. Check that GA field (gclid) points to your field, not (not selected), and that it is a text field. Another cause: the deal sits in a pipeline that is not in the connection’s Allowed pipelines — KO does not sync such deals.