Use Signals in your application

Once you've defined and published your attributes and interventions, your applications can consume them in two ways:

• Pull: retrieve calculated attribute values from the Profiles Store on demand, for example, to personalize a page or provide context to a chatbot
• Push: subscribe to interventions, so that Signals notifies your application as soon as a user meets the trigger criteria

Both patterns require a connection to Signals using the Python SDK, Node.js SDK, browser plugin, or API. If the consumer is an agent, it can instead discover and read the same data as tools through the Signals MCP server.

This section covers:

• Services: stable interfaces that group attribute group versions together for your applications, recommended for production use
• Retrieve attributes: fetch calculated attribute values using a service or directly from an attribute group
• Agentic contexts: fetch a user's recent session activity as JSON or a narrative summary, to ground your agents
• Signals MCP server: let your agent discover the attribute groups and agentic contexts your deployment publishes and read the ones that fit the task
• Subscribe to interventions: receive intervention payloads and react to them in your application