How to push UTM parameters to Salesforce

SourceLoop can write each lead’s first and latest touch, lead quality, and lead value onto Salesforce Leads, Contacts, and Opportunities. In Salesforce you create the fields yourself and map them on the Fields tab. You can also point SourceLoop at fields you already have.

This article walks through the mapping system end to end.

Before you start

You’ll need:

• Salesforce connected to SourceLoop
• A Salesforce user with Modify All Data (or System Administrator profile) for the auto-create flow
• An Admin or Editor role in SourceLoop

The fields SourceLoop can push

On Leads and Contacts:

• Details: name, country, city, and LinkedIn URL
• First touch: Channel, Source, Medium, Campaign, Term, Content, and Landing page
• Latest touch: the same set, for the visit they converted on
• Lead and revenue: Sourceloop Lead quality, Lead score, and Lead value
• Ad click ids from Google, Microsoft, Meta, and LinkedIn
• Your custom fields, such as Service or Budget

On Opportunities:

• First touch and Latest touch Channel, Source, and Campaign, worked out from the people on the deal
• Sourceloop Visits before deal: how many visits the deal’s people made before it was created
• Sourceloop Journey: a link to the deal’s journey in SourceLoop

SourceLoop never changes a deal’s own name, amount, or stage. Your CRM owns those.

Creating the fields

Salesforce doesn’t let apps create fields, so create the ones you want yourself, as text fields on Lead, Contact, and Opportunity, then map them on the Fields tab. Name them however you like, for example “First touch channel”.

Step 1: Open the Fields tab

1. Sign in to SourceLoop.
2. Open Setup -> CRM and click the Salesforce card.
3. Click the Fields tab in the drawer.

The Fields tab shows one object at a time. Use the tabs at the top to switch between Leads, Contacts, Accounts, or Opportunities. Fields are grouped into Details, Lead and revenue, First touch, Latest touch, Ad click ids, and Custom fields, with a search box and a Not mapped filter. The count at the top shows how many fields are mapped.

Step 2: Map fields

Salesforce doesn’t let apps create fields for you, so:

1. In Salesforce Setup, create the fields you want on each object, for example a text field called “First touch channel” on Lead, Contact, and Opportunity.
2. Back on the Fields tab, click Reload Salesforce fields.
3. Pick your new field in the Salesforce field picker on each SourceLoop row.

Remove a mapping with the x on its row. Mappings save as you make them, and new leads and changes reach Salesforce within minutes.

Step 3: Configure Salesforce’s Lead → Contact conversion mapping

This is the most-missed step. Salesforce’s standard Lead conversion only copies custom fields from Lead to Contact if you’ve explicitly configured the mapping. Without it, your sourceloop_first_source__c value on the Lead gets dropped when the Lead converts to a Contact.

1. In Salesforce, go to Setup -> Object Manager -> Lead -> Fields & Relationships -> Map Lead Fields.
2. For each sourceloop_* custom field on Lead, map it to its same-named counterpart on Contact.
3. Save.

Now your attribution carries through every conversion. If you converted Leads before doing this, the historical conversions won’t have the source data on the Contact, but every conversion going forward will.

Step 4: Verify the mapping is working

1. Submit a test lead on your site and wait a few minutes.
2. Open the Lead in Salesforce.
3. Check the sourceloop_* custom fields and any standard fields you mapped, values should match what’s shown on the contact in SourceLoop’s Contacts.

If a field isn’t getting written, see Troubleshoot Salesforce sync issues.

Should you also map to Salesforce’s standard LeadSource?

A common question. Two camps:

• Don’t map (default behavior): SourceLoop writes to sourceloop_* fields. Your team’s existing LeadSource conventions stay intact. Reports built on LeadSource keep working unchanged. SourceLoop adds new fields you can pivot on separately.
• Do map: SourceLoop writes first-touch source to LeadSource directly. Useful when your existing Salesforce reports are heavily built on LeadSource and changing them is more work than letting SourceLoop populate it. Caveat: SourceLoop will overwrite any prior LeadSource value (including manual entry).

There’s no wrong answer, it depends on how much existing Salesforce reporting depends on LeadSource. Most teams start with the default and add the LeadSource mapping later if reporting is awkward.

Pushing to custom objects

Custom objects (e.g., Custom_Application__c) aren’t supported on the Fields tab. For those, use an outgoing webhook (Activation -> Outgoing webhooks) to send raw conversion events as JSON and write to the custom object via an Apex trigger or Flow on your side.

What’s next

After fields are mapped, the next step is aligning SourceLoop’s lifecycle stages with Salesforce’s Lead Status picklist. See Map SourceLoop stages to Salesforce Lead Status.