> ## Documentation Index > Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt > Use this file to discover all available pages before exploring further. # Personyze > Send Zeotap CDP audiences and profile attributes out to Personyze, so a Personyze campaign can target the visitors who qualified. ## What this is The Personyze destination sends audiences and profile attributes **out of** Zeotap CDP and into Personyze, where they become a visitor attribute you can target a Personyze campaign on. Nothing flows back the other way: the [Integrations Master List](/articles/integrations-master-list-publication/integrations-master-list) records Personyze as a Destination only, so there is no Personyze source page to read alongside this one. Personyze is a personalisation solution that uses machine learning and behavioural targeting to deliver cross-channel experiences. Once a Zeotap CDP audience has been delivered, Personyze can use it in its own Targeting and Personalisation rules. Zeotap CDP ships two separate Personyze destinations: * **Personyze** — this page. A batch destination, attached to an audience in the **Audiences** application, that sends the audience and its mapped attributes. * **[Personyze Real Time Integration](/articles/integrate-customer/personyze-real-time-integration)** — a real-time destination, attached to a **Send to Destinations** node in a journey, that sends events and user profiles as customers flow through. Both send data in the same direction — out of Zeotap CDP to Personyze. Choose the one that matches where you are activating from, Audiences or Journeys. ## Supported identifiers and actions This integration supports raw email addresses, Custom IDs, First Name, Last Name, Phone and Industry. | Action | [ID extension](/articles/segment-customer/extend-your-audience#id-extension) | [Delete](/articles/segment-customer/delta-upload-and-delete-functions) | [Delta upload](/articles/segment-customer/delta-upload-and-delete-functions) | | :- | :- | :- | :- | | **Send Attributes to Personyze** | – | – | – | Because delta upload and delete are not supported, each refresh sends the audience membership as it stands at the time the refresh runs. ## Prerequisites In Zeotap CDP: * An account with permission to create and edit destinations. For the wider destination model — platforms, actions and mappings — see [Destinations](/articles/integrate-customer/destinations). * An [audience](/articles/segment-customer/create-an-audience) defined with the criteria for the cohort you want to send, since the audience name has to be reproduced exactly on the Personyze side. In Personyze: * An active Personyze account. * Permission to view the **Settings → Integrations** screen, so you can obtain the Private API Key. * Permission to add visitor attributes and to edit campaign targeting rules. ## Get your Personyze Private API Key The Private API Key is the encryption key that authenticates API calls in Personyze. Obtain it before you create the destination in Zeotap CDP. Log into the Personyze console and navigate to **Settings → Integrations**. Personyze console showing the Campaigns screen, with Settings and Integrations highlighted in the left navigation below Content Placement, Conversion Tracking, Visitor Attributes and Recommendations On the **Integrations** screen, click **Get keys** on the **Full-featured API** tile. Personyze Integrations screen listing third-party application tiles including Segment, Full-featured API, Google analytics and HubSpot, with the Full-featured API tile's Get keys control opened to a popover containing a key field, a Revoke link and a Generate another key button Copy the key and store it somewhere safe. You enter it in the **Private API Key** field when you create the destination in Zeotap CDP. The same popover carries **Revoke** and **Generate another key** controls. If you revoke or regenerate this key later, update the Zeotap CDP destination with the replacement, or deliveries stop authenticating. ## Create the Personyze destination Log into the Zeotap CDP App and go to the **DESTINATIONS** application. Click **+ Create Destination**. Zeotap CDP Integrate Destinations screen on the Private Destination tab, showing a table of existing destinations with ID, destination name, created date and last updated columns, and the Create Destination button highlighted top right Under **All Destinations**, search for **Personyze**. Zeotap CDP All Destinations catalogue with the Search for a Destination box highlighted above a grid of destination tiles Click the **Personyze** tile. A panel describing the destination appears on the left, and the fields required to establish the integration appear on the right. Enter: * **Destination Name** — a name that identifies this destination later, when you link an audience to it. * **Private API Key** — the key you obtained from your Personyze account above. Review the values and click **Next**. Zeotap CDP Enter Destination Details screen for Personyze, showing a Destination Name field and a Private API Key field with placeholder entries, a Destination Details and Mapping progress indicator, and a Next button Under **Choose your Action**, select **Send Attributes to Personyze**. This auto-populates Internal ID, Email, First Name, Last Name, Phone and Industry under **Map the Fields**. You can edit or remove any field from the mapping except the mandatory ones, which are marked with an asterisk. Zeotap CDP Mapping screen with Send Attributes to Personyze selected under Choose your Action, and a Map the Fields table pairing Catalogue fields such as Contact Id and First Name with destination fields including Internal ID and Email, both marked as required For the rules that govern actions and mappings across every destination, see [Define the mapping](/articles/integrate-customer/destinations#define-the-mapping). Click **Create Destination**. The destination is then listed in the **Audiences** application, ready to be linked to an audience. ## Create a matching visitor attribute in Personyze Before you link an audience to the Personyze destination, create a visitor attribute in Personyze whose name is the audience name. Personyze matches on this attribute, so the names have to agree exactly. Log into Personyze. In the left navigation panel, under **Settings**, click **Visitor Attributes**. Under **User cross-session attributes**, click **+ Add new attribute**. Personyze Visitor Attributes screen showing the User session-limited attributes and User cross-session attributes rows, with Add new attribute opened to a small form containing Inner name, Display name and Data type fields above a table of existing attributes In the pop-up window, enter the **Display name** of the attribute. It must match the name of the audience created in Zeotap CDP exactly — if the audience is named `GCS Test Audience`, the Display name must also be `GCS Test Audience`. For **Inner name**, give the same name in lower case, with spaces replaced by underscores — for example, `gcs_test_audience`. Click **Add**. ## Link an audience to the destination With the destination created and the Personyze attribute in place, link the audience to the destination in the **Audiences** application. The steps are the same for every batch destination — see [Activate in Audiences](/articles/integrate-customer/link-an-audience-to-the-destination#activate-in-audiences), which also covers the refresh frequency and the output identifier mapping. Saving the destination on the audience moves it to **In Progress** while the IDs upload, and to **Success** once the upload completes. The terms *Audiences* and *Segments* are used interchangeably to refer to customer cohorts belonging to a specific category — for example, customers over 18 years of age who performed an `addToCart` event in the last 30 days. ## Add the targeting rule in Personyze After you link an audience to the Personyze destination, add a targeting rule in Personyze for the user profiles that qualified for the audience to be pushed to Personyze. Log into Personyze and navigate to **Campaigns → Targeting and Personalisation**. Click **Add** beside **User CRM/ABM/Profile data**. Personyze Visitor Targeting screen inside a campaign, listing the rule categories Pages Visited, Countries/Cities, User CRM/ABM/Profile data and Device and System, with User CRM/ABM/Profile data and its Add control highlighted In the pop-up window, set the condition: `Visitor matches if <= equal> ` Choose the attribute you created from the drop-down list, then click **Add**. Personyze User CRM/ABM/Profile data rule row reading Visitor matches if Include, Any of, a named user attribute, equal, true, with Cancel and Add buttons ## Verify the audience reached Personyze Check both sides after the first refresh has run. 1. **In Zeotap CDP** — open the audience–destination pair in the **Audiences** application and confirm the status has moved past **In Progress** to **Success**, with a non-zero qualified count. For what the statuses mean across destinations, see [Verify the activation worked](/articles/integrate-customer/destinations#verify-the-activation-worked). 2. **In Personyze** — go to **Settings → Visitor Attributes** and confirm the attribute you created for this audience is listed under **User cross-session attributes**. Then open the campaign and confirm the targeting rule resolves to that attribute. The two sides will not agree exactly. Personyze can only connect an uploaded profile to a visitor when the identifier it was uploaded with is also observable on your site, so a share of delivered profiles never matches a live visitor. ## Troubleshoot the Personyze destination Work through these before raising a ticket. * **The audience does not appear as an attribute in Personyze.** The attribute is not created by the delivery — you create it yourself, before linking. Confirm it exists under **User cross-session attributes**, that its **Display name** matches the Zeotap CDP audience name character for character, and that its **Inner name** is the same string in lower case with underscores instead of spaces. * **The destination fails to authenticate.** The Private API Key on the destination is the credential for every call. If the key has been revoked or regenerated in **Settings → Integrations**, the destination still holds the old value — edit the destination and paste the current key. * **A mandatory field is empty.** The mapping marks some destination fields as required. If a Catalogue field mapped to one of them is null for part of the audience, those records are the ones to look at first. * **The pair stays In Progress, or the run reports an error.** These are destination-level failures rather than Personyze-specific ones. See [Why deliveries fail](/articles/integrate-customer/destinations#why-deliveries-fail) for the errors that surface on an audience–destination pair and what each one means. * **The campaign does not fire for visitors you expect.** Personyze's own guidance on the Visitor Attributes screen is that imported customer data has to carry an identifier key — such as email or a CRM ID — that is also present on your site, as a site cookie, URL parameter, JavaScript variable or page element. Without that, Personyze cannot connect an uploaded profile to the visitor in front of it. Confirm the identifier you mapped in the destination is one Personyze can observe on site. If none of the above applies, see [When to contact support](/articles/integrate-customer/destinations#when-to-contact-support) for what to include in the request. ## FAQ They are two integrations for the same vendor, distinguished by where you activate from. **Personyze** — this page — is a batch destination attached to an audience in the **Audiences** application. **[Personyze Real Time Integration](/articles/integrate-customer/personyze-real-time-integration)** is a real-time destination attached to a **Send to Destinations** node in a journey, and it sends events and user profiles rather than an audience. Both send data out of Zeotap CDP to Personyze. Personyze has no knowledge of the Zeotap CDP audience as an object — it only sees a visitor attribute. The audience name is what arrives, so the attribute has to be waiting under that exact name for the value to land on it. That is also why the attribute is created before the audience is linked, not after. No. Neither delta upload nor delete is supported on this integration, and neither is ID extension. See [Delta upload and delete functions](/articles/segment-customer/delta-upload-and-delete-functions) for the destinations where they are available. Yes. The destination stores the Personyze account credential and the mapping, so it can be linked to as many audiences as you need. Each audience needs its own matching visitor attribute in Personyze, and its own targeting rule in the campaign that uses it. ## Next steps * [Set up the real-time Personyze destination →](/articles/integrate-customer/personyze-real-time-integration) * [Link the audience to the destination →](/articles/integrate-customer/link-an-audience-to-the-destination#activate-in-audiences) * [Review how destinations, actions and mappings fit together →](/articles/integrate-customer/destinations) * [Build the audience that feeds this destination →](/articles/segment-customer/create-an-audience) * [Check what influences upload time to destinations →](/articles/segment-customer/factors-influencing-the-data-upload-time-to-destinations) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.