LS4SF Package ver. 5.33 has several powerful, new features to take advantage of:
- NEW! Revenue Radar Reporting: Customers using our Predictive and/or Intent Modeling can generate and customize a revenue radar report using the data enriched through LS4SF. Please review the following article for more information! [Insert Revenue Radar Report article here].
- NEW! User Interface Tree View: LS4SF tabs are now aligned on the left hand panel to align more with the Salesforce UI. Navigating LS4SF has never been easier!
- NEW! Permission Set added for Leadspace Enrich Button users: This makes it easier than ever to grant specific users the permissions needed to use the Leadspace Enrich Button on individual records.
- NEW! Custom Fields added to Event Based Triggers: You can now use SFDC custom fields, like LS fields, to trigger an Event Based Sync for Updated Records. This provides more flexibility in the type of triggers you want to create that launch record enrichment for your changed records.
- NEW! SFDC Winter Release '24 ready: All metadata APIs have been updated for full compatibility with the SFDC Winter Release.
New Installation Instructions
Install the Package
- Have a Salesforce System Administrator log into the SFDC instance to which you want to install.
- Click the installation link here.
- Full installation link: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tDp0000006RWt
- NOTE: Some Test, UAT, and Sandbox instances will not recognize the above link. In these cases, please do the following:
- Login to your test env. and copy the full URL from your browser into a Notepad
- Delete everything in the URL after your top level domain for the env. For example, you would be left with this:
- Add packaging/installPackage.apexp?p0=04t3m000002GpoC to your trimmed URL and paste into your browser window.
- From here, you must select one of three options. Please note that this selection pertains only to the access granted on the profiles, any access and use on the LS4SF application are strongly recommended to be assigned via the Leadspace Permission sets. These permissions are also created later as part of the Permission Sets creation and can be easily assigned to users at any time.
- Install for Admins Only (Recommended)
- Install for All Users
- Install for Specific Profiles
- A pop-up may appear (depending on the version you are coming from) asking if you want to allow access to api.aptrinsic.com. Click Yes to the Gainsight notification and select Continue.
You MUST select apigw.leadspace.com and api.aptrinsic.com to proceed. The latter of the two URLs is for Gainsight usage tracking on the Leadspace side.
- Once you click ‘Upgrade’, you’ll get a message the package is upgrading and an option to click ‘Done’. This will take you to SFDC → Setup → Installed Packages.
Depending on the size and complexity of your SFDC environment, the installation can take up to 10 mins. In these cases, you’ll receive an email when the update is complete.
Input Authentication Credentials
Depending on whether you are using Classic or Lightning View, the next steps may be a bit different.
During the integration setup, Leadspace will send an OAUTH token with a program ID and secret that needs to be added to the LS4SF Integration Settings tab. This is the first order of business after the new package is installed.
- Classic: In Leadspace for Salesforce App, go to Settings tab
- Lightning: Because of the switch in the UI, you will likely need to access the Settings tab through the SFDC App Launcher. Just search for ‘Settings’ and select it. We will address this later in the setup:
Once you access the settings page, you should see the following:
The program ID/secret will either be sent directly to your SFDC System Admin, or to your Enablement representative before the installation. If you are unsure or need your OAUTH token program ID and secret, please contact Leadspace Support.
- In the 'Authentication' section at the top, input the program ID and secret sent to you
- In the 'Single Enrichment Authentication' section, input the same credentials
- Click ‘Update Settings’ and wait for the ‘Success’ message to appear.
Once the install is finished and authentication credentials are entered, use the SFDC app switcher and access the Leadspace for Salesforce app. The next steps will depend on whether you are using Salesforce Classic or Lightning views:
Please navigate to the Settings tab.
- Staying in the Settings tab, click on the ‘LS Utilities’ button. This will run a complete utility on the main components of the package updates.
Once the package is installed, you should refresh and see the new, tree view UI. From here, you will need to go to the Settings app through the Salesforce App Launcher instead of the button on the left panel. If not, you may see the following error:
Select the LS Utilities button. This will run a complete utility on the main components of the package updates.
The LS Utility tool will open in a new tab and run diagnostics on key components of the LS4SF application. Please note each section has help text in the ? icon next to the title.
The key to the LS Utilities is to look for any red errors or messages. If you see an error in red, you will want to click the ‘Fix’ then the ‘Recheck’ buttons on each.
Remote Site Settings: Key URLs in Setup allow navigation in the app.
- If this shows any URLs in Red, please click ‘Fix’, then ‘Recheck’
- You should see a green ‘Passed’ message
Permission Sets: Three permission sets are created by the package to assign to users who will manage and use the LS4SF Application:
- You may see a green ‘Partial Pass’ on this section which typically means the permission sets have been created correctly. You can reference the Leadspace for Salesforce Permission guide for the manual setup of each permission set:
Leadspace Job Handler: Creates the Scheduled Job Handler which creates enrichment jobs in Salesforce.
Minutely Periodic - Leadspace Job Handler Worker: Special job handler/scheduler for users that take advantage of Minutely Syncs. This may be green but might not apply if you are not using minutely syncs.
Bypass Validation Extra Field Creation: Allows an extra field to be created to bypass validation rules for any fields that may conflict with the LS4SF package. This defaults to OFF in settings.
Clean Records in LS Sync History Object: If older versions of LS4SF have been installed, this utility cleans old, unused, or outdated/renamed fields from the package fields during installation.
Leadspace Reports Folder: Creates a ‘Leadspace Reports’ folder for included reports such as ‘Revenue Radar’.
If you have any issues with the LS Utility, or experience any errors that will not resolve by using the ‘Fix’ and ‘Recheck’ buttons, please contact Leadspace Support for assistance.
Set Navigation Bar
Now that you have completed the initial setup, please click the pencil ‘edit’ icon on the far right hand side of the page, under the profile icon.
From here, click ‘Reset Navigation to Default’ to remove all unnecessary tabs other than the single ‘Main’ tab for the application:
Once this is clicked, refresh the page/session.
We’ve gone over some of Settings options throughout this setup. Now let’s take a look at some other key sections in the Settings section.
The following settings are grouped in the Configurations, Bypass Validation, Event Based, and LS Logs sections in the Settings section:
Email Address: Emails added here will be notified of Sync Activity automated notifications.
Number of Allowed Transactions: Max number of records that can be processed through a single Sync Definition. Max suggested is 500,000
Record Bulk Size: Selections from 5 - 500. Indicates the number of records that will be sent through each bulk API call. Recommendation is 100 or 200.
Sync Definition - Minute Interval: Values are either 3 or 5 and are locked in after you select and run a single periodic minutely sync.
Receive Email Updates For Each Minutely Based Sync Activity: If you are using a minutely periodic sync, this setting dictates whether users in the ‘Email’ section will receive a notification for every sync activity.
Custom Objects: Default OFF, once enabled this disabled the standard objects and allows you to use custom Company and Person objects created by Leadspace. Please review the following with your System Admin before considering the enablement of this setting:
Ignore Validation Rules: Defaults to OFF, when enabled, allows certain validation rules set in SFDC to be ignored during LS enrichment.
Event Based Trigger: Enables Sync Definition type ‘Event Based’ which allows you to set on-demand enrichment for created and/or updated Account, Contact, and Lead records.
Allow Trigger for Non LS Permitted Users: By default, users who create or update records as part of an event-based trigger must have the Leadspace Manager permission set assigned. Enabling this setting bypasses that requirement. The recommendation is to ENABLE this setting.
LS Logs: Allows LS Logs to capture warning and error data regarding LS4SF activities and sync jobs.
Logs Level: Default to ‘Info’ which captures errors, warnings, and info. Selected value is the LOWEST setting you’ll see in LS logs, so INFO is advised.
The Endpoints section has six Leadspace endpoints listed. There is no need to make changes here.
Input Field Mapping
Input field mapping allows you to set the target fields in your SFDC instance from which we are going to pull data when enriching said records. It’s critical that each object you plan on enriching through LS4SF have their respective input field mapping aligned to the fields from which their data is located.
The good news is that the LS4SF package does a historically great job of automatically mapping the correct input fields in your SFDC instance, but it’s best to confirm.
- Click on ‘Input Field Mapping’ on the left.
- Select the applicable object button and review the mapping.
- The left column is the field data we are looking for
- The right column is the mapped input field. You can click on each field dropdown to see an entire list of all fields available to be mapped in your system.
- Once you have confirmed that all fields are mapped correct, click the ‘Update Mapping’ button. You should see this message:
- Please repeat the above steps for all objects as needed.
Output Field Mapping
The last part of the setup is to set the Output Field Mapping for each object you will be using with the LS4SF application. During this part of the process, we will be creating and mapping Leadspace Custom fields in the desired objects you will be enriching.
There are five total objects that have their own Output Mapping tabs in LS4SF - Three of them are standard:
And two are Custom:
- Company (Custom)
- Person (Custom)
If you are using standard objects (recommended), you will only be able to update Accounts, Leads, and Contacts Output Mapping options.
If you are using custom objects, you will only be able to update Company and Person Output Mapping tabs. The standard tabs will be unavailable. For more information on custom objects, please refer to LS4SF: Using Custom Objects.
There’s a specific layout to each of the output mapping tabs that are consistent amongst each other.
Active: All fields default to ‘Active’. This indicates whether a field will be created and mapped during the initial mapping. For future mapping, it indicates whether a field will return data upon enrichment.
Recommendation from LS is to begin each mapping exercise by unchecking all active boxes for all fields (top ACTIVE box in column).
Override: All fields default to ‘Active’. This indicates whether the field will be overwritten with new Leadspace enrichment data upon subsequent enrichments.Leadspace recommends that all fields marked Active are also marked Override.
Leadspace Field: The label name of the LS field. You’ll also see a ‘NEW’ badge next to any field that is new to that object. Since this is the initial setup, all fields have this badge to begin with.
Field Type: Default field type defined by LS.
Map to Field: Defaults to ‘Create New Field’. This is a dropdown of all fields in your env to which you can map the LS fields. Recommendation here is to use ‘Create New Field’ unless you have already created LS fields manually in these objects.
Field Label: Field label of the field in Salesforce. Default will be the same as the Leadspace field name.
Internal Field: Internal API field name for the LS fields
Intent, Recommended, Common Columns: Fields checked in any of these boxes are Leadspace recommended, common, or intent only fields. This serves as a recommendation only and cannot be modified.
The mapping exercise should be discussed with your internal teams as needed, as this will dictate what fields will be created in Salesforce, and what data you will get back from Leadspace when you enrich records in the respective objects.
When you have decided which fields to map, please follow the process outlined here:
- As mentioned in the ‘Active’ description above, use the top ACTIVE button on the column to uncheck all fields by default. This will help to avoid any accidental or unwanted field creation and mapping.
- Check the ‘Active’ and ‘Override’ box for any field you want to create and map.
- Once you have all the desired fields marked active and override, click the ‘Update Mapping’ button.
- Allow the process to complete (1-5 mins.) and review the changes.
Note that now, the fields you did not create and map no longer have the ‘New’ badge but still have the value <Create New Field> in the Map To Field column.
Please repeat the mapping process for all objects you will be enriching through LS4SF.
Revenue Radar Reporting
New to package 5.33 is our new Revenue Radar reporting! Customers who are taking advantage of our Intent Modeling and/or Predictive Modeling can generate and customize a revenue radar report.
For more information on the Revenue Radar Report, please review the article from our KB https://support.leadspace.com/hc/en-us/articles/9865430129692-LS4SF-Revenue-Radar-Report.