Rehook Destination

Rehook is a powerful and dedicated user-incentivization solution that enables businesses to reward and engage users without depending on tech teams. With an elegant and easy-to-use interface, Rehook is designed to help you run user-promotion campaigns that are flexible, customizable and scalable.

This destination is maintained by Rehook. For any issues with the destination, contact the Rehook Support team.

Getting started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for Rehook in the Destinations Catalog, and select the Rehook destination.
3. Select which Source should send data to the Rehook destination.
4. Open the Rehook Dashboard and navigate to Settings > API Keys & Secret Key. Copy your key.
5. Open the Segment app and paste the API Key & Secret Key in the Rehook destination settings page.

Supported methods

Rehook’s destination is designed to support the following Segment Spec methods. Because this is an Actions Destination, you can also map other Segment methods.

Identify

If you’re not familiar with the Segment Spec, take a moment to understand what the Identify method does. An example call looks like this:

Example 1:

analytics.identify('userId12345', {
  firstName: 'Bob',
  lastName: 'Dole',
  email: 'bob.dole@example.com',
  company: 'Initech',
  employees: 234
});

Example 2:

analytics.identify('userId12345', {
  firstName: 'Bob',
  lastName: 'Dole',
  email: 'bob.dole@example.com',
  company: 'Initech',
  employees: 234,
  referral_code: "ERTYUS"
});

Every time you make an Identify call with an included userId:

1. Rehook verifies that the userId exists.
2. If the userId does not 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.
3. If the userId exists, Rehook updates the user properties for the Customer against the Segment traits sent in the Identify call payload.
4. If referral_code is unique, Rehook updates the user properties in its database.

All of the traits recognized by Segment are translated and matched with the Rehook Customer user properties. These fields are automatically created or mapped for a Customer in Rehook and are available for personalization and advanced segmentation.

Track

If you’re not familiar with the Segment Spec, take a moment to understand what the Track method does.

An example call looks like this:

Example 1:

analytics.track('Product Viewed', {
  userId: "userId12345",
  product_id: '507f1f779439011',
  name: 'Monopoly: 3rd Edition',
  price: 18.99,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});

Example 2:

analytics.track('signup', {
  userId: "userId12345",
  referral_code: 'ERTYUS'
});

Segment sends Track calls to Rehook as a Custom Event. When you make a Track call, Segment sends the event to Rehook with the event name and all properties that you specified.

Destination Settings

Available Actions

Build your own Mappings. Combine supported triggers with the following Rehook-supported actions:

• Identify User

• Track Event

Identify User

Send the identify event to create or update the customer in rehook.

Identify User is a Cloud action. The default Trigger is: type = "identify"

Click to show / hide fields

Track Event

Send the Track event to rehook.

Track Event is a Cloud action. The default Trigger is: type = "track"

Click to show / hide fields

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.