Segment makes it easy to send your data to Iron.io (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Iron.io in the format they understand. Learn more about how to use Iron.io with Segment.
When you toggle on Iron.io in Segment, we’ll start sending data to an IronMQ instance with data for your account. Currently, Iron.io supports all of the Segment methods, and will send data from any one of our libraries.
When sending data to Iron.io, we’ll auto-fill a queue called “segment”. You can use Iron.io 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, Iron.io can act as an intermediary buffer.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Supported Sources and Connection Modes
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 Iron.io API endpoint.
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!