# Vidora Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Vidora** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

[Vidora](https://vidora.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) provides a Machine Learning Platform for Marketing, AdTech, and Product teams to quickly and easily transform raw consumer data into valuable business decisions. Examples include: [next-best-action](https://www.vidora.com/general/video-building-real-time-decisioning-in-cortex-for-next-best-offer-and-next-best-action), next-best-offer, [dynamic decisioning](https://www.vidora.com/ml-in-business/dynamic-decisioning-using-real-time-machine-learning), [predictions](https://segment.com/recipes/using-predictive-purchase-behavior-to-increase-campaign-roi/), and prescriptive modeling.

This destination is maintained by Vidora. For any issues with the destination, [contact the Vidora Support team](mailto:support@vidora.com).

## Getting Started

1. From the Destinations catalog page in the Segment App, click **Add Destination**.
2. Search for "Vidora" in the Destinations Catalog, and select the "Vidora" destination.
3. Choose which Source should send data to the "Vidora" destination.
4. Go to the [Vidora dashboard](https://app.vidora.com/#!/api/docs), find and copy the "API key".
5. Enter the "API Key" in the "Vidora" destination settings in Segment.

## Track

If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/segment/connections/spec/track/) to learn about what it does. An example call would look like:

```js
analytics.track("event_name", {
    property1: "example",
});
```

When sending any data to Vidora, a `timestamp` and either a `userId` or `anonymousId` are required.

Segment sends Track calls to Vidora as a `track` event with the `event_name` as the event type and will include any corresponding `properties`.

## Page

If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/segment/connections/spec/page/) to learn about what it does. An example call would look like:

```js
analytics.page({
    name: "page_name",
    properties: {
        property1: "example",
    },
});
```

When sending any data to Vidora, a `timestamp` and either a `userId` or `anonymousId` are required.

Segment sends Page calls to Vidora as a `pageview` event along with the `page name` and corresponding `properties`.

## Screen

If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/segment/connections/spec/screen/) to learn about what it does. An example call would look like:

```objc
[[SEGAnalytics sharedAnalytics] screen:@"screen_name"
                            properties:@{ @"property1": @"example" }];
```

When sending any data to Vidora, a `timestamp` and either a `userId` or `anonymousId` are required.

Segment sends Screen calls to Vidora as a `screenview` event along with the `screen name` and corresponding `properties`.

## Identify

If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/segment/connections/spec/identify/) to learn about what it does. An example call would look like:

```js
analytics.identify("userId123", {
    trait1: "example",
});
```

When sending any data to Vidora, a `timestamp` and either a `userId` or `anonymousId` are required.

Segment sends Identify calls to Vidora as an `identify` event along with any corresponding user `traits`.

## Group

If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/segment/connections/spec/group/) to learn about what it does. An example call would look like:

```js
analytics.group("groupId", {
    name: "Group Name",
    trait1: "example",
});
```

When sending any data to Vidora, a `timestamp` and either a `userId` or `anonymousId` are required.

Segment sends Group calls to Vidora as an `group` event along with any corresponding user `traits`.

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/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.

> \[!NOTE]
>
> Real-time audience syncs to Vidora  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.

| Field   | Description                                                                 | Required | Type   |
| ------- | --------------------------------------------------------------------------- | -------- | ------ |
| API Key | You can find your Vidora API key in the API>Documentation section of Cortex | Yes      | string |