|
| 1 | +--- |
| 2 | +title: Inflection Destination |
| 3 | +id: 62260e5dbc37b83046a847be |
| 4 | +--- |
| 5 | + |
| 6 | +[Inflection](https://www.inflection.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides a B2B marketing automation platform for product-led growth companies. Combining Segment data with CRM data to create a single view of the customer, Inflection was built with marketing teams in mind, pricing a platform that can drive hyper-contextualized communications to support adoption, expansion, and engagement. |
| 7 | + |
| 8 | +This destination is maintained by Inflection. For any issues with the destination, [contact the Inflection Support team ](mailto:[email protected]). |
| 9 | + |
| 10 | +## Getting Started |
| 11 | +{% include content/connection-modes.md %} |
| 12 | + |
| 13 | +1. From the Destinations catalog page in the Segment App, select **Inflection**. |
| 14 | +2. Choose the Source from which events have to be sent to Inflection destination. |
| 15 | +3. [Contact the Inflection Support team ](mailto:[email protected]) and get an **API key ** generated for your account. |
| 16 | +4. Enter the **API Key** in the Inflection destination settings on Segment. |
| 17 | +5. Once data starts flowing in from Segment to Inflection, the stats can be viewed on the Connections page on Inflection App. |
| 18 | + |
| 19 | + |
| 20 | +## Supported methods |
| 21 | + |
| 22 | +Inflection supports the following methods, as specified in the [Segment Spec](/docs/connections/spec). |
| 23 | + |
| 24 | +### Page |
| 25 | + |
| 26 | +Send [Page](/docs/connections/spec/page) calls to be added to *Product Activity* on Inflection App. For example: |
| 27 | + |
| 28 | +```js |
| 29 | +analytics.page() |
| 30 | +``` |
| 31 | + |
| 32 | + |
| 33 | +### Screen |
| 34 | + |
| 35 | +Send [Screen](/docs/connections/spec/screen) calls to be added to *Product Activity* on Inflection App. For example: |
| 36 | + |
| 37 | +```obj-c |
| 38 | +[[SEGAnalytics sharedAnalytics] screen:@"Home"]; |
| 39 | +``` |
| 40 | +
|
| 41 | +
|
| 42 | +### Identify |
| 43 | +
|
| 44 | +Send [Identify](/docs/connections/spec/identify) calls to Identify a user. The traits should have the `email` trait to be processed. All the other reserved traits are optional, but will be used to populate *Person DB* if available. |
| 45 | +If a *Data Warehouse* is set to sync *Person DB* data to Inflection, the Identify call will be used only to map the `userId` to the `person.id` on Inflection app. |
| 46 | +For example: |
| 47 | +
|
| 48 | +```js |
| 49 | +analytics.identify('userId123', { |
| 50 | + |
| 51 | +}); |
| 52 | +``` |
| 53 | + |
| 54 | + |
| 55 | +### Track |
| 56 | + |
| 57 | +Send [Track](/docs/connections/spec/track) calls to be added to *Product Activity* on Inflection App. For example: |
| 58 | + |
| 59 | +```js |
| 60 | +analytics.track('Login Button Clicked') |
| 61 | +``` |
0 commit comments