# 💫 Segment Partner Destination Documentation

---
Nat.app Destination
---

[Nat.app](https://nat.app?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a CRM tool for founders and sales people that makes it easy to stay in touch with users and find product market fit.

This destination is maintained by Nat.app. For any issues with the destination, please [reach out to their team](mailto:[e-mail]).

> The Nat.app Destination is currently in beta, which means that they are still actively developing the destination. To join their beta program, or if you have any feedback to help improve the Nat.app Destination and its documentation, please [let their team know](mailto:mailto:[e-mail])!

## Getting Started

{% include content/connection-modes.md %}

1. From your Segment UI's Destinations page click on "Add Destination".
2. Search for "Nat.app" within the Destinations Catalog and confirm the Source you'd like to connect to.
3. Drop in the "API Key" into your Segment Settings UI which you can find from your [Nat.app's settings page](https://contacts.nat.app/settings).

## Identify

If you haven't had a chance to review our spec, please take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:

analytics.identify('userId123', {
  email: '[e-mail]'
});

Identify calls are sent to Nat.app as an `identify` event.

**Those are the only events this integration accepts and they need to contain an `email` and a `timestamp`to be accepted**.

Every `identify` event that contains an email will be added as an interaction to the timeline of the contact it is associated with. There can only be one event generated per day per contact, so as to keep our *closeness indicator* accurate.

Additionally, they can also include a `url` that will be added as a description to the event in the user's timeline.

Here is an example of an `identify` even that has been added to a timeline:

### Accepted data format
We accept multiple types of data format, so as to make the integration as easy as possible. Let's start with the recommended format:

#### Recommended format - with traits & page
The user email is stored in `traits` and the url in `page`.

{
"type": "identify",
"timestamp": "2020-05-31T17:55:47.263Z",
"traits": {
    "email": "[e-mail]"
  },
"page": {
      "url": "xxxxx"
    }
}

#### Alternative formats
Additionally, we also accept other formats that we created to satisfy specific customer needs. Please reach out to [e-mail] if you need a custom format.

*Example 1 - Without traits or url information*

{
"timestamp": "2020-05-31T17:55:47.263Z",
"type": "identify",
"email": "[e-mail]"
}
*Example 2 - With event information but without traits*
In this case, the `event`will replace the `url` in the app.

{
"timestamp": "2020-05-31T17:55:47.263Z",
"type": "identify",
"email": "[e-mail]",
"event": "User logged in",

},
}

### Required & Optional data
**Required: email & timestamp**
If the integration can't identify an `email` and a `timestamp`, an error will be returned. Please follow the recommended format.

**Optional: url**
A description data point is optional and needs to be called `url`. It will be added in the timeline as shown in the image above. If there is no `url`, a standard message will be added to the timeline instead.