Support

Add the Click ID field to Salesforce leads

Tapper matches a Salesforce lead to the Google Ads click that produced it through the Google click ID, the GCLID. When the GCLID is stored on your Salesforce leads, Tapper reads it during each sync and ties the lead's outcome to a specific ad click.

Before you start

Store the click ID on your leads

This part happens in Salesforce and on your lead form, not in Tapper. The public guide Add the Click ID Field has the full steps. In outline:

  1. In Salesforce, create a field on the Lead object to hold the click ID.
  2. Make sure the Salesforce user that connected Tapper can see the field.
  3. On your lead form, capture the gclid value from the landing page URL into that field.
  4. Submit a test lead and check that the value lands on the new lead in Salesforce.

If your leads already carry a click ID, for example because you import offline conversions into Google Ads, check with whoever set that up before you build a second field.

Check the field in Tapper

  1. Open Protected Entities, open the entity, and click CRM under Advanced in the left rail.
  2. Look at Click ID field. It shows the Salesforce field Tapper reads the click ID from. It is read-only: Tapper detects the field from your Salesforce org when you connect.
  3. Check that it names the field you created.

The CRM tab with the Click ID field outlined

What happens next

The Match rate section shows how many of the outcomes Tapper read from Salesforce it could tie to an ad click, with three chips:

ChipWhat it counts
Salesforce click IDOutcomes matched through the click ID stored on the Salesforce record
Tapper click dataOutcomes matched through Tapper's own record of the ad click
UnmatchedOutcomes Tapper could not tie to an ad click

The Match rate section with the Salesforce click ID, Tapper click data and Unmatched chips

If something goes wrong

  • The Click ID field reads "None found. Matching uses Tapper click data." or names another field. First check that the Salesforce user that connected Tapper can see your field: Tapper sees the fields that user can see. Tapper looks for the field when Salesforce is connected, so for a field you added afterwards, write to support@tapper.ai with the entity name and the field's API name in Salesforce. Syncing needs a click ID field, so set it up before you turn syncing on.
  • The match rate stays low. That usually means the click ID field is missing on your leads, or empty. Open a recent lead in Salesforce and check that the field holds a value. If it is empty, check how your lead form captures the click ID.
  • Some campaigns skip Tapper's tracking. On a Block + Lift workspace, Tapper sets a tracking template on your Google Ads account that passes the gclid of every click to Tapper. Where a campaign, ad group or ad has its own tracking template, it overrides Tapper's, and Tapper can't see those clicks. The dashboard warns you with the banner Some ads skip Tapper's tracking and offers Fix tracking. Until it is fixed, leads from those clicks can only match through the Salesforce click ID. See Fix campaigns, ad groups or ads that override Tapper's tracking.

Still need help?

Chat with our team and mention this article.