|
| 1 | +--- |
| 2 | +title: Rehook Destination |
| 3 | +rewrite: true |
| 4 | +id: 64c02312ff0ce798cc8d1a7e |
| 5 | +--- |
| 6 | + |
| 7 | +[Rehook](https://rehook.ai/){:target="_blank"} is a powerful and dedicated user-incentivization solution that enables businesses to reward and engage users without any dependency on tech. With an elegant, easy-to-use interface, Rehook is designed to help you run user-promotion campaigns that are flexible, customizable, and scalable. |
| 8 | + |
| 9 | + |
| 10 | +Rehook maintains this destination; for any issues with the destination, [contact the Rehook Support team ](mailto:[email protected]). |
| 11 | + |
| 12 | + |
| 13 | +## Getting Started |
| 14 | + |
| 15 | + |
| 16 | + |
| 17 | +1. From the Destinations catalog page in the Segment App, click **Add Destination**. |
| 18 | +2. Search for **Rehook** in the Destinations Catalog, and select the **Rehook** destination. |
| 19 | +3. Choose which Source should send data to the Rehook destination. |
| 20 | +4. Go to the [Rehook Dashboard](https://dashboard.rehook.ai/){:target="_blank"} and navigate to **Settings > API Keys & Secret Key**, and copy it. |
| 21 | +5. Enter the **API Key & Secret Key** in the Rehook destination settings in Segment. |
| 22 | + |
| 23 | + |
| 24 | +## Supported methods |
| 25 | + |
| 26 | +Rehook supports the following methods, as specified in the [Segment Spec](/docs/connections/spec). |
| 27 | + |
| 28 | +### Identify |
| 29 | + |
| 30 | +Take a look at the [Identify method documentation](/docs/connections/spec/identify) to learn about what it does. |
| 31 | + |
| 32 | +```js |
| 33 | +analytics.identify('userId12345', { |
| 34 | + firstName: 'Bob', |
| 35 | + lastName: 'Dole', |
| 36 | + |
| 37 | + company: 'Initech', |
| 38 | + employees: 234 |
| 39 | +}); |
| 40 | +``` |
| 41 | + |
| 42 | +Every time you make an identify call with userId included: |
| 43 | +1. Rehook verifies that the userId exists. |
| 44 | +2. If the userId doesn’t exist, Rehook adds the user as a Customer to the Rehook database and matches user properties with the Segment `traits` sent in the identify call payload. |
| 45 | +3. If the userId exists, Rehook updates the user properties for the Customer against the Segment `traits` sent in the identify call payload. |
| 46 | + |
| 47 | +All the [special traits](/docs/connections/spec/identify#traits) recognized by Segment are translated and matched with the Rehook user properties for a Customer. These fields are automatically created or mapped for a Customer in Rehook and are available for personalization and advance segmentation. |
| 48 | + |
| 49 | +### Track |
| 50 | + |
| 51 | +Take a look at the [Track method documentation](/docs/connections/spec/track) to learn about what it does. An example call looks like: |
| 52 | + |
| 53 | +```js |
| 54 | +analytics.track('Product Viewed', { |
| 55 | + userId: "97980cfea0067", |
| 56 | + product_id: '507f1f77bcf86cd799439011', |
| 57 | + name: 'Monopoly: 3rd Edition', |
| 58 | + price: 18.99, |
| 59 | + url: 'https://www.example.com/product/path', |
| 60 | + image_url: 'https://www.example.com/product/path.jpg' |
| 61 | +}); |
| 62 | +``` |
| 63 | +Segment sends `Track` calls to Rehook as a Custom Event. When you call the track, Segment sends the event to Rehook with the event name and all properties that you specified. |
| 64 | + |
| 65 | +Be sure if you send an Identify or Track call without userId, the call will be dropped. |
0 commit comments