Einstein Relationship Insights
Einstein Relationship Insights (ERI) is a Sales Cloud feature that scans external sources (news, the web, public profiles) to surface relationship signals about Accounts, Contacts, and Leads in the CRM.
Definition
Einstein Relationship Insights (ERI) is a Sales Cloud feature that scans external sources (news, the web, public profiles) to surface relationship signals about Accounts, Contacts, and Leads in the CRM. The product flags newsworthy events (executive changes, acquisitions, funding announcements), maps relationship paths between people in the org and people at the target account, and presents the signals as a research card pinned to the record. Reps use ERI to walk into a sales meeting informed about the customer without spending the prep time on Google.
Relationship Insights is one of the older Sales Cloud Einstein features and has gone through several rebrands. The core promise has stayed the same: turn the unstructured signal scattered across LinkedIn-style relationship data, news feeds, and public business directories into a structured panel inside Salesforce. Adoption tends to be highest in enterprise sales motions where deal cycles are long and the cost of walking into a meeting cold is high. For SMB-focused sales motions with short cycles, the feature can feel heavyweight.
What signals Einstein Relationship Insights surfaces and how it builds them
The research card on the record
The ERI experience centers on a research card pinned to an Account, Contact, or Lead. The card shows recent news about the target, organizational changes (new executives, departures, mergers), relationship paths between the rep's company and the target, and selected biographical highlights for key contacts. The card is a Lightning component that an admin places on the page layout. Reps glance at it before a meeting; they do not navigate into it on every record open. The pin-and-glance pattern is the design intent.
Where the signal comes from
ERI ingests data from multiple external sources: licensed news feeds, public business directories, Salesforce-managed identity graphs, and partner integrations. The exact source mix is curated by Salesforce, not configured by the admin. The customer cannot point ERI at a specific feed or exclude a specific source. This trade gives ERI broad coverage without per-customer source maintenance, but it also means the customer cannot tune the signal to their specific industry intelligence needs.
Relationship paths and the connector model
Beyond news, ERI maps relationship paths: for a target contact, who at the rep's company has a prior connection to them or to someone in their network. The connection signal draws from email and calendar metadata captured by Einstein Activity Capture (when EAC is also enabled), prior CRM activity, and public profile overlap. The visualization shows a graph of who-knows-whom, which is most useful for breaking into accounts where the rep has no direct contact. The data quality depends heavily on how much activity is being captured.
News alerts and event-driven outreach
ERI generates alerts when a high-signal event affects a tracked Account or Contact: a funding round, an executive change, a product launch. Alerts can be surfaced in the platform email digest, in the research card, or wired to flows for downstream automation (auto-create a Task, post to a Chatter group, alert the AE). Event-driven outreach is the highest-ROI use of ERI in B2B sales motions: a well-timed congratulations message after a funding round opens conversations that cold outreach cannot.
Privacy, GDPR, and data freshness
ERI's data comes from public and licensed sources, which keeps it on the right side of most privacy regimes, but the customer still owns disclosure and consent posture for any contact stored in their CRM. Data freshness varies by source: news alerts can be near real-time, while organizational profile data may lag by weeks. The product does not expose a per-record freshness indicator, which sometimes leads to reps citing stale information in conversations. Verify before quoting.
How ERI fits with Einstein Activity Capture
ERI and Einstein Activity Capture compose. EAC supplies the internal connection graph (who at the company has emailed whom at the target). ERI overlays the external signal (news, public relationships). The combined view is far more valuable than either feature alone, which is why most teams enable both together. Without EAC, ERI relationship paths are limited to CRM activity history, which is usually thin.
Adoption patterns and when ERI underdelivers
ERI works best in enterprise sales motions with multi-stakeholder deals and long cycles. It underdelivers in SMB motions where prep time is constrained and every minute counts. The feature also struggles in industries with thin external data coverage (some regional markets, some specialized B2B niches). Pilot ERI with two or three power reps before committing to a wider rollout; their experience predicts whether the rest of the team will get value or treat it as noise.
How to enable Einstein Relationship Insights and pilot adoption
ERI is an admin-enabled feature with a permission set for users. The work is choosing the pilot cohort and configuring how the signal surfaces on pages.
- Confirm licensing
ERI requires its own license in many editions. Confirm with the AE before scoping the rollout.
- Enable in Setup
Setup, Einstein Relationship Insights, enable. The platform-side enablement provisions the data sources and surfaces.
- Add the research card to page layouts
In App Builder, drop the Relationship Insights component on Account, Contact, and Lead pages. Position it where reps actually look (often on a research or summary tab).
- Pilot with a small cohort
Assign the permission set to two or three power reps. Pilot for two weeks. Collect feedback on whether the signal is helping their actual meetings.
- Decide rollout based on pilot signal
If the pilot reps cite specific wins, expand. If they describe the feature as background noise, hold and re-evaluate. ERI value is real but not uniform across motions.
Which page layouts and tabs show the card. Most teams pin to Account, Contact, and Lead summary pages.
Where event alerts surface: digest email, research card, flow-triggered automation. Configurable per event type.
Enable Einstein Activity Capture in parallel for richer relationship paths. ERI works without EAC but the graph is thinner.
Use Einstein Relationship Insights permission. Required for users to see the data. Pilot via this set.
ERI respects CRM sharing rules on the parent record. A rep without access to an Account does not see the ERI card for it.
- Data source mix is curated by Salesforce, not customer-configurable. Industries with thin external data coverage may see low signal density.
- Data freshness varies by source. The card has no per-record freshness indicator; verify before quoting in customer conversations.
- ERI alone is half the picture. Pair with EAC for richer relationship graphs; without EAC the paths are usually thin.
- Adoption patterns are uneven. Enterprise sales motions get value; SMB motions often do not. Pilot before committing to a wide rollout.
- Disclosure and consent for stored contact data remain the customer's responsibility, not the platform's, even when ERI sources are public.
Trust & references
Cross-checked against the following references.
- Einstein Relationship InsightsSalesforce Help
- Einstein for SalesSalesforce Help
Straight from the source - Salesforce's reference material on Einstein Relationship Insights.
- Einstein Relationship Insights overviewSalesforce Help
- Einstein Relationship Insights setupSalesforce Help
Hands-on resources to go deeper on Einstein Relationship Insights.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Einstein Relationship Insights surface?
Q2. What problem does Relationship Insights solve?
Q3. What's a typical use case?
Discussion
Loading discussion…