DataLane Salesforce Integration Setup Guide
Last updated: April 27, 2026
Questions? Contact [email protected]
This document is your complete guide for connecting your Salesforce instance to DataLane as a Destination for CRM matching and/or sync.
1 What is the DataLane Salesforce Integration
1.1 What DataLane Does in Your Salesforce Org
DataLane connects to your Salesforce org via a managed package and OAuth to perform entity resolution and data enrichment / syncing on your Account, Contact, and Lead records.
What DataLane does:
Reads Account, Contact, and Lead records to match them against DataLane's data
Writes entity resolution results back (e.g., matched DataLane IDs, match timestamps, enriched field values)
Creates new Account, Contact, and Lead records when configured for insert syncs
What DataLane does not do:
Delete records from your org (the Delete permission exists only because Salesforce requires it as a dependency for Modify All — DataLane never exercises it)
1.2 What Gets Installed
The DataLane managed package installs the following components into your org:
External Client App (ECA)
The DataLane ECA handles OAuth authorization. It requests two scopes:
api — REST and Bulk API access
refresh_token — allows DataLane to automatically refresh access tokens without requiring re-authentication
Permission Set: "DataLane Integration"
Grants the integration user permissions to DataLane's installed custom fields (see below).
Note: Name fields (FirstName, LastName), address fields (BillingStreet, MailingCity, etc.), and other core fields like Company and Status are always accessible to any user with object-level Read access — Salesforce does not require (or allow) explicit field-level security grants for these fields. DataLane has full read and write access to these fields through the object-level Edit permission.
Custom Fields on Account:
Custom Fields on Contact:
Custom Fields on Lead:
1.3 Data Access
By installing the DataLane managed package, providing the appropriate permissions, and completing the OAuth authorization, you are granting DataLane API access to read, create, and update Account, Contact, and Lead records in your Salesforce org. Specifically:
DataLane will read standard and custom field data on these objects for entity resolution matching.
DataLane will write to DataLane custom fields (listed above) and, where configured, to standard or customer-specified fields for enrichment.
DataLane accesses data via the Salesforce REST API and Bulk API using the credentials of the dedicated integration user.
Access is scoped to the permissions granted by the DataLane Integration permission set — DataLane cannot access objects or fields beyond what this permission set (plus any supplementary permission sets you assign) allows.
You can revoke DataLane's access at any time by revoking the OAuth token, un-assigning the permission set, or uninstalling the managed package.
2 Installation & Configuration
2.1 Verify Prerequisites
Before installing, please confirm:
Org is on a supported edition (Enterprise, Unlimited, or Developer)
External Client Apps are enabled (Setup → External Client App Settings → ON)
My Domain is deployed (Setup → My Domain → status shows "Deployed")
2.2 Install the Managed Package
Follow this link to install the DataLane Salesforce Integration
Log in as a System Administrator if prompted.
Select "Install for Admins Only."
Check the acknowledgement box.
Click Install.
Installation typically completes within a few minutes. For large orgs it may take up to 30 minutes — you will receive an email when done. Check progress: Setup → Deployment Status.
2.3 Create a Dedicated Integration User
Using a dedicated integration user is a Salesforce best practice. It ensures the connection is not tied to any individual, keeps audit trails clean, and scopes permissions appropriately.
Already have a dedicated integration user? Skip to 2.4.
In Setup, search for "Users" and click Users.
Click New User.
Fill in the details:
4. Click Save. Salesforce will send a verification email to set the password.
About the Salesforce Integration license: Enterprise, Unlimited orgs get 5 free Salesforce Integration licenses. Developer Edition gets 1. Additional licenses cost $10/month. If your edition does not offer this license, use a standard Salesforce license with the "Minimum Access - Salesforce" profile.
MFA Note: If your org enforces MFA, complete the challenge when the integration user first logs in during the one-time OAuth step. After that, DataLane refreshes tokens automatically.
2.4 Assign the DataLane Integration Permission Set
In Setup → Users, click the integration user.
Scroll to Permission Set Assignments and click Edit Assignments.
Move "DataLane Integration" from Available to Enabled.
Click Save.
Note: The DataLane Integration permission set is the minimum access required on the integration user to enable DataLane to write to custom, DataLane managed fields (installed by the app) in your CRM.
2.5 Configure the External Client App Policy
In Setup, search for "External Client App Manager."
Find "DataLane" and click on it.
Click Manage Policies → Edit.
Set Permitted Users to "All users may self-authorize."
Set Refresh Token Policy to "Refresh token is valid until revoked."
Click Save.
2.6: Grant Access to All Fields
Note: Due to Salesforce limitations when installing ECAs, we typically recommend all customers to provide the integration user another permission set including “Modify All Records”, “View All Fields”, and “Create”, on the targeted objects (e.g., Accounts, Contacts, Leads) and “Read Access” and “Edit Access” for all field level permissions. This gives the application user maximum configurability in the UI.
Setup → Permission Sets → New.
Name: "DataLane Custom Field Access" → Save.
Click Object Settings → select the object (e.g., Accounts).
Edit → Toggle “Modify All Records”, “View All Fields”, and “Create” under the Object Permissions
Toggle Read Access (and Edit Access for syncs) for all fields (or only fields DataLane application users will need access to)
Repeat for Contact and Lead as needed.
Save, then assign to the integration user (same as Step 4).
2.7: Verify the Installation
Setup → Installed Packages → "DataLane Salesforce Integration" appears
Setup → External Client App Manager → "DataLane" with correct policies
Integration user has "DataLane Integration" permission set (and any additional permission sets) assigned
2.8: Complete OAuth Authorization (requires access to DataLane UI)
Click "Destinations" under Setup on the UI sidebar panel
Click "Add Destination" and select Salesforce
Click "I've completed installation" if you've confirmed successful installation of the DataLane Salesforce Integration in your org
Click "Connect to Salesforce"
Log in as the dedicated integration user — not your personal admin account.
DataLane will confirm the connection is active.
Important: The OAuth connection runs with the permissions of whichever user authorizes it. Always use the dedicated integration user.