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:

Field (API Name)

Purpose

DataLane__Account_Id__c

Links the Account to a DataLane account UUID

DataLane__Attempted_Match_Date__c

Timestamp of the last matching run

DataLane__Last_Enriched_Date__c

Timestamp of the last enrichment run

DataLane__Franchise_Brand__c

Franchise brand name (for franchise-based customers)

Custom Fields on Contact:

Field (API Name)

Purpose

DataLane__Contact_Id__c

Links the Contact to a DataLane contact UUID

Custom Fields on Lead:

Field (API Name)

Purpose

DataLane__Account_Id__c

Links the Lead to a DataLane account UUID

DataLane__Contact_Id__c

Links the Lead to a DataLane contact UUID

DataLane__Attempted_Match_Date__c

Timestamp of the last matching run

DataLane__Last_Enriched_Date__c

Timestamp of the last enrichment run


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

  1. Follow this link to install the DataLane Salesforce Integration

  2. Log in as a System Administrator if prompted.

  3. Select "Install for Admins Only."

  4. Check the acknowledgement box.

  5. 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.

  1. In Setup, search for "Users" and click Users.

  2. Click New User.

  3. Fill in the details:

Field

Value (EXAMPLE)

First Name

DataLane

Last Name

Integration

Email

A shared/group address (e.g., [email protected])

Username

A unique username (e.g., [email protected])

User License

Salesforce Integration

Profile

Salesforce API Only System Integrations or Minimum Access – API Only Integrations (auto-assigned with the Integration license)

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

  1. In Setup → Users, click the integration user.

  2. Scroll to Permission Set Assignments and click Edit Assignments.

  3. Move "DataLane Integration" from Available to Enabled.

  4. 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

  1. In Setup, search for "External Client App Manager."

  2. Find "DataLane" and click on it.

  3. Click Manage Policies → Edit.

  4. Set Permitted Users to "All users may self-authorize."

  5. Set Refresh Token Policy to "Refresh token is valid until revoked."

  6. 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.

  1. Setup → Permission Sets → New.

  2. Name: "DataLane Custom Field Access" → Save.

  3. Click Object Settings → select the object (e.g., Accounts).

  4. Edit → Toggle “Modify All Records”, “View All Fields”, and “Create” under the Object Permissions

  5. Toggle Read Access (and Edit Access for syncs) for all fields (or only fields DataLane application users will need access to)

  6. Repeat for Contact and Lead as needed.

  7. Save, then assign to the integration user (same as Step 4).


2.7: Verify the Installation

  1. Setup → Installed Packages → "DataLane Salesforce Integration" appears

  2. Setup → External Client App Manager → "DataLane" with correct policies

  3. Integration user has "DataLane Integration" permission set (and any additional permission sets) assigned


2.8: Complete OAuth Authorization (requires access to DataLane UI)

  1. Click "Destinations" under Setup on the UI sidebar panel

  2. Click "Add Destination" and select Salesforce

  3. Click "I've completed installation" if you've confirmed successful installation of the DataLane Salesforce Integration in your org

  4. Click "Connect to Salesforce"

  5. Log in as the dedicated integration user — not your personal admin account.

  6. 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.


3 Troubleshooting

Problem

Solution

Package installation fails ("External Client Apps not enabled")

Enable in Setup → External Client App Settings

Package installation fails (edition error)

Verify Enterprise, Unlimited, or Developer edition

OAuth popup shows authorization error

Set Permitted Users to "All users may self-authorize"

OAuth popup blocked by browser

Allow popups for the Nango/DataLane domain and retry

Data sync misses some records

Verify DataLane Integration permission set is assigned (View All / Modify All)

Bulk update silently skips fields

Create supplementary permission set for custom fields

Connection stops working after some time

Check ECA refresh token policy is "valid until revoked"

MFA blocks integration user login

Complete MFA challenge during one-time OAuth, or temporarily exempt the user