You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Iterate Source

Source Info

The Iterate Source is an Object Cloud source. This means that it sends information (traits) about a thing that exists and persists over time, such as a person or company, and which can be updated over time. Data from this source can only be exported directly to a warehouse, but it can then be used for further analysis. Learn more about cloud sources.

Iterate is a customer insights platform that helps you build better products by asking the right questions at the right time.

This is an Event Cloud Source, which export data into your Segment warehouse and federates that data into your other enabled Segment Destinations.

This source is maintained by Iterate. For any issues with the source, contact the Iterate Support team.

Getting started

From your workspace's Sources catalog page, click Add Source.
Search for "Iterate" in the Sources Catalog, select Iterate, and click Add source.
On the next screen, give the source a name and configure any other settings.
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example, Iterate_Prod, Iterate_Staging, or Iterate_Dev).
Click Add Source to save your settings.
From your Iterate settings page in the Segment UI, copy your write key.
Log in to your Iterate account.
Navigate to Company Settings > Integrations > Segment and paste the write key to connect.

Stream

Iterate sends survey response data to Segment as server-side Track events. These events are available in any destination that accepts server-side events and are available in a schema in your data warehouse for SQL querying.

The Iterate source uses the external_id (if one exists for the user) as the Segment userId. If an external_id is not available, Iterate passes the internal Iterate user ID as the anonymousId.

Identify

Iterate includes user traits within the context.traits object of the Track event. This updates the user's profile in Segment with the latest information collected in the survey.

For example:

The text of the answer, keyed by the question prompt or a custom attribute name.
User info like email, name, and phone, if collected by a "User Info" question type.

Events

The table below lists events that Iterate sends to Segment. These events appear as tables in your warehouse, and as regular events in other destinations. Iterate includes the userId, if available.

Event name	Description
`survey-question-response`	A user answered a specific question in a survey.

Event properties

The table below lists the properties included in the events listed above.

Property name	Description
`survey_id`	ID of the survey
`survey_name`	Name of the survey
`question`	The text prompt of the question answered
`response`	The answer provided by the user
`label`	(Optional) Custom attribute name configured for the question
`response_string`	The answer as a string (if applicable)
`response_int`	The answer as an integer (if applicable)
`response_array`	The answer as an array (for multi-select or matrix questions)
`response_year`	The year component (for date questions)
`response_month`	The month component (for date questions)
`response_day`	The day component (for date questions)
`response_properties`	Map of any additional traits associated with the response

Adding destinations

Now that you've set up your source, you can connect it to Destinations.

Log into your downstream tools and check to see that your events appear as expected and that they contain all of the properties you expect. If your events and properties don't appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.

If there are any issues with how the events are arriving to Segment, contact the Iterate support team.