Recombee Destination

The new Recombee destination built on the Segment Actions framework provides the following benefits over the classic Recombee AI destination:

• Streamlined Configuration: You can now create mappings in a dedicated tab in the Segment web app, as opposed to needing to edit this in the destination's settings. This allows you to configure the mappings on a per-event basis and makes it easier to verify that your mappings work as intended.
• Removable Bookmarks: You can now use the Delete Bookmark Action to remove the bookmark interaction from the Recombee database.

Recombee recommends ensuring that a Recombee (Actions) destination and a classic Recombee AI destination connected to the same source are not enabled at the same time in order to prevent errors.

Recombee made the following configuration changes when setting up the new destination:

• Renamed the API Key setting to Private Token: This better reflects the type of token required.
• Removed the Track Events Mapping setting: If you want to map custom events to Recombee interactions, create your own mappings on the Mappings tab in the Segment app.
• Removed the Item ID Property Name setting: This functionality is now available in Segment's native Mappings tab. Ensure that your mappings use the desired property for the Item ID action field.
• In presets, the Item ID property is determined differently: In the default settings, the asset_id property (or sku for Ecommerce events) is now the fallback property, instead of name. The name property is never used by default, as it may not conform to the required Item ID format. The property content_asset_id (or the first ID in content_asset_ids,) is now the default Item ID only in Video events, where they are always present.

1. If you don't already have one, set up a Recombee account.
2. From the Segment web app, navigate to Connections > Destinations and click Add Destination.
3. Select Recombee and click Add Destination.
4. Select an existing Source to connect to Recombee.
5. Navigate to the Recombee Admin UI and complete the following actions:
   • Choose the Recombee Database where you want to send the interactions.
   • Click Settings in the menu on the left.
   • In the API ID & Tokens settings section, find the Database ID and the Private Token of the Database.
6. Back in the Segment app, navigate to the settings page of the Recombee destination you created.
   • Copy the Database ID from the Recombee Admin UI and paste it into the Database ID field in the destination settings.
   • Copy the Private Token from the Recombee Admin UI and paste it into the Private Token field in the destination settings.

Once you send the data from Segment to the Recombee destination, you can:

• Open the KPI console of the Recombee Admin UI to see the numbers of the ingested interactions (updated in realtime).
• Select the ID of an Item (or User) in the Items (or Users) catalog section in the Admin UI to view a specific ingested interaction.

Recombee has the following presets

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

• Add Cart Addition
• Set View Portion from Watch Time
• Delete Bookmark
• Add Detail View
• Add Rating
• Merge Users
• Add Bookmark
• Delete Cart Addition
• Add Purchase
• Set View Portion

Adds a cart addition of the given item made by the given user.

Add Cart Addition is a Cloud action. The default Trigger is type = "track" and event = "Product Added"

Sets the viewed portion of a given item (e.g. a video or article) by the given user. Use this action when you have the watch time of the item (e.g. in seconds) instead of the portion watched.

Set View Portion from Watch Time is a Cloud action.

Deletes a bookmark of the given item made by the given user.

Delete Bookmark is a Cloud action. The default Trigger is type = "track" and event = "Product Removed from Wishlist"

Adds a detail view of the given item made by the given user.

Add Detail View is a Cloud action.

Adds a rating of the given item made by the given user.

Add Rating is a Cloud action.

Merges interactions (purchases, ratings, bookmarks, detail views, ...) of two different users under a single user ID.

Merge Users is a Cloud action. The default Trigger is type = "alias"

Adds a bookmark of the given item made by the given user.

Add Bookmark is a Cloud action. The default Trigger is type = "track" and event = "Product Added to Wishlist"

Deletes a cart addition of the given item made by the given user.

Delete Cart Addition is a Cloud action. The default Trigger is type = "track" and event = "Product Removed"

Adds a purchase of the given item(s) made by the given user.

Add Purchase is a Cloud action.

Sets the viewed portion of a given item (e.g. a video or article) by the given user. Use this action when you have the viewed portion as a number between 0 and 1.

Set View Portion is a Cloud action.

You can inform Recombee that a specific interaction resulted from a successful recommendation (meaning the recommendations were presented to a user and the user clicked on one of the items) by setting the ID of the successful recommendation request in the Recommendation ID field of the action (this is the recomm_id property by default). You can read more about this setting in Recombee's Reported Metrics documentation

Sending the Recommendation ID gives you precise numbers about successful recommendations in the KPI section of the Recombee Admin UI. This explicit feedback also helps improve the output of the recommendation models.

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.

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