# events.win Destination

## Destination Info

* Refer to it as **events.win** 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.
* This destination is **Beta.**

[events.win](https://events.win/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) provides a single platform to create your tracking plan, sync event definitions to your code, and see detailed metrics on how correct your data is. With events.win, you can ensure that your tracking is accurate and up-to-date.

This destination is maintained by events.win. For any issues with the destination, [contact the events.win support team](mailto:hi@events.win).

## Getting started

1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "events.win".
2. Select events.win and click **Add Destination**.
3. Select an existing Source to connect to events.win.
4. Go to the [events.win dashboard](https://app.events.win/developers), find and copy the **Developer key**.
5. Return to Segment and enter the **Developer Key** in the events.win destination settings.
6. events.win starts to receive data from Segment. There may be a delay before data is visible in the events.win dashboard.

## Supported methods

events.win supports Segment's [Track](/docs/segment/connections/spec/track) method, as specified in the [Segment Spec](/docs/segment/connections/spec).

### Track

events.win consumes and validates [Track](/docs/segment/connections/spec/track) calls against the tracking plan you've previously defined in events.win. events.win doesn't store the data, but instead provides a detailed report on how correct your data is.

You can use the [@events.win/cli](https://www.npmjs.com/package/@events.win/cli) to generate type-safe tracking code for your events.

```js
/**
 * Example:
 * events.win will look at your spec for the event `login-button-clicked` and validate the properties `handle` and `id` are present and have the correct data type.
 */
analytics.track("login-button-clicked", {
  user: {
    handle: "frodo.baggins",
    id: "123456789",
  },
});
```

## 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 events.win  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   |
| ------------- | ----------------------------- | -------- | ------ |
| Developer Key | Your events.win developer key | Yes      | string |