What this means for your store
Lightning embed drops a CRM Analytics dashboard or lens onto a record page, home page, or Experience Cloud site. Bind filters to the page's AccountId or OpportunityId and the widget follows as reps click through accounts - no separate analytics tab. For hybrid field + ecommerce account managers, that closes the gap between activity timelines and trend charts.
Scenario on a real storefront
A US packaging supplier embeds “Account Revenue & Pipeline” on the Account page. AccountId from the record drives the dashboard filter:
# Lightning App Builder → Account Record Page
# Component: CRM Analytics Dashboard
# Dashboard: Account_360_CRMA
# Height: 600px
# Filter: AccountId = {!Record.Id}
# Dashboard widget (preconfigured in CRMA):
# Field: AccountId
# Operator: equals
# Value: {{column.AccountId}}
# Opportunity page: second widget bound to OpportunityId
# Experience Cloud: partner licence + RLS on partner accountsWhat to do next
- Embedded widgets inherit CRMA access and RLS - test as the rep persona, not system admin.
- Three half-loaded charts slow Lightning more than one focused dashboard; keep the layout tight.
- Mobile Salesforce has limited embed support - check phone layout before promising field reps a pocket pipeline view.
Bottom line
Lightning embed puts analytics where sellers already work. Bind Account or Opportunity IDs, lean layout, validate RLS under each profile before rollout.