Add the Click ID field to Salesforce leads
On this page
Tapper matches a Salesforce lead to the Google Ads click that produced it through the Google click ID, the GCLID. With the GCLID stored on your leads, Tapper reads it at each sync and ties each lead's outcome to its ad click.
Before you start
- Salesforce is connected on the entity's Setup > Data sources page. See Connect Salesforce (read-only).
- A Salesforce admin can add a field to your leads, and someone can edit the lead form on your website.
Store the click ID on your leads
This happens in Salesforce and on your lead form. The public guide Add the Click ID Field has the full steps. In outline:
- In Salesforce, create a field on the Lead object to hold the click ID. Name it
GCLID__c(Tapper also findsGoogle_Click_ID__c,GoogleClickId__candGCLID_c__c) so Tapper detects it when you connect. - Make sure the Salesforce user that connected Tapper can see the field.
- On your lead form, capture the
gclidvalue from the landing page URL into that field. - Submit a test lead and check that the value lands on it in Salesforce.
If your leads already carry a click ID, for example for offline conversion imports to Google Ads, check with whoever set that up before you build a second field.
Check the field in Tapper
- With several protected entities, pick the entity in the switcher under the workspace name. Under Setup, select Data sources and press Manage on the Salesforce row.
- On the Settings tab, check that Click ID field names the field you created. It is read-only: Tapper detects the field when you connect.

Read the match rate
The Overview tab shows how many outcomes Tapper tied to an ad click, with three chips:
| Chip | What it counts |
|---|---|
| Salesforce click ID | Outcomes matched through the click ID stored on the Salesforce record |
| Tapper click data | Outcomes matched through Tapper's own record of the ad click |
| Unmatched | Outcomes Tapper could not tie to an ad click |

If something goes wrong
- Click ID field reads "None found. Matching uses Tapper click data." or names another field. Tapper sees only the fields the connecting Salesforce user can see, so check that first. Tapper looks for the field when Salesforce is connected: for a field added later, write to support@tapper.ai with the entity name and the field's API name. Syncing needs a click ID field, so set it up before you turn syncing on.
- The match rate stays low. The field is usually missing or empty. Open a recent lead in Salesforce; if the field is empty, check how your form captures the click ID.
- Some campaigns skip Tapper's tracking. On a workspace with Block, a campaign, ad group or ad with its own tracking template overrides Tapper's, which hides its clicks from Tapper. The banner Some ads skip Tapper's tracking offers Fix tracking. Until then, those leads match only through the Salesforce click ID. See Fix campaigns, ad groups or ads that override Tapper's tracking.
Related
Was this helpful?
Still need help?
Chat with our team and mention this article.