Manage Talon.One customer profiles and custom attributes via the Integration API
domain: docs.talon.one · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Pre-create any custom attributes on the Customer profile entity in Campaign Manager (or via the Management API) before referencing them.
Choose an integration ID to represent each customer profile as its stable identifier.
Call PUT /v2/customer_profiles/{customerProfileId} with header Authorization: ApiKey-v1 {key} and an attributes map of built-in (Name, ShippingCity, etc.) and custom fields.
Bind sessions to the profile by setting profileId on subsequent customer_session calls so rule targeting and history accumulate on the profile.
Use the responseContent option on a session call to fetch profile data back in the same round trip instead of issuing a second request.
Known gotchas
Sending a custom attribute name that was never created in Campaign Manager fails with a 400.
The same per-customer concurrency limit (3 in-flight, small queue, then 409) applies to profile updates, session updates, and event tracking together.
Talon.One documentation discourages anonymous sessions (no profileId) since you lose profile-level targeting and history.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?