Chat leads in every tool at once
Identify the visitor with email, name and company as soon as they share them. Segment updates the person in your CRM, email platform and ad audiences without a separate integration for each.
Segment chatbot integration
The Segment step sends what happens in a conversation to your Segment workspace as standard identify and track calls. From there Segment routes it to your analytics, warehouse, CRM and ad tools, so chat behaves like every other source in your stack.
Build on the Free plan. The Segment step runs on Pro ($39/month) and above.
- Builder step
- Segment: Identify or Track event
- How you connect
- HTTP API source write key
- Regions
- United States or European Union
- Plan
- Pro and above (native integrations)
What it does
What the Segment step can do
Conversations are some of the most telling events a visitor produces: they say what they want, what they are worried about and how ready they are to buy. Most chatbots keep that inside their own dashboard. The Segment step publishes it as data your whole stack can use.
Because it speaks Segment's own spec, nothing downstream needs to know about Conferbot. An identify call with an email updates the person in every destination you have connected, and a track call such as Demo Requested shows up in your funnels next to page views and sign-ups.
Identify the visitor
Tie the visitor to who they are with traits: email, name, first and last name, phone, company, job title, website or any custom trait, each filled from a chat variable.
Track an event
Record something the visitor did, such as Demo Requested or Quote Started, with properties like plan, budget or product, taken from their answers.
Anonymous until known
Leave User ID empty and the chat session ID is sent as Segment's anonymousId, so every call from one conversation ties together. Once you know who it is, put ${email} or your own user ID in; a step with a User ID sends that ID instead of the anonymous one.
Skipped questions send nothing
Trait and property rows with an empty value are left out, so a question the visitor skipped does not overwrite a good value in your destinations with a blank.
Safe to retry
Every call carries a unique message ID, which Segment uses to drop duplicates. Calls also carry the chatbot's ID, so you can tell bots apart in your data.
Your data region
Choose the United States or European Union endpoint to match where your Segment workspace is hosted.
Reference
Fields in the Segment step
| Operation | Fields |
|---|---|
| Identify | Segment source, User ID (optional), traits as key and value rows. |
| Track event | Segment source, User ID (optional), event name, properties as key and value rows. |
| Source (connection) | Write key from an HTTP API source, a name for the source, data region (US or EU). |
Setup
How to connect Segment to your chatbot
About five minutes. You need a Pro or higher Conferbot workspace and access to create a source in Segment.
- 1
Create an HTTP API source
In Segment, add an HTTP API source, or open an existing one, and copy its write key from Settings, API Keys.
- 2
Add the Segment step
Drag the Segment step into the flow where you have something worth recording: after the email question for Identify, after a key choice for Track.
- 3
Connect the source
Paste the write key, name the source and pick the data region. Tick the option to send a test event if you want to confirm the key; Segment can only confirm a write key by receiving data, so this records one Conferbot Connection Test event.
- 4
Choose Identify or Track
For Identify, add traits such as
email=${email}. For Track, name the event in Segment's usual Object Action style, such asDemo Requested, and add properties. - 5
Set the user ID
Leave it empty to use the anonymous chat session, or enter
${email}or your own user ID variable once the visitor is known. - 6
Test in the debugger, then publish
Preview the bot and watch the calls arrive in the source's debugger in Segment. Then publish.
Recipes
Flows people build with Segment
Conversation events in your funnel
Track Chat Started, Pricing Asked and Demo Requested so product and marketing see where chat helps conversion, next to the rest of your event data.
Qualification as traits
Send answers to qualifying questions, such as team size or use case, as traits. Sales tools downstream can then score and route the person without re-asking.
Onboarding signals
For a product's in-app bot, track which help topics users ask about during onboarding, so your product analytics show where people get stuck.
Access
Permissions and access
Write-only key
A write key can only send data into its source. It cannot read your Segment data or change workspace settings. It is stored encrypted in Conferbot.
One source per bot or many
Connect several sources if you want to keep bots apart, for example a website bot and a support bot, and pick the source in each Segment step.
Consent
Identify calls carry personal data. Only send traits your privacy policy covers, and use your consent tooling downstream as you do for other sources.
Good to know
Limits and behaviour to plan around
Segment's HTTP API limits
Segment accepts calls up to a size and rate limit per source. A chatbot sends one small call per Segment step, far below those limits. See Segment HTTP API.
Ten-second wait
The step waits up to 10 seconds for Segment. If Segment does not answer, the conversation continues and the call is not resent.
Region must match
An EU workspace needs the EU region on the source in Conferbot. With the wrong region, Segment rejects the write key.
Names are permanent
Event and trait names become columns and events in your destinations. Agree a naming plan before you publish; renaming later leaves the old names in history.
Troubleshooting
Fixing common Segment problems
| What you see | Why, and the fix |
|---|---|
| Segment rejected the write key | The key is wrong, was rotated, or the region does not match your workspace. Reconnect the source with the current key and the right region. |
| Calls do not appear in the debugger | The step is on a branch the test did not reach, or the source is disabled in Segment. Walk the exact path in preview and check the source is enabled. |
| Traits are missing | The variables were empty when the step ran, so those rows were skipped. Move the step after the questions that set them. |
| Track fails with no event | The event name is empty. Name the event in the step. |
| Anonymous and known profiles do not merge | A step with a User ID sends only that ID, not the session's anonymousId, so earlier anonymous calls stay separate. Ask for the email early and put the same User ID on every Segment step after it. |
FAQ
Segment integration: common questions
What does the chatbot send to Segment?
Standard identify calls with traits about the visitor, and track calls with an event name and properties. Each call is a normal Segment HTTP API call.
Which Segment source should I use?
An HTTP API source. Create one in Segment, or open an existing one, and copy its write key.
Which Conferbot plan includes Segment?
Segment is a native integration, included on Pro and above. You can build and preview the flow on any plan.
How are anonymous visitors handled?
When User ID is empty, the chat session ID is sent as the anonymousId, so all calls from one conversation belong together. A step with a User ID sends that ID instead, so ask for the email early if you want one profile.
Will a skipped question overwrite data with a blank?
No. Trait and property rows with empty values are left out of the call.
Does it support Segment's EU region?
Yes. Pick European Union when you connect the source if your workspace is hosted in the EU.
Why does connecting send a test event?
Segment cannot validate a write key without receiving data. The optional test records one Conferbot Connection Test event so you know the key works.
Can I tell which bot sent a call?
Yes. Every call carries the chatbot's ID in its context, so you can filter or split by bot downstream.
What happens if Segment is unavailable?
The conversation continues normally. The step waits up to 10 seconds and the call is not resent, so no duplicate events are created.
Make chat a first-class source in your data stack
Start free with Conferbot - the free plan includes 600 conversations a month and needs no credit card, so you can build the flow today. The Segment step switches on with Pro.
Checked against Conferbot's product and Segment's documentation on November 3, 2026: Segment HTTP API, Segment Identify spec, Segment Track spec.
Discover More
Continue exploring
Explore features, connect third-party tools, and browse ready-made templates.
Guides & Resources
Deep-dive pillar guides, real use cases, and the chatbot & AI glossary.
What Is a Chatbot?The complete beginner's guideCustomer Support ChatbotAutomate support & cut response timesLead Generation ChatbotCapture & qualify more leadsBest AI Chatbot BuildersCompare the top platformsWhat Is an AI Agent?AI agents explained, no jargonAI Agent vs ChatbotThe difference, side by sideChatbot ROI CalculatorSee your savings - free, no signupChatbot Use CasesReal-world chatbot examplesChatbot & AI GlossaryKey terms explained
Guides for Segment flows
Guides on measuring what chat does for your business.