#Sales Cloud Einstein26 debatiendo

@Mariappan Perumal

Recommendation Builder does not expose the classic precision, recall, and F1 metrics you'd get from a hand-rolled recommender or even from Prediction Builder's scorecard. That's not you missing a screen. The model evaluation in Recommendation Builder is deliberately abstracted, and the single metric Salesforce surfaces is predicted lift, not accuracy or precision. So the honest framing for your evaluation is: you validate Recommendation Builder differently than you'd validate a model where you control the train/test split. 

Here's what's actually happening behind the scenes and how to work with it.

After you select your Recommended Item object, Interaction object, and Interaction types, the build runs two things you can act on. First the Data Checker, then the scorecard. The Data Checker validates whether each object has enough data to build a meaningful recommendation before it lets you proceed, and the scorecard then gives you the model's quality, top predictive factors, and predicted lift. 

Predicted lift is the metric to anchor on, and it's more useful than it first appears. Lift tells you how much better your recommendations are than simply suggesting the most popular items, and the recommended workflow is to use the scorecard to measure that, and if you're not happy, fine-tune the segments and settings and rebuild until performance is acceptable. So lift is your relative quality signal: a model that can't beat a popularity baseline by a meaningful margin isn't worth deploying.

On your two specific questions.

For "how is the model evaluated for accuracy and precision," the answer is that Salesforce evaluates it internally against held-out interaction data but does not expose precision/recall to you.  

For "what's the smart way to validate quality before production," since the tool won't give you offline precision, build your own holdout validation around it. This is the approach I'd take and the one worth bringing to a client:

Reserve a time-based holdout of interaction data that you exclude from the build window. Generate recommendations from the model, then check how many of those recommended items the same users actually interacted with in your held-out period. That gives you a real precision and hit-rate measurement that the tool doesn't surface, computed against ground truth you controlled. It's the closest thing to the precision/recall you're asking for, and it's defensible. 

Run a champion/challenger in production rather than a hard cutover. Deploy the recommendation inside a Next Best Action strategy and A/B test it against either the existing logic or a popularity baseline, measuring actual click-through or conversion lift on live traffic. Recommendations deploy by adding business rules in an NBA strategy, which is also where you control and gate them, so the strategy layer is your natural place to split traffic and measure real-world precision through behavior rather than an offline score. 

- SP 

@GlobalOne80 Admin Please check the Salesforce Help articles below for the resolution:

Please verify that the Salesforce user email matches the connected Exchange mailbox email address. Also, confirm that the user is added to the correct EAC configuration and reconnect the email account if needed.

Hello Tara, 

Yes, you should be able to use Einstein Opportunity Insights even with EAC turned off, provided Salesloft is creating activities directly in Salesforce and not storing them externally. EOI is mainly looking at engagement/activity signals around opportunities (emails, calls, meetings, tasks, etc.), so it generally cares more about the activity records existing and being correctly related to Opportunities, Contacts, or Leads rather than who created them. I’d just double-check how Salesloft is writing the data — if it’s creating standard Salesforce Tasks/Events with proper associations, you should be fine. The main risk is if some engagement data lives only inside Salesloft or custom objects, since Einstein may not pick those up. Hope this helps!

Hi @Lauren Bearinger,  

Yes, with Einstein Activity Capture 2-way sync, adding a new attendee to an old Outlook event can potentially trigger an updated calendar invite email to that person, depending on how Outlook/Exchange handles meeting updates. Salesforce itself does not send the invite, but the synced calendar system may treat it as a meeting update and notify the added attendee. 

To avoid accidental emails, it’s best to test with an internal user first or disable attendee notifications temporarily before updating older events.