How to track lead source in Salesforce

Salesforce is the system of record for most B2B sales teams, but Salesforce’s native attribution stops at a single LeadSource field with no multi-touch model and no historical journey. SourceLoop adds: first-touch and last-touch source on every Lead and Contact, the full UTM trail, the visitor’s pre-conversion journey, and multi-touch attribution models that respect Salesforce’s Lead → Contact → Opportunity flow.

This article covers the OAuth connect flow only. After connecting, see:

• Push UTMs and lead source to Salesforce fields
• Map SourceLoop stages to Salesforce Lead Status

Why connect Salesforce to SourceLoop?

Salesforce ships with one LeadSource field per Lead. SourceLoop adds:

• First-touch source / medium / campaign as separate fields, so you know the original channel even after multiple touchpoints
• Last-touch (converting session) source / medium / campaign as separate fields
• Full UTM trail with content and term, not just source and medium
• Visitor journey (every page browsed pre-conversion) viewable on the Lead / Contact record
• Multi-touch attribution models (first, last, linear, position-based, time-decay)
• Revenue-by-channel when payment integrations are connected, attributed back to the original Lead

All of this sits on standard Salesforce records, so it shows up in Salesforce reports, Lightning record pages, and any workflow / process you build against it.

Before you start

You’ll need:

• A SourceLoop workspace with the tracking pixel installed
• A Salesforce org (Sales Cloud or Service Cloud; any edition)
• A Salesforce user with System Administrator profile, or Modify All Data + API Enabled permissions, to run the OAuth connect
• An Admin or Editor role in SourceLoop

Step 1: Open the CRM integrations page

1. Sign in to SourceLoop.

2. Click Setup in the left sidebar.

3. Click the CRM tab inside Setup.

4. Scroll to the Salesforce card.

Step 2: Pick sandbox or production

1. In the Salesforce drawer, tick Connect to a Salesforce sandbox (test.salesforce.com) if you want to try it on your sandbox first. Leave it unticked for production.
2. Click Connect Salesforce.

You’ll be redirected to Salesforce’s sign-in, either login.salesforce.com (production) or test.salesforce.com (sandbox).

Step 3: Authorise SourceLoop on Salesforce

1. Sign in to Salesforce if you aren’t already.
2. Pick the org you want to connect (if you have multiple Salesforce users).
3. Review the scopes SourceLoop is requesting (API access, refresh_token, offline_access).
4. Click Allow.

Salesforce redirects you back to SourceLoop. The connection card flips to Connected and shows your Salesforce instance URL (e.g., acme.my.salesforce.com).

Step 4: Choose what syncs

After connecting, the Salesforce drawer opens on the Sync tab. Each direction has its own switch, and both start switched off.

• Send leads to Salesforce: new leads arrive with their channel, campaign, and ad. Choose All leads or Good leads only. Use Find matching records to fill in attribution on records SourceLoop has already matched, without creating anything new. Only leads from the moment you switch this on are created in Salesforce.
• Bring Salesforce data in: accounts, contacts, and opportunities, with their stages and revenue, credited to the campaigns behind each buyer. Turn on Add contacts Sourceloop has not seen to bring in people who never came through your website.

Step 5: Mark won and lost stages and map fields

1. On the Deal stages tab, mark which opportunity stages mean won and lost, so closed revenue is credited correctly.
2. On the Fields tab, map SourceLoop’s attribution to fields in Salesforce. Salesforce doesn’t let apps create fields for you, so create the fields you want on Lead, Contact, and Opportunity first (for example “First touch channel” and “Latest touch campaign” as text fields), then map them here. See Push UTMs to Salesforce.

Step 6 (optional): Turn on real-time updates

By default, SourceLoop checks Salesforce for changes every 15 minutes. For instant updates, open Real-time updates in the drawer and set up a Salesforce Flow with an HTTP Callout that sends contact, account, and opportunity changes to the URL shown, authenticated with the bearer secret shown next to it.

What happens next

• The first sync reads your pipelines, opportunities, and matched people in the background. Large orgs take longer.
• Lead status and lifecycle stages: map Salesforce values to SourceLoop’s under Setup -> Stages. See Map Salesforce lead status.
• Troubleshooting: see Troubleshoot Salesforce sync.

What’s next

• Map attribution to your Salesforce fields: Push UTMs to Salesforce
• Map Lead Status values: Map Salesforce lead status
• Fix a sync that looks stuck: Troubleshoot Salesforce sync