Salesforce
Overview
Section titled “Overview”Signals writes leads captured on an ad platform or a form straight into Salesforce, so they reach the people who follow them up without anyone exporting a file.
Signals maps each lead form field to a Salesforce field and creates the record in the object you choose. The lead arrives with the platform lead ID attached, which is what lets you tie a Salesforce record back to the ad that produced it.
This is the reverse of the Salesforce source connector, which reads records out of Salesforce to send to an ad platform. If you are reporting lead outcomes back to Meta, TikTok, Snapchat or LinkedIn, that is the connector you want.
Supported sources
Section titled “Supported sources”Sources supported by Salesforce
| Category | Supported |
|---|---|
| Lead generation |
Prerequisites
Section titled “Prerequisites”Before connecting Salesforce, make sure you have:
- A Salesforce account with permission to create and update records in the object you intend to write to.
- A field in that object to hold the lead ID from your source. Create it before you start, because the mapping step will not let you finish without it.
- A Datahash Studio account with the target project selected.
- A lead generation source already connected in the same project. The destination reads its connection, so the source has to exist first.
Authentication
Section titled “Authentication”In Studio, open Destinations, find the CRM category, and click the Salesforce tile. This connector uses single sign-on only, so there is no key or token to manage.
- Click Sign in with Salesforce.
- Sign in and approve the requested permissions. The permissions are what allow Datahash to write records into your org.
Configuration
Section titled “Configuration”Source and connection
Section titled “Source and connection”- Choose the source type, which is the lead platform or form the leads come from.
- Select the connection name created when that source was set up.
- Give this destination connection a name.
Then choose the Salesforce object the leads should be written to. Leads and Contacts are the usual choices, and a custom object can be used where you have one.
The connector writes into one object per connection. If you need leads split across two objects, set up two instances.
Field mapping
Section titled “Field mapping”The mapping screen puts your lead form fields on the left and the Salesforce schema fields on the right.
Two rules apply to every mapping on this connector.
- The lead ID from your source must be mapped. It is named after the platform the lead came from, for example Meta Lead ID or TikTok Lead ID, and it is the only field that has no substitute.
- Every field your CRM marks as required, shown with an asterisk in the mapping screen, must be mapped as well. An unmapped required field fails the record rather than the connection, so the setup will look healthy while leads quietly do not arrive.
Map as many further fields as you need. Anything you leave unmapped is simply not written.
Test connection and response preview
Section titled “Test connection and response preview”Click Test Connection before finishing. This sends a sample record into Salesforce, so the test lead lands in your live CRM and someone will need to remove it afterwards. Once the test passes, click Finish.
Manage instance
Section titled “Manage instance”To add another, open Manage Connections and click Add Instance, then work through the same steps. A CRM can hold several instances, so one connection per lead source is a reasonable pattern where the mapping differs between them.
To change one, click the connection name in Manage Connections, then the edit icon in the top right. Update the fields, click Test Connection and then Finish. Clicking Cancel keeps the previous configuration running; updates apply only after you finish.
Data & identifiers
Section titled “Data & identifiers”Lead data is written into your own CRM, so nothing is hashed on the way. What arrives is what the lead form captured, in plain text, which means the CRM’s own access controls and retention rules are what govern it from that point on.
There is no fixed field specification for this destination. The fields available to map are whatever your lead form captured on one side and whatever your CRM schema exposes on the other, so the shape differs from one connection to the next.
Best practices
Section titled “Best practices”- Create the lead ID field in Salesforce before you begin. It is the most common reason people abandon the setup part way through.
- Map every field marked with an asterisk. A record that fails a required-field check is rejected silently as far as the connection status is concerned.
- Remove the test record after Test Connection passes. It is a real record in your live org.
- Use one instance per lead source rather than one shared instance, so the mapping for each form stays readable.
- Check the object you selected is the one your sales process actually works from. Leads written to the wrong object are easy to miss for weeks.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”Sign-in completes but the setup will not finish. Usually the lead ID field does not exist in the object you selected, or a required field is unmapped. Both block Finish.
Leads are not arriving. Confirm the source is connected in the same project and receiving leads, and that the connection was finished rather than left open. A connection left mid-setup does not deliver.
Some leads arrive and others do not. The ones failing are almost certainly missing a value for a Salesforce required field. The connection stays healthy while individual records are rejected.
A test record is sitting in Salesforce. That is the sample sent by Test Connection. Delete it; nothing removes it automatically.
Records are in the wrong object. The object is fixed per connection and cannot be changed for records already written. Create a new instance pointing at the right object.
Delivery stopped. The sign-in grant may have been revoked, or the user’s permissions in Salesforce changed. Reconnect through Sign in with Salesforce.