Segment makes it easy to send your data to (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to in the format they understand. Learn more about how to use with Segment.

Getting Started

When you toggle on in Segment, we’ll start sending data to an IronMQ instance with data for your account. Currently, supports all of the Segment methods, and will send data from any one of our libraries.

When sending data to, we’ll auto-fill a queue called “segment”. You can use as a message queue buffer in front of your webhook server or internal data processing cluster. For example, if you want to analyze your data as part of an ETL process, can act as an intermediary buffer.

Here’s a case study: How to Build an ETL Pipeline for ElasticSearch Using Segment and (’s blog)

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.


Your API endpoint.

Project ID

You can find your Project ID under the IronMQ settings for your project.


You can find your token under the IronMQ settings for your project.

If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!