# Markettailor destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Markettailor** 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.

[Markettailor](https://www.markettailor.io/), helps B2B marketers create personalized websites without code, leveraging company data, audience insights, and recommendations.

Markettailor maintains this destination. For any issues with the destination, contact the Markettailor Support team.

## Getting Started

1. From the destinations catalog page in the Segment App, click **Add destination**.
2. Search for "Markettailor" in the destinations Catalog, and select the Markettailor destination.
3. Choose which Source should send data to the Markettailor destination.
4. Go to the [Markettailor Integrations page](https://app.markettailor.io/integrations), find the Segment integration, click **Authorize**, and copy the API key.
5. Enter the API Key in the Markettailor destination settings in Segment.

## Supported methods

Markettailor supports the following methods, as specified in the [Segment Spec](/docs/segment/connections/spec).

### Page

Send [Page](/docs/segment/connections/spec/page) calls to Markettailor. For example:

```js
analytics.page()
```

Segment sends Page calls to Markettailor as a `page view`.

### Identify

Send [Identify](/docs/segment/connections/spec/identify) calls to Markettailor. For example:

```js
analytics.identify('userId123', {
  email: 'john.doe@example.com'
  });
```

Segment sends Identify calls to Markettailor as an `identify` event.

### Track

Send [Track](/docs/segment/connections/spec/track) calls to Markettailor. For example:

```js
analytics.track('Login Button Clicked')
```

Segment sends Track calls to Markettailor as a `track` event.

## 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 Markettailor destination 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 API key in the popup when clicking "Authorize" for Segment under the Integrations tab. | Yes      | string |