Data 360
Stillwater House · Agent Memory, live
Data 360 Agentic Memory shared by agents on Google, Salesforce and AWS
Maya ChenContact = Data 360 Individual
One guest, one memory, every agentEach memory is colored by the agent whose conversation produced it
reads memory saves memory
Step by stepLIVE
Behind the scenes
ACE Demo Studio · setup

Connect your Salesforce org

The studio runs the Stillwater story against your own SDO: a Google ADK agent, an AWS Strands agent and an Agentforce agent sharing one guest’s memory in Data 360. Connect your org, then fix anything the checklist flags.

Your org

Setup → My Domain.
Settings → Consumer Key and Secret (Salesforce emails you a code first).
Your secret stays in this server’s memory for your session only. It is never saved, logged or sent back to your browser; you re-enter it after the server restarts.

What the org needs first

  1. Data 360 live (Data Cloud Setup Home says “live and connected”). This is the one step you must do yourself; on a new SDO it takes about an hour.
  2. The three agent registrations (Stillwater_Web_Concierge, Stillwater_Guest_Services, Stillwater_Trip_Planner) and the test guest Maya Chen. The checklist can create these for you.
  3. With Client Credentials only: an External Client App with Client Credentials on (and again under OAuth Policies), a Run As user and the scopes api, cdp_ingest_api, cdp_profile_api, cdp_query_api.
  4. Optional: the Agentforce Guest Services agent and Agentforce Session Tracing.
The setup guide walks through each of these on a brand-new SDO.

Checklist

Connect your org to run the checks.