Salesforce Sales Cloud

Datafly Signal creates Salesforce Sales Cloud records server-to-server using the REST API Create-a-Record resource. Lead-capture events from your site — sign-ups, form submissions, demo requests — become Salesforce Lead records, with no client-side script and no data leaving your infrastructure unhashed where hashing applies.

Prerequisites

You need a Salesforce org with API access and an External Client App (or Connected App) configured for the OAuth 2.0 Client Credentials flow. This is the recommended server-to-server authentication method — it requires no interactive login and no refresh tokens.

Configuration

Configure in Signal

1. Go to Integrations > Add Integration > Salesforce Sales Cloud.
2. Choose the Default (Lead Capture) preset.
3. Enter your instance_url, login_host, client_id, client_secret, and sobject_type.
4. Select the consent categories that apply (typically marketing).
5. Click Save.

The integration’s Field Mappings can be edited in the Management UI to map additional Lead fields.

API Endpoint

Signal first obtains an access token via the Client Credentials grant:

POST https://{login_host}/services/oauth2/token
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials&client_id={client_id}&client_secret={client_secret}

The token response returns access_token and instance_url. Signal then creates the record:

POST https://{instance_url}/services/data/v60.0/sobjects/Lead
Authorization: Bearer {access_token}
Content-Type: application/json

A successful create returns HTTP 201 with the new record ID:

{ "id": "00Q5g00000ABCDeEAF", "success": true, "errors": [] }

Identity Signals

Salesforce Sales Cloud is a system of record, not a probabilistic match service. Records are keyed by their natural fields — for Leads, the Email field is the de-facto identifier. Signal maps the identity traits you provide via datafly.identify() to standard Salesforce field API names:

The marketing consent signal maps to the Lead’s HasOptedOutOfEmail flag: when canonical marketing consent is true, the Lead is opted in (HasOptedOutOfEmail = false); otherwise it is opted out.

Event Mapping

Default (Lead Capture) preset

Anonymous page views (page) and other events are dropped — only lead-capture events create records.

Example: Lead Generated

Datafly.js call:

datafly.identify("lead-001", {
  email: "jane.doe@example.com",
  firstName: "Jane",
  lastName: "Doe",
  company: "Acme Corp",
  phone: "+44 7700 900123",
  title: "Head of Growth"
});
 
datafly.track("Lead Generated", {
  description: "Requested whitepaper: Server-Side Tagging",
  industry: "Technology",
  num_employees: 250
});

Salesforce REST payload sent by Signal:

{
  "Email": "jane.doe@example.com",
  "FirstName": "Jane",
  "LastName": "Doe",
  "Company": "Acme Corp",
  "Phone": "+44 7700 900123",
  "Title": "Head of Growth",
  "LeadSource": "google",
  "Description": "Requested whitepaper: Server-Side Tagging",
  "Industry": "Technology",
  "NumberOfEmployees": 250,
  "HasOptedOutOfEmail": false
}

Testing

1. Configure the integration against a sandbox first (login_host = test.salesforce.com).
2. Submit a lead-capture form on a page running Datafly.js.
3. In Salesforce, open the Leads tab and confirm the new record appears with the mapped fields.
4. Use Signal’s Event Debugger to inspect the exact REST payload sent and the 201 response containing the new record ID.

Troubleshooting

Rate Limits

Salesforce enforces a daily API request limit per org (varies by edition and license count). The integration creates one record per matching event; for high-volume sign-up flows, monitor your org’s API Usage in Setup and consider gating which events create Leads.