Send Attributed Leads to Salesforce

Being able to keep track of online marketing sources inside Salesforce CRM is a common need. This guide outlines the steps needed to configure Salesforce to store additional fields and instructions to set up visitor tracking necessary for gathering UTM, Landing Page and Referrer URLs along with leads.

Salesforce Setup

Open Home – Objects and Fields – Object Manager.

(Note: this guide assumes Lightning Experience is being used; legacy UI versions have slightly different menu structure.)

Select Lead. Open Fields & Relationships and click New.

Choose following settings in Steps 1 and 2:

  • Data Type – Text,
  • Field Label – Referrer URL
  • Length – 255
  • Field Name – Referrer_URL

On ‘Step 3. Establish field-level security’ make sure the user that is used in integration has access to the field. Default values are sufficient most of the time.

On Step 4, click ‘Save & New‘.

Proceed adding following fields, using values below as Field Labels, setting Data Type to Text and Length to 255 and leaving everything else by default (similar to how Referrer URL was added):

  • Landing Page
  • UTM Source
  • UTM Medium
  • UTM Campaign
  • UTM Term
  • UTM Content

You can also add other fields such as ‘GA Cookie’ if you’d like Google Analytics Users Explorer Client Id to be present in Salesforce Lead, for example.

In Able

If you’re using Able to capture website form leads with UTM parameters and referrer URL, it will automatically recognize new Salesforce Leads' fields and will populate them with the available data.

To configure Able to send leads to Salesforce, open API Credential‘ in Able CDP Dashboard and click Connect – Salesforce:

Then, open Funnel tab and press Add Outbound to enable sending of Leads tracked by Able to Salesforce.

Congratulations! This is the entire process of adding UTM parameters, referrer URL and landing page URL to Salesforce Leads using Able Customer Data Platform.

What else you can do

Track Leads

Send Events Using Webhooks

Events can be sent to Able CDP from custom apps using its inbound webhook. This is convenient to attribute purchases and other conversions that aren't necessarily reflected in the payment system. For example, when the service usage accumulates before being invoiced once a payment threshold is reached or next billing cycle occurs.