Skip to main content
Send x-conversation-id on each search in one shopper conversation. Channel3 stores that id with the search and groups every catalog call that sends the same value: search, browse, image search, similar products, and product detail. A click or sale that comes from one of those searches stays on the conversation.
Strongly recommended for better analytics. A session is much easier to read when every call shares the id.
Use a stable id from your app for that conversation. 1–64 characters: letters, numbers, underscores, and hyphens. Send the same value on every later call in the session. Those grouped sessions show up in your Channel3 dashboard. Clicks and sales filter by user_id. They do not take a conversation id. Send x-conversation-id when your app calls /v1/search itself. The Conversational Agent is a separate path: pass conversation_id in the body of POST /v1/conversations to continue a thread, and Channel3 groups the searches that turn runs.