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.

Inflection Source


Source Info
  • The Inflection Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.

Inflection(link takes you to an external page) provides a B2B marketing automation platform for product-led growth companies.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.

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


Getting Started

getting-started page anchor
  1. From the Sources catalog page(link takes you to an external page) in your workspace, click Add Source.
  2. Search for "Inflection" in the Sources Catalog, select Inflection, and click Add Source.
  3. On the next screen, give the Source a nickname configure any other settings.
  4. Click Add Source to save your settings.
  5. Copy the Write key from the Segment UI and log in to your Inflection account - navigate to Connections > Add a new connection > Segment Integration > Select Source > and paste the write key in the Segment as Destination Field.

Inflection uses its stream Source component to send Segment event data. It uses a server-side (select from Track, Identify, Page, Group) methods to send data to Segment.

Inflection passes the userId associated with the email recipient as the userId. In cases where Inflection does not have an associated userId value, Inflection passes personId to Segment as an anonymousId. When Inflection receives the userId for the email it sends an Identify call with both the personId and userId to Segment.


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

Event NameDescription
Email DeliveredEmail was sent successfully
Email OpenedProspect opened the email
Email Unique OpensUnique email open by a prospect
Email BouncedEmail servers rejected the email
Email Reported as SpamProspect reported the email as spam
Link ClickedProspect clicked the tracking link
Unique Link ClickUnique tracking link click by a prospect
Unique Link Click per Unique OpenUnique tracking link click per unique open by a prospect
Email UnsubscribedProspect clicked the unsubscribe link

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

Property NameDescription
eventEmail event type
userIdProspect email ID
email_idID of the email
campaign_idCampaign ID
campaign_run_idCampaign Run ID
campaign_nameCampaign Name
email_subjectSubject line of the email
email_link_urlURL of the link clicked
is_unique_openUnique email open by a prospect (true or false)
is_unique_clickUnique tracking link by a prospect (true or false)

Now that your Source is set up, you can connect it with 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 Inflection support team.