|
| 1 | +--- |
| 2 | +title: Skalin Destination |
| 3 | +id: 6256de4a1fe40d47ffb0b707 |
| 4 | +--- |
| 5 | + |
| 6 | +## About Skalin |
| 7 | + |
| 8 | +[Skalin](https://skalin.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} calculates your customer health score and alerts you as needed. Your team can be more proactive, save time, and generate more revenue. |
| 9 | + |
| 10 | +This destination is maintained by Skalin. For any issues with the destination, [contact the Skalin Support team ](mailto:[email protected]). |
| 11 | + |
| 12 | + |
| 13 | +## Getting Started |
| 14 | + |
| 15 | +{% include content/connection-modes.md %} |
| 16 | + |
| 17 | +1. From the Destinations catalog page in the Segment App, click **Add Destination**. |
| 18 | +2. Search for "Skalin" in the Destinations Catalog, and select the "Skalin" destination. |
| 19 | +3. Choose which Source should send data to the "Skalin" destination. |
| 20 | +4. Go to the [Skalin plateform Segment integration page](https://app.skalin.io/#/integration/segment){:target="_blank"}, click on "Connect" button to create configuration, find and copy the **API Key** and "Skalin Client ID" in Segment connection section. |
| 21 | +5. Enter the **API Key** and **ClientID** in the "Skalin" destination settings in Segment. |
| 22 | + |
| 23 | +## Supported methods |
| 24 | + |
| 25 | +Skalin supports the following methods, as specified in the [Segment Spec](/docs/connections/spec). |
| 26 | + |
| 27 | +### Page |
| 28 | + |
| 29 | +Send [Page](/docs/connections/spec/page) calls to *feature*. For example: |
| 30 | + |
| 31 | +```js |
| 32 | +analytics.page('myFeature') |
| 33 | +``` |
| 34 | + |
| 35 | +Segment sends Page calls to Skalin as a `feature`. |
| 36 | + |
| 37 | + |
| 38 | +### Screen |
| 39 | + |
| 40 | +Send [Screen](/docs/connections/spec/screen) calls to *feature*. For example: |
| 41 | + |
| 42 | +```obj-c |
| 43 | +[[SEGAnalytics sharedAnalytics] screen:@"Home"]; |
| 44 | +``` |
| 45 | +
|
| 46 | +Segment sends Screen calls to Skalin as a `feature`. |
| 47 | +
|
| 48 | +
|
| 49 | +### Identify |
| 50 | +
|
| 51 | +Send [Identify](/docs/connections/spec/identify) calls to *identity*. For example: |
| 52 | +
|
| 53 | +```js |
| 54 | +analytics.identify('userId123', { |
| 55 | + |
| 56 | +}); |
| 57 | +``` |
| 58 | + |
| 59 | +Obtinaly, you can provide your CustomerID: |
| 60 | +```js |
| 61 | +analytics.identify('userId123', { |
| 62 | + |
| 63 | + trait: { |
| 64 | + groupId: 'myCustomerID' |
| 65 | + } |
| 66 | +}); |
| 67 | +``` |
| 68 | + |
| 69 | +Segment sends Identify calls to Skalin as an `identify` event. |
| 70 | + |
| 71 | + |
| 72 | +### Track |
| 73 | + |
| 74 | +Send [Track](/docs/connections/spec/track) calls to *feature*. For example: |
| 75 | + |
| 76 | +```js |
| 77 | +analytics.track('myFeature') |
| 78 | +``` |
| 79 | + |
| 80 | +Segment sends Track calls to Skalin as a `feature` event. |
0 commit comments