When a visitor is matched to a Salesforce Account, Qualified can push Signals data to your mapped Account fields and display activity in an Account 360 view directly on the Account record in Salesforce. This article walks you through setting up field mappings and configuring permissions, and explains when Signals data is pushed to Salesforce.
Before you begin
Before mapping fields in Qualified, your Salesforce admin needs to create new custom fields on the Account object in Salesforce to receive Signals data. There are two ways to do this:
- Unmanaged package: Download the Signals unmanaged package, which includes a collection of pre-built custom fields on the Account object, plus reports and dashboard components for visualizing Signals data.
- Manual setup: Have your Salesforce admin manually create the custom fields on the Account object.
Salesforce user permissions
To push Signals data into Salesforce, your Qualified integration user needs the following permissions:
| Object | Read | Edit |
|---|---|---|
| Accounts | X | X |
| Campaigns | X | X |
| Contacts | X | X |
| Leads | X | X |
| Opportunities | X | |
| The API Enabled permission must also be checked for the integration user. | ||
Warning: If you implemented Qualified before 2022, you'll need to update your existing integration user's permissions to add Edit access on Accounts.
Map Signals fields
Once your Salesforce admin has added the new fields on the Account object, you're ready to map them in Qualified.
Refresh your Salesforce fields
- Go to Settings → Integrations → Salesforce → Connection.
- Find the “Salesforce fields” section and click the Update fields button.
This pulls the latest custom fields from your Salesforce org into Qualified so they're available to map.
Map fields in Qualified
- Next, go to Settings → Signals → Salesforce.
- Under Signals Fields, map each Signals field (left column) to the corresponding Salesforce Account field (right column).
- Click Save.
How Signals data is pushed to Salesforce
Qualified pushes Signals data to Salesforce in two ways:
- After account activity: when a visitor from an account is on your site, Qualified pushes that account's updated Signals fields to Salesforce within about five minutes. These updates go out in small batches every five minutes, so your Account records stay close to real time.
- Nightly, for inactive accounts: each night, Qualified updates accounts that had no website activity that day. This keeps their Signals fields current, including any score decay from inactivity. The nightly update is delivered in batches of 5,000 accounts, so in a large org it can take a while for every account to update.
By default, Signals activity is aggregated by domain. When several Salesforce accounts share a domain, Qualified pushes the same combined Signals values to each of them.
Note: Signals can report on each account separately instead, which suits a flat Salesforce account structure better than a parent and child hierarchy. To turn this on for your organization, contact your Qualified Success Architect (QSA).
Salesforce API usage
Signals uses Salesforce's Bulk API to push data. Each push counts as one API call against your Salesforce org's daily API limit. Signals typically uses up to about 289 API calls per 24 hours: one for each five-minute batch, plus the nightly update.
Your org's daily API limit depends on your Salesforce contract. Your Salesforce admin can check current usage in Salesforce Setup.
Embedded Visualforce component (deprecated)
Note: If your team previously set up the Signals Account 360 view using the embedded Visualforce component, that configuration will continue to work, and no changes are needed on your end. When you're ready to migrate to the current setup, see Displaying Qualified Data in Salesforce with the Canvas App.
.svg)
