Skip to main content
Once you’ve verified it, the context tells you who is looking at which contact, in which CRM. A decoded context looks like this:

Fields

Treat any field not marked “Always” as optional, and ignore fields you don’t know: Rollout may add more. The context never carries the contact’s emails or phone numbers. To read them, and the rest of the contact’s data, use the Universal API.

Ids are unique per marketplace

The ids in user, crm and org are the CRM’s own. They’re unique within one marketplace, not across marketplaces: two CRMs can both have an agent AG123. Key everything you store by x.marketplaceId as well.

Identifying the agent

user.id is stable for an agent within one marketplace. To recognize an agent on later launches, link the pair (x.marketplaceId, user.id) to their account in your app the first time they sign in:
On each launch, look up the pair. If it’s linked, show the app for that user. If it isn’t, ask the agent to sign in. See Signing agents in. To group agents by team or office, use org.id, again together with x.marketplaceId.