Spideo Destination

Destination Info
Partner Owned
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Spideo is the leading company in video and cultural content recommendation.

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

Getting Started

  1. From the Destinations catalog page in the Segment App, click Add Destination.
  2. Search for “Spideo” in the Destinations Catalog, and select the “Spideo” destination.
  3. Choose which Source should send data to the “Spideo” destination.
  4. Use the same API key that you are using for your existing Spideo integration, as provided by the Spideo team.
  5. Enter the “API Key” in the “Spideo” destination settings in Segment.

Supported methods

Spideo supports the following methods, as specified in the Segment Spec.

Track

Send Track calls to track user interactions, such as content watched or clicked, on your platform. For example:

analytics.track('Video Content Watched',{
    asset_id: 'xyz'
});

Track events sent from Segment to Spideo will surface as different Spideo interaction types (for example ‘play’, ‘click’, ‘buy’), depending on the event contents. These events will be used to personalize future user recommendations, and will feed Spideo’s analytics Explore platform.

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.

Real-time to batch destination sync frequency

Real-time audience syncs to Spideo may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

Settings

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

Setting Description
API Key
(required)
string. The API key to use is the same API key you are already using for your Spideo integration
client
(required)
string. Please enter your client name here (should be the same as the prefix of your Spideo API URL)

This page was last modified: 28 Aug 2023



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account