Vector integrates seamlessly with Salesforce to enrich your CRM with contact-level data, helping your team connect anonymous website visitors, qualify high-intent accounts, and drive timely outreach. This guide covers how the integration works, what data syncs where, and how to control every step of the process.

🔐 How Do I Connect Vector to Salesforce?

A single Salesforce user (typically an admin or integration user) connects Vector to your Salesforce instance via OAuth. This connection handles all syncing across your organization — individual users do not need to log in with their own credentials.

To connect Salesforce to your Vector workspace:

1. Navigate to the bottom left corner. Integrations → Salesforce

2. Click Connect Salesforce

3. You’ll be redirected to log in via your Salesforce credentials

✅ Once logged in, your Salesforce instance is securely connected to Vector.
✅ Only one connection is needed:

🔑 Required Salesforce Permissions

The Salesforce user account you use to connect Vector needs the right permissions in place before you authorize. If the connecting user is missing any of these, the OAuth flow may complete successfully — but syncing will fail silently or partially, which can be frustrating to diagnose.

We recommend connecting with a dedicated integration user rather than a personal admin account. This prevents the connection from breaking if someone changes their password or leaves the team.

System Permissions

The connecting user must have API Enabled turned on. This is the single most important permission — without it, Vector cannot communicate with your Salesforce instance at all, regardless of what object-level access is configured.

To check: go to Setup → Users → [User] → Profile or Permission Set → System Permissions → API Enabled ✅

If you're creating a dedicated integration user, assign them a profile that includes API access (e.g. Salesforce Integration or System Administrator), or create a custom Permission Set with API Enabled and assign it.

Object-Level Permissions

Vector needs the following access across the objects it touches. These should be set on the connecting user's Profile or an assigned Permission Set.

Field-Level Security

Object-level permissions alone aren't enough — Salesforce also controls access at the individual field level. If a field is restricted for the connecting user, Vector won't be able to read or write to it even if the object-level access is correct.

At minimum, the connecting user needs Read, Edit, and Create access on:

• Standard Lead fields: First Name, Last Name, Email, Company, Title, Phone, Website

• Standard Contact fields: First Name, Last Name, Email, Phone, Title, Account Name

• Standard Account fields: Name, Website, Industry, Number of Employees

• Task fields: Subject, Status, Description, Activity Date, Who ID, What ID

• Any custom fields you've created to receive Vector data (e.g. Vector_Segment_Name__c, Vector_Last_Visit_Date__c, Vector_UTM_Source__c)

To check field-level security: go to Setup → Object Manager → [Object] → Fields & Relationships → [Field] → Set Field-Level Security.

🔁 Is the Integration Bi-Directional?

Vector is primarily a one-way integration (Vector → Salesforce) — but with limited data pulling from Salesforce → Vector to support segmentation:

• ✅ Pushes to Salesforce: Vector can enrich Leads, Contacts, and Accounts and optionally log Tasks

• ✅ Pulls from Salesforce: Vector can public Account Lists using saved views to support CRM-aligned segmentation (e.g. pulling in Account Name, Owner, Stage)

• ❌ Vector does not scan, enrich, or modify existing Salesforce records unless explicitly configured via segment actions

• ❌ Account Lists are read-only — Vector does not push enriched data back to those records

🔄 So while the integration includes some limited pulling of account data, it’s not a full bi-directional sync in the traditional sense.

What Vector Sends to Salesforce

Enriched data may include:

• First Name, Last Name

• Job Title, Company Name, Company Domain

• LinkedIn URL, Mobile Phone Number

• Company Size, Seniority, Department, Industry

• Segment metadata (Segment Name, Segment ID, Last Active Timestamp, etc.)

What Vector Does Not Pull From Salesforce

• No scanning or importing of existing Contacts, Leads, or Accounts

• No enrichment or modification of your existing CRM records

• Data is only pushed when a segment includes a Salesforce sync action

⚙ Sync Settings Overview

You control how Vector interacts with Salesforce across three objects:

• Leads and Contacts (grouped in settings)

• Accounts

• Tasks (optional activity creation)

Lead/Contact Sync (Grouped in Settings)

In the Salesforce integration settings, Leads and Contacts are managed in a shared section — meaning sync behavior is configured together, but each object has its own independent toggle.

Available Options:

• Update existing leads – Update Lead records matched by name + company

• Create leads – Create new Leads if no match is found

• Update existing contacts – Update Contact records matched by name + email

• Create contacts – Create new Contacts if no match is found

✅ You can turn each of these on or off based on how your CRM is structured and whether you work primarily in Leads, Contacts, or both.

Account Sync

Account sync is configured separately and provides the same flexibility:

• Update existing accounts – Based on name + domain

• Create new accounts – When no match is found

📌 Tip: Account sync is commonly used in ABM workflows to enrich known accounts with segment and intent data.

Task Creation

Vector can optionally create a Salesforce Task each time a visitor is identified via Contact, Lead, or Account.

• Create new activity – Enables automatic creation of task records based on visit or intent triggers
  This is helpful for logging activity, triggering automations, or alerting sales teams of high-intent behavior.
  

  

Example in Salesforce:
When a task is pushed, you’ll see a record like this in Salesforce:

🛠 Field Mapping: Standard & Custom

In Vector, you can control which fields get synced to Salesforce and where they land — at the Lead, Contact, or Account level. Each object has its own tab, and you can define mappings independently per object.

Standard Field Mapping (Default Fields)

Vector provides a set of core enrichment fields that can be mapped directly to their corresponding Salesforce fields. These include:

• First Name

• Last Name

• Email

• Company Name

• Company Domain (mapped to Website)

• Title

These are typically pre-selected for you and can be adjusted as needed. They are available across Leads, Contacts, and Accounts, depending on how your sync is set up.

🛠 Field Mapping Using Dynamic Variables

Vector supports dynamic field mapping using structured variables when you select "Custom Value" as the data source.

Available Variables & Why They’re Helpful

Example in Salesforce:
When a task is pushed, you’ll see a record like this in Salesforce:

Passing UTMs and First-Page Details into Salesforce

Vector can capture the very first page a contact or lead landed on and any UTM parameters tied to that visit. You can map these directly into Salesforce fields for cleaner attribution and campaign reporting.

Vector + Salesforce Integration Guide

Vector integrates seamlessly with Salesforce to enrich your CRM with contact-level data—helping your team identify high-intent buyers, connect anonymous website visitors to real people, and take action at the right time.

This guide covers:

• How to connect Vector to Salesforce

• How data flows between systems

• How to configure behavior (Leads vs Contacts, updates, etc.)

• Best practices and common setups

🔐 Connecting Vector to Salesforce

A single Salesforce user (typically an admin or integration user) connects Vector via OAuth.

To connect:

1. Navigate to Settings → Integrations → Salesforce

2. Click Connect Salesforce

3. Log in with your Salesforce credentials

✅ Only one connection is required per organization
✅ All syncing is managed centrally

💡 Important:
Connecting Salesforce does not automatically send data.
Data is only sent when you explicitly add a Salesforce action to a segment.

🔁 How the Integration Works

Direction of data flow

Vector → Salesforce (one-way)

Vector sends enriched contact and account data into Salesforce when triggered by segments.

⚙ How Configuration Works

Organization-Level Settings (Not Per Segment)

All Salesforce settings are configured at the organization level, not per segment.

This means:

• You cannot send one segment to Leads and another to Contacts

• Your configuration applies globally across all segments

🧠 What You Can Control

Vector gives you control over how data is created and updated in Salesforce through a set of toggles.

Available actions:

• Create Leads

• Update Leads

• Create Contacts

• Update Contacts

• Create Accounts

• Update Accounts

• Create Tasks (activity logging)

Each of these can be enabled or disabled independently.

👥 Leads vs Contacts: How to Decide

Understanding this is key to setting up the integration correctly.

Leads

• Unqualified prospects

• Not directly tied to Accounts

• Typically owned by Marketing

• Must be converted to become Contacts

Contacts

• Qualified people tied to Accounts

• Used by Sales

• Immediately connected to company records

🧩 Common Setup Patterns

1. Product-Led Growth (PLG)

• Skip Leads entirely

• Create Contacts directly

Configuration:

• Create Contacts = ON

• Create Leads = OFF

2. Traditional Enterprise Sales

• Use Leads for qualification

• Convert to Contacts later

Configuration:

• Create Leads = ON

• Create Contacts = OFF

3. Hybrid Model

• Use both Leads and Contacts

Behavior:

• Vector checks for existing Contacts first

• If none found → creates a Lead (default priority)

🔍 How Record Matching Works

When Vector processes a person, it follows this logic:

Lookup order:

1. Check for existing Contact

   • Match on: Name + Email

2. Check for existing Lead

   • Match on: Name + Company

If a record exists:

• Updates that record (if enabled)

If no record exists:

• Creates a Lead first (if enabled)

• Otherwise creates a Contact

🧪 Data Requirements (Very Important)

Vector only creates or updates records if required fields are present.

Required fields:

If required data is missing, Vector will skip the action silently.

Example:
If a record has no company → Lead creation will not happen.

🏢 Account Creation Behavior

You can choose whether Vector creates Accounts.

If enabled:

• Accounts are created using company + domain

If disabled:

• Vector will only associate with existing Accounts

📝 Activity Tracking (Tasks)

You can optionally log Vector activity in Salesforce as Tasks.

This allows your sales team to:

• See engagement activity

• Track intent signals

• Prioritize outreach

⚠ Important Limitations

1. No Per-Segment Routing

You cannot:

• Send Segment A → Leads

• Send Segment B → Contacts

Workarounds:

• Use Salesforce Flows or automation to route records after creation

2. Free Plan Limitation

• Cannot create new Contacts on free plans

• Can still update existing Contacts

3. Data Quality Matters

Missing required fields will prevent record creation or updates.

🧭 Recommended Setup Approach

1. Start simple

   • Choose Leads or Contacts (not both initially)

2. Test with a small segment

   • Validate behavior before scaling

3. Enable updates

   • Keep CRM data fresh

4. Monitor results

   • Watch for skipped records due to missing data

🛠 Troubleshooting

Records not creating?

Check:

• Is the correct “create” toggle enabled?

• Are required fields present?

• Are you on a free plan (Contact creation blocked)?

• Does Salesforce allow API access?

Wrong object type being created?

• Leads are prioritized for new records when both are enabled

• Missing fields may change behavior

Updates not working?

Check:

• Is the “update” toggle enabled?

• Does the record match correctly?

• Are Salesforce permissions set properly?

💡 Best Practices

• Align configuration with your sales motion

• Ensure clean, complete data

• Document your setup internally

• Use Salesforce automation (Flows) for advanced routing

• Treat this as part of your broader go-to-market strategy, not just a sync

Need help configuring your sync settings or testing your mappings? Let us know — we’re happy to help.