All Collections
CRM & integrations
General information
LoneScale Contact Tracking - Contact Input Reports Salesforce
LoneScale Contact Tracking - Contact Input Reports Salesforce
Updated over a week ago

LoneScale Contact Tracking job change input reports are static or dynamic lists of people that you'd like to track for job changes or enrich.

Rather than using a single list or report, it's crucial that we identify and map different segments of people that you wish to track. We advise to create a list/report for each type of contacts:

  • Which groups or segments of Contacts we are tracking for job changes

  • Which companies are most important to you (Target Companies and/or Customers)

For LoneScale to track your key contacts for job changes, we need to know who to track. To do this, we set up different cohorts of users/contacts that you wish to track via reports from Salesforce.

When someone on one of those tracking lists changes jobs, LoneScale can:

  • update the contact

  • create/update the new account

  • create a record into a custom object

Differentiating these lists can be extremely helpful in prioritizing the importance of both job departures as well as where they land - using them to decide which sequence/cadence they should enter for sales engagement:


1️⃣ Option 1: Salesforce Reports (Preferred)

Connecting Salesforce reports is ideal for a few reasons:

  • LoneScale can automatically read your reports for updates on who we should be tracking

  • You control the filtering around who is listed in these reports

  • These reports can be saved in a specific folder in Salesforce where only those that should have access to them can see/edit them.

Salesforce reports can be Lead, Contact, Opportunity Contact Roles, or even custom objects. See below for more information regarding the columns needed.

2️⃣ Option 2: CSVs

‍CSV Upload - if you have users/contacts you want to track, and they only exist in a database external to Salesforce (i.e. Users in your application, product user database, or data warehouse), we can also read into CSV files, and still return new contacts into your Salesforce for these individuals at their new companies.

  • Note that depending on where these external contacts lie, we might be able to use our API or build a separate integration with you to pull them in dynamically.

If you have a subset of users/contacts you want to track, and they exist in a database external to Salesforce (i.e. Users from your application or data warehouse), we can also read into CSV files and still return new leads/contacts into your Salesforce for these individuals at their new companies. The disadvantage of using CSVs is needing to import new ones each month.

3️⃣ Option 3: API or Custom Integrations for Input Reports

If you have people that you'd like to track for job changes living as a product user database (e.g. Mixpanel or Pendo) or data warehouse (e.g. Snowflake or Redshift), there are other options to automate the regular collection of new Contacts.

🚨 ⚠️ 🚨 What Columns Should we Provide?

Regardless of what type of input report you create, please include the following fields if possible --- the more you can include, the better our match rate will be:

  • First Name (Required)

  • Last Name (Required)

  • Company Name (Strongly Suggested)

  • Job title (Strongly Suggested)

  • Email Address (Strongly Suggested)

  • Country location (Suggested)

  • LinkedIn URL (Suggested)

Did this answer your question?