7 min readIntegrations

Salesforce Link Tracking: Short-Link Clicks in the CRM

Salesforce only tracks clicks on links it sent. Elido has no native Salesforce connector yet, so here is the honest DIY route using the API and webhooks.

Marius Voß
DevRel · edge infra

Salesforce records a click when Salesforce sent the link. Account Engagement rewrites the URLs in its own emails and attributes the click to a prospect, and custom redirects extend that to links you paste elsewhere. That is the whole of the native story.

Elido does not have a Salesforce connector. It is planned, and the Salesforce help page says the same. What you can do today is build the bridge yourself: a short link you own, the Elido API to read clicks, and the Salesforce API to write them. This post covers what the native tools do, the honest DIY path, and the decisions that matter more than the plumbing. For the same problem in another CRM, HubSpot link clicks on the contact timeline has the shape.

What the Native Tools Cover

Two mechanisms, both scoped to Salesforce-sent messages.

Email link tracking in Account Engagement rewrites each link through a tracker subdomain, so the click is recorded against the prospect who was mailed. It works well and it only works there.

Custom redirects go one step further: you generate a tracked URL and use it in a banner, a social post or a document, and clicks appear as prospect activity. Repeat clicks from the same prospect are throttled within a window, so the count isn't a raw total, and attribution to a named prospect depends on the visitor already being identified. Note that Salesforce's help site returned an access error when I tried to re-check these pages on 2026-10-25, so I'm stating no limits or numbers from them; confirm the details in your org.

Marketing Cloud has its own tracked-link model with the same principle: it measures what it sent.

The Elido Salesforce integration page with the connection values and setup steps for sending link clicks to the CRM

What Elido Does and Doesn't Do Today

  • What it does: short links on your domain, per-link analytics, a recent-clicks API (GET /v1/analytics/workspaces/{workspace_id}/clicks/recent) and CSV export, and signed webhooks for link and domain lifecycle events such as link.created, link.updated and domain.verified.
  • What it doesn't: a Salesforce connector, Lead or Opportunity creation, field mapping, two-way sync, or a per-click identifier you can stamp on a record. A click.created webhook exists, but it carries no visitor identity, so it can't tell you which Lead clicked. Events named conversion.recorded and threshold.exceeded are planned and not sent. The webhooks guide lists what exists.

So the click data has to be pulled, not pushed. Webhooks versus polling for click tracking covers why that is a reasonable trade.

The DIY Route

The pattern is short: a scheduled job reads new clicks, turns them into rows, and writes to Salesforce.

First, read from Elido. Poll the recent-clicks endpoint every few minutes with an API key, and keep a watermark of the last timestamp you saw. Each click row carries the link, the destination it resolved to (with whatever campaign parameters that URL holds), country, device, browser and time. The API quickstart shows the REST calls; the Go SDK is published (v0.1.0), while the TypeScript, Python and Ruby SDKs are not on their package registries yet.

Second, write to Salesforce. The REST API creates a record with a POST to the sObject collection for your object, authenticated with an OAuth access token from a Connected App you create in your org. Salesforce's platform events documentation describes the alternative: publish an event and let subscribers decide. Both Salesforce developer pages returned a 403 to my fetch on 2026-10-25, so I haven't re-verified endpoint paths or limits against them; use your org's current API version and check the reference before coding.

Third, keep the write path boring. Three choices decide whether this is a weekend job or a recurring incident.

Publish a platform event rather than writing directly, if your admins prefer flows. A subscriber then decides whether a click updates a campaign member, creates a task, or does nothing for that campaign. When marketing changes its mind, you edit a flow rather than your script.

Deduplicate on a key you control. Your poller can fetch an overlapping window, so the same click can come back twice. Build a stable key from link, timestamp and visitor fields, store it on the record as an external ID and upsert on it. Rate limits and idempotency on a link API covers the same discipline.

If you also receive Elido webhooks (for link changes, say to mirror a new link into a campaign), verify the signature first. Each delivery carries X-Elido-Signature and X-Webhook-Timestamp, computed over the timestamp and the raw body; the check is in the webhooks for link events post.

Clicks pulled from the analytics API by a scheduled job, then written to Salesforce as a click record and campaign member update

Matching a Click to a Person, Honestly

This is where integrations quietly lie, so it is worth stating plainly.

A click carries whatever the link carried. If you generated a distinct short link per recipient, the link ID identifies the recipient and you can write to their record with confidence. If four hundred people received the same link, you have four hundred clicks and no names, and no clever join recovers them. Elido stores no click ID you can pass back, so the join key is the link you minted.

So decide per use case. Outbound sequences and one-to-one follow-ups justify a link per recipient, created through the API when the message is queued. Broad campaigns do not, and campaign-level counts are the honest output: clicks per campaign, per medium, per link, attached to the campaign object rather than to individuals. URL shorteners for B2B sales teams covers where the per-recipient version pays for itself.

Don't infer identity from an IP address or a timing coincidence. It is wrong often enough to poison a pipeline report, and in Europe it is a processing decision you would rather not have to defend.

What to Write, and Where

Four targets, in ascending order of how much thought they need.

  • A custom click object: Click__c with lookups to Contact and Campaign, plus link, campaign parameters, country, device and timestamp. This is the durable choice; reporting stays fast and the activity feed stays readable.
  • Campaign member status. Moving a member from Sent to Responded on first click is the single most useful automation here, because it feeds every campaign report you already have.
  • A task, sparingly. Useful for high-value links where a rep should see the touch in their feed. Terrible as a default, because a few thousand tasks a week buries everything else.
  • A rollup field on the contact. Last clicked date and a running count are cheap to maintain and answer most questions a rep asks without opening a related list.

Map the campaign parameters into fields when the job writes the row. Elido's click row has no separate UTM fields, so parse them out of the destination URL once, in the poller; utm_campaign on the click record is what lets a sales ops report group by campaign without joining to anything.

Four setup steps for Salesforce click tracking, from creating the click object through the scheduled poller to campaign member automation

Volume Is the Constraint Nobody Plans For

Clicks arrive in bursts. A newsletter to fifty thousand people produces thousands of clicks in the first ten minutes, and a naive job turns each one into an API call.

Salesforce orgs have daily API allowances, and platform event publishing has its own quotas; I couldn't load the vendor pages to quote them, so look up your edition's figures. The arithmetic is worth doing before launch: peak clicks per minute against your allowance. The answer is usually that per-click writes don't fit.

Three ways out, in order of preference. Aggregate on your side and write hourly summaries for campaign-level reporting. Write only when a link crosses a count you care about, such as its third click. Or batch, holding clicks briefly and inserting them in bulk. I've seen the per-click version fail once, at 9am on a launch day, and the fix under pressure is always cruder than the one designed in advance.

Testing It Before You Trust It

Five checks. Create a test link, click it, and confirm one record appears with the campaign attached. Run the job twice over the same window and confirm there's still one record. Click a link for an unknown contact and confirm it lands as an unattributed row rather than throwing. Revoke the access token and confirm the job fails loudly. Then run a real campaign at low volume and reconcile Elido's count against the record count for the same window; a gap of a few percent is bot filtering and timing, a gap of thirty percent is a bug. Elido's bot filter is a User-Agent list, so some automated clicks will still count.

What Will Change When the Connector Ships

The planned native connector is meant to replace the Connected App, the poller and the field mapping with a configured integration. We aren't giving a date. Your click object and campaign-member logic should survive that move, which is another reason to model them cleanly now. Watch the changelog.

Frequently asked questions

Does Elido have a Salesforce integration?

Not yet. A native Salesforce connector is planned and not built: no Connected App, no Lead or Opportunity creation, no field mapping. Today you can forward link and domain events with a webhook, and pull click data from the analytics API into your own job. This post shows that DIY route.

Does Salesforce track link clicks natively?

It tracks clicks on links it sent. Account Engagement rewrites links in its emails through a tracker subdomain and records the click on the prospect, and custom redirects extend that to links you place elsewhere. Anything sent outside those tools, including a rep's own mailbox, an SMS campaign or a printed code, produces no click in Salesforce at all.

What is a custom redirect in Account Engagement?

A tracked link generated inside Account Engagement that records a click as an activity on the prospect record. It suits banner ads, social posts and files hosted elsewhere. Two limits matter in practice: repeat clicks by the same prospect are throttled within a short window, and the link only identifies a person when the visitor is already cookied.

How do I get short-link clicks into Salesforce?

With Elido there is no native connector today; it is planned. The DIY route is a small job that reads clicks from the Elido analytics API and writes records through the Salesforce REST API, or publishes a platform event that a flow turns into a record. Elido webhooks cover link and domain changes, not clicks, so the click side has to be a poll.

Can a click be attributed to a specific contact?

Only if the link was unique to that contact. A single campaign link clicked by four hundred people yields four hundred anonymous clicks, and nothing in the payload changes that. Generate a link per recipient when person-level attribution matters, and accept campaign-level reporting when it does not.

Should clicks be tasks or a custom object?

A custom object, once volume is real. Tasks are convenient because they surface on the activity timeline, and they become noise at a few thousand rows a week and inflate storage. A custom click object with a lookup to contact and campaign keeps reporting fast and lets you roll up counts without touching the activity feed.

Try Elido

Paste a URL, get a working short link

No signup. Link lives for 30 days. Sign up to keep it forever.

Free account required. The free plan includes 25 links in total. Already have an account? Log in

Try Elido

EU-hosted URL shortener with custom domains, deep analytics, and an open API. Free tier - no credit card.

Tags
salesforce link tracking
click tracking crm
platform events
custom redirects
webhooks
campaign member

Continue reading