|
| 1 | +--- |
| 2 | +title: Matcha Destination |
| 3 | +id: 6286930129cf5f85d889854f |
| 4 | +--- |
| 5 | + |
| 6 | +[Matcha](https://www.matcha.co/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides scoring and insights based on product usage data for Product-Led Growth companies to better detect and use upsell opportunities. |
| 7 | + |
| 8 | +This destination is maintained by Matcha. For any issues with the destination, [contact the Matcha Support team ](mailto:[email protected]). |
| 9 | + |
| 10 | +## Getting Started |
| 11 | + |
| 12 | +{% include content/connection-modes.md %} |
| 13 | + |
| 14 | +1. From the Destinations catalog page in the Segment App, click **Add Destination**. |
| 15 | +2. Search for **Matcha** in the Destinations Catalog, and select the **Matcha** destination. |
| 16 | +3. Choose which Source should send data to the Matcha destination. |
| 17 | +4. Ask your Account Manager for your **API key ** or [contact the Matcha Support team ](mailto:[email protected]). |
| 18 | +5. Enter the **API Key** in the Matcha destination settings in Segment. |
| 19 | + |
| 20 | +## Supported methods |
| 21 | + |
| 22 | +Matcha supports the following methods, as specified in the [Segment Spec](/docs/connections/spec). |
| 23 | + |
| 24 | +### Page |
| 25 | + |
| 26 | +Send [Page](/docs/connections/spec/page) calls to allow Matcha to use pageviews information in the scoring. For example: |
| 27 | + |
| 28 | +```js |
| 29 | +analytics.page() |
| 30 | +``` |
| 31 | + |
| 32 | +Segment sends Page calls to Matcha as a `pageview`. |
| 33 | + |
| 34 | + |
| 35 | +### Screen |
| 36 | + |
| 37 | +Send [Screen](/docs/connections/spec/screen) calls to Matcha to use mobile information in the scoring. For example: |
| 38 | + |
| 39 | +```obj-c |
| 40 | +[[SEGAnalytics sharedAnalytics] screen:@"Home"]; |
| 41 | +``` |
| 42 | +
|
| 43 | +Segment sends Screen calls to Matcha as a `screenview`. |
| 44 | +
|
| 45 | +
|
| 46 | +### Identify |
| 47 | +
|
| 48 | +Send [Identify](/docs/connections/spec/identify) calls to relay identification information that will be used for cross references in Matcha's scoring. For example: |
| 49 | +
|
| 50 | +```js |
| 51 | +analytics.identify('userId123', { |
| 52 | + |
| 53 | +}); |
| 54 | +``` |
| 55 | + |
| 56 | +Segment sends Identify calls to Matcha as an `identify` event. |
| 57 | + |
| 58 | + |
| 59 | +### Track |
| 60 | + |
| 61 | +Send [Track](/docs/connections/spec/track) calls to allow Matcha to better understand user interactions with your product and use it in the scoring. For example: |
| 62 | + |
| 63 | +```js |
| 64 | +analytics.track('Login Button Clicked') |
| 65 | +``` |
| 66 | + |
| 67 | +Segment sends Track calls to Matcha as a `track` event. |
0 commit comments