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 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 — 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.
The Private API Key is the encryption key that authenticates API calls in Personyze. Obtain it before you create the destination in Zeotap CDP.
1
Log into the Personyze console and navigate to Settings → Integrations.
The Personyze console with Settings expanded in the left navigation and Integrations selected
2
On the Integrations screen, click Get keys on the Full-featured API tile.
The Personyze Integrations screen, with Get keys clicked on the Full-featured API tile
3
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.
Log into the Zeotap CDP App and go to the DESTINATIONS application.
2
Click + Create Destination.
The Zeotap CDP Destinations listing, with Create Destination highlighted
3
Under All Destinations, search for Personyze.
The All Destinations catalogue, with the search box highlighted
4
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.
The Enter Destination Details step for Personyze, with the Destination Name and Private API Key fields
5
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.
The Mapping step, with Send Attributes to Personyze chosen and Catalogue fields mapped to Personyze destination fields
For the rules that govern actions and mappings across every destination, see Define the mapping.
6
Click Create Destination. The destination is then listed in the Audiences application, ready to be linked to an audience.
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.
1
Log into Personyze.
2
In the left navigation panel, under Settings, click Visitor Attributes.
3
Under User cross-session attributes, click + Add new attribute.
The Personyze Visitor Attributes screen, with Add new attribute opened on the User cross-session attributes row
4
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.
5
For Inner name, give the same name in lower case, with spaces replaced by underscores — for example, gcs_test_audience.
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, 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.
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.
1
Log into Personyze and navigate to Campaigns → Targeting and Personalisation.
2
Click Add beside User CRM/ABM/Profile data.
The Visitor Targeting screen, with the User CRM/ABM/Profile data rule category highlighted
3
In the pop-up window, set the condition:Visitor matches if <Include> <Any of> <Display name of the attribute> <= equal> <true>
4
Choose the attribute you created from the drop-down list, then click Add.
The completed User CRM/ABM/Profile data condition, matching the visitor attribute against true
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.
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.
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 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 for what to include in the request.
Why are there two Personyze entries in the destination catalogue?
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 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.
Why does the Personyze attribute name have to match the audience name?
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.
Does this destination support delta upload or delete?
No. Neither delta upload nor delete is supported on this integration, and neither is ID extension. See Delta upload and delete functions for the destinations where they are available.
Can one Personyze destination serve several audiences?
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.
.png?fit=max&auto=format&n=OFEzw22E9lo2DHYT&q=85&s=816d7f247d590bc7bb09fff1e0b92a3d)
.png?fit=max&auto=format&n=OFEzw22E9lo2DHYT&q=85&s=9cca1024dea8e775f5b0ad6aa1d68a75)
