Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
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.

Outgrow Source


Source Info
  • The Outgrow 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.

Outgrow(link takes you to an external page) provides a platform for marketers to create interactive content like calculators, quizzes, and assessments to better engage customers and generate personalized leads.

This is an Event Cloud source which can not only export data into your Segment warehouse, but can also make that data available to your other enabled Segment destinations.

This source is maintained by Outgrow. For any issues with the source, contact the Outgrow support team.


Getting started

getting-started page anchor
  1. From your Segment workspace's Sources catalog page, click Add Source.
  2. Search for "Outgrow" in the Sources Catalog, select Outgrow, and click Add Source.
  3. On the next screen, give the Source a name (for example, Outgrow_Production) and click Add Source to save your settings.
  4. Copy the Write Key from the Segment UI.
  5. Log in to your Outgrow account and follow the Outgrow integration setup guide(link takes you to an external page) to navigate to the integrations section of your content piece.
  6. Paste your Segment Write Key into the Outgrow configuration settings to connect the two platforms.

Outgrow uses the stream Source component to send Segment event data. It uses server-side Track and Identify methods to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.

Outgrow provides users the flexibility to map identifiers. The default behavior is for Outgrow to pass the field mapped by the user (such as an email address) as the userId.

Events

events page anchor

The following table lists events that Outgrow sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.

Event nameDescription
LEAD GENERATEDTriggered when a user completes a form or interaction within an Outgrow experience.

The following table lists the properties included in the events listed above. Outgrow allows for dynamic mapping, so the specific properties sent depend on your custom configuration.

Property nameDescription
emailThe email address captured in the Outgrow lead form (if mapped).
phoneThe phone number captured in the Outgrow lead form (if mapped).
userIdThe unique identifier for the user as mapped in the Outgrow settings.
nameThe name of the lead captured within the Outgrow experience (if mapped).

Now that your Outgrow source is set up, you can connect it with destinations.

Log in to 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 relevant destination docs for each tool for troubleshooting.

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