CRM / User-List Targeting

CRM / User-List Targeting personalizes your site for people you already know — the contacts in your CRM, the accounts on your ABM list, or any user list you import. Personyze matches the visitor in front of you to their imported record, then lets you target on any field that record carries: account tier, industry, role, plan, renewal date, lifetime value — anything you can put in a spreadsheet column.

In the panel this campaign type lives under New campaign › Web Browser › CRM / User-List Targeting.

Before you start

This campaign type needs a user list to target against. If you have not connected one yet, the campaign picker says “No CRM or user list connected yet” and offers a Connect a list shortcut — that takes you into the same import flow described in step 2 below.

You also need at least one identity key set up, so Personyze can tell that the anonymous visitor on the page is a particular person from your list. That is step 1.

The steps

The campaign has six steps: Keys, User Data, Target, Content, QA and Performance.

The first two are account-wide settings, not campaign settings. They are the same screens as Settings › Visitor attributes, embedded into the campaign so you can set them up without leaving the wizard. Editing them here and editing them there is the same edit, and it affects every campaign on the account.

1. Keys — how a visitor is matched to a record

A key is what ties an imported profile to a real person browsing your site. Without one, Personyze has no way to know that this visitor is the user from your CRM.

The identifier types are fixed: email and CRM ID. What you configure on this step is where on the page Personyze reads each one from — a URL parameter, a cookie, a form field, a JavaScript variable, or a value in your data layer.

Typical setups:

Email — read from the login or newsletter form field, or from a URL parameter in the links you send from your ESP.
CRM ID — read from a URL parameter after sign-in, from a cookie your application sets, or from a JavaScript variable on the page.

You can set up both. A user can be recognised by either, and the moment Personyze sees a key in the place it has been told to look, it matches the visitor to their record and applies your targeting on the spot.

Because keys are identity, they also drive cross-device recognition: a person identified by the same email on their laptop and their phone is one profile, not two.

An individual user profile. The identity keys at the top are what a successful match produces — everything below them becomes available for targeting. Click to enlarge.

2. User Data — importing your list

This step is where your CRM data actually arrives. Each list can come from one of four sources, and each refreshes on its own schedule:

File upload — a one-off spreadsheet or CSV.
URL / RSS-Atom feed — a feed Personyze re-reads on a schedule.
SFTP — a drop folder your system writes to.
API push — your application pushes JSON to Personyze.

Use an upload for a fixed list you will not change often, and a feed, SFTP drop or API push for data that moves — plan changes, renewal dates, account tiers.

The Imported user lists section showing each list with its source, user count, last refresh, and status — The Imported user lists section: every list with its source, how many users it holds, when it last refreshed, and whether it is healthy. Click to enlarge.

Inside the campaign, New list is the way in. It opens a four-step import wizard.

Step 1 — choose the list. Assign the incoming users to a list, or skip and let Personyze match them into existing profiles automatically.

Step 1: pick the list these users belong to. Click to enlarge.

Step 2 — choose the source. This is where you pick file upload, URL feed, SFTP or API push.

Step 2 of the import wizard with the four upload sources annotated: file upload, URL feed, SFTP push, and JSON API push — Step 2: the four sources. The choice here decides whether the list is a one-off snapshot or stays in sync. Click to enlarge.

Step 3 — map your columns. Tell Personyze which column is the email, which is the CRM ID, and which of the remaining columns map to which profile fields. Anything you map here becomes targetable in step 3 of the campaign.

Step 3 of the import wizard with the column-to-field mapping dropdowns annotated — Step 3: column-to-field mapping. Map at least one identity key, or the rows cannot be matched to visitors. Click to enlarge.

Step 4 — review and import. Check the mapping, then start the import.

Step 4 of the import wizard: review the mapping before starting the import — Step 4: the last look before the import runs. Click to enlarge.

If the field you need does not exist yet, you can create it — see Adding Custom User Profile Data Fields.

3. Target — building the audience

Now you narrow the audience. CRM fields appear as a User / CRM / ABM data rule group, and you can combine them freely with Personyze’s behavioural and contextual rules — so “enterprise accounts” can become “enterprise accounts, on the pricing page, second visit this week”.

The Target step. Each group narrows the audience further. Click to enlarge.

Click Add targeting rule and choose User / CRM / ABM data to target on an imported field.

The rule picker. User / CRM / ABM data covers every field you mapped during import. Click to enlarge.

A finished CRM rule. Rules combine with and / or logic, so you can express account tier and behaviour together. Click to enlarge.

4. Content — what these people see

Choose what to show the audience you just defined. Any Personyze content type works here: recommendation widgets, banners, popups, in-place edits with the Live Editor, or custom JavaScript.

Imported fields are also available inside the content, not just in the targeting — so a banner can greet someone by first name, name their account manager, or count the days to their renewal.

5. QA — check it before it goes live

QA works the same as for any campaign: review the summary of your rules and content, preview the campaign, and share a preview link with colleagues. The audience forecast tells you how many known users currently match — a fast way to catch a rule that is narrower than you intended.

The QA step: campaign summary (targeting rules and action), preview options (shareable links, open in simulator), and the audience forecast panel. — The QA step. If the forecast reads zero, the usual cause is a key that is not being found, not a targeting mistake. Click to enlarge.

6. Performance — results once it is live

After the campaign is running, the Performance step shows its live results: how often it was shown, how the audience engaged, and what it contributed.

If nobody matches

Almost every “my CRM campaign is not showing” case comes down to identity, not targeting. Work through it in this order:

Is the key being read? Visit your own site, sign in, and check that the visitor is recognised. If the key never appears where Personyze was told to look, no match can happen.
Did the import actually land? Check the user count and last-refresh time on the list.
Is the field mapped? A column that was skipped during mapping is not targetable, even though it is in your file.
Only then, check the rules. Widen the audience temporarily and see whether the forecast moves.

Cross-Device Tracking — how identity keys unify a person across devices.
Adding Custom User Profile Data Fields — creating fields to import into.
User Profile Data Setup and Synchronizing — keeping imported data fresh.
REST API: users object — pushing profiles programmatically instead of importing files.