# Personyze Destination

## Destination Info

* Accepts [Identify](/docs/segment/connections/spec/identify) calls.
* Refer to it as **Personyze** 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.

[Personyze](https://www.personyze.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is a complete cross-channel personalization solution for showing highly optimized content in websites, emails, and apps using targeting and recommendation engines, and a variety of content creation, editing, and A/B testing tools.

This destination is maintained by Personyze. For any issues with the destination, [contact the Personyze Support team](mailto:info@personyze.com).

## Getting Started

1. From the Segment web app, click **Catalog**.
2. Search for "Personyze" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter the "API Key" into your Segment Settings UI which you can find from your [Personyze dashboard](https://personyze.com/site/tracker/condition/index#cat=Account%20settings%2FMain%20settings%2FIntegrations/conditions) under Account Settings > Integrations > Segment > Get Keys
4. Once you've updated the API key in Segment, data from the source you selected will be shown right away in Personyze under "Manage Visitor Profiles".

## Identify

If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/segment/connections/spec/identify/) does. An example call would look like:

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

Identify calls will be sent to Personyze to update the Visitor Profile. You can see this updated under Dashboard > Users as well as in the Live Visits view.

The following traits are explicitly mapped in Personzyne:

* email
* firstName
* lastName
* phone
* gender
* age
* city
* country
* zip code
* interest
* industry
* role

All other traits will be sent to Personyze as custom string attributes and used for targeting. You can edit the default trait type of these traits within Personyze as needed, by going to:
Settings > Visitor Attributes > Visitor Attributes

## 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 Personyze  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 | In the Personyze dashboard, under Account Settings > Integrations > Segment > Get Keys, you’ll see your API Key. | Yes      | string |