# Matcha 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 **Matcha** 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.

[Matcha](https://www.matcha.co/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) provides scoring and insights based on product usage data for Product-Led Growth companies to better detect and use upsell opportunities.

This destination is maintained by Matcha. For any issues with the destination, [contact the Matcha Support team](mailto:support@matcha.co).

## Getting Started

1. From the Destinations catalog page in the Segment App, click **Add Destination**.
2. Search for **Matcha** in the Destinations Catalog, and select the **Matcha** destination.
3. Choose which Source should send data to the Matcha destination.
4. Ask your Account Manager for your **API key** or [contact the Matcha Support team](mailto:support@matcha.co).
5. Enter the **API Key** in the Matcha destination settings in Segment.

## Supported methods

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

### Page

Send [Page](/docs/segment/connections/spec/page) calls to allow Matcha to use pageviews information in the scoring. For example:

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

Segment sends Page calls to Matcha as a `pageview`.

### Screen

Send [Screen](/docs/segment/connections/spec/screen) calls to Matcha to use mobile information in the scoring. For example:

```objc
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
```

Segment sends Screen calls to Matcha as a `screenview`.

### Identify

Send [Identify](/docs/segment/connections/spec/identify) calls to relay identification information that will be used for cross references in Matcha's scoring. For example:

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

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

### Track

Send [Track](/docs/segment/connections/spec/track) calls to allow Matcha to better understand user interactions with your product and use it in the scoring. For example:

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

Segment sends Track calls to Matcha 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 Matcha  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 | Ask your Account Manager for getting an API Key | Yes      | string |