This preview of pull request 1639 is meant for internal use only.

Iron.io Destination

Iron.io quick info

Iron.io accepts Track, Page, Identify, Group, and Alias calls. If you reference it in the Integrations object, call it “Iron.io”.

Iron.io accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.

Getting Started

When you enable 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.

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

Personas

You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Supported Sources and Connection Modes

Before you start, make sure Iron.io supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode ⬜️ ⬜️ ⬜️
☁️ Cloud-mode

Segment offers an optional Device-based Connection Mode for Mobile data going to Iron.io, so that you can use Iron.io features that collect data directly from the mobile device. To do this, you must package the Segment-Iron.io mobile SDK with the Segment mobile library.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

Endpoint

Your Iron.io API endpoint.

Project ID

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

Token

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

This page was last modified: 20 Oct 2020



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account