Personyze Zapier integrationAutomate Personyze with Zapier.
The Personyze Zapier integration offers 1 trigger, 8 actions and 3 searches to move visitor profiles out of Personyze and feed it audiences, products and offline activity. It runs on the free plan, Zapier lists it as beta, and here is what it costs and what breaks.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
What the Personyze Zapier integration actually does
Personyze adapts what each visitor sees on your site and in your emails, based on how they behave and which audience they belong to. Zapier connects it to your other tools without code. You build a Zap, an automation that starts on an event and runs steps after it, every time. Personyze brings 12 visible operations to that.
Three results come up first. Known visitors handed to sales: Visitor Created or Updated passes each identified profile to your CRM or a sheet, so a rep sees who came back. Store purchases that count online: Record Product or Article Interaction logs a purchase made in a shop or by phone, so recommendations stop suggesting what the customer already owns. Audiences filled from your data: Find Audience with its create option, then Add Visitor to Audience, drops people into a segment named by your CRM, and the campaigns aimed at it start matching them.
What Zapier does not do for Personyze: it has only one trigger, and that trigger is checked on a timer (on the free plan, every 15 minutes), so nothing here reacts the second a visitor clicks. It does not reach visitors who stayed anonymous unless you change a setting, and it ignores everything that happened before your Zap was switched on. One action also deletes for good, which deserves a careful read below.
Before you commit, the Zapier review and the Make vs Zapier comparison help you check the platform itself.
Zapier vocabulary in one minute
Eight words come back on every line of this page. Here they are in plain English, once.
- Zap
- Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it and starts by itself.
- Action
- What the Zap does after it starts: the step that creates, updates or deletes something in an app for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those only.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, with no wait.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and quietly stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps after it can use what it found.
- Connection
- Your Personyze account linked to Zapier once, then reused by every Personyze step in every Zap you build.
What a Personyze Zap really costs
Personyze is not a premium app on Zapier, so it works on the free plan. The bill is counted in tasks, and only completed actions count.
- Triggernever counted
- Successful action1 task each
- Failed actionnot counted
- Free plan100 tasks a month, two-step Zaps only
- Personyzenot premium, works on the free plan
The trigger never costs a task, and neither do Zapier's checks of Visitor Created or Updated, however often they run. Each successful action counts once, so a three-action Zap uses three times more than a one-action Zap. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger and one action. Add a filter, a search step or a second action and it becomes a multi-step Zap, which needs a paid plan. The real cost driver here is volume: switch off Only Identified Visitors and every profile change on a busy site runs the Zap.
Connect Personyze to Zapier in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. You need a Personyze account first, plus access to any part of it you do not own and want the Zap to touch.
- 02
Pick Personyze
Search Personyze by name in the dialog, select it, then click Add connection. A tab opens on the Personyze side so you sign in with the account the Zap should act as.
- 03
Grant access
Sign in to Personyze in that tab and allow Zapier to use the account. The connection then appears in your list, and every Personyze step can pick it without asking again.
Your first Personyze Zap: returning visitors into your CRM
GoalEvery identified visitor whose Personyze profile changes is created or updated in the CRM, but only when the profile carries an email.
- 01
Build: pick the starting event
Create a Zap, choose Personyze as the trigger app and
Visitor Created or Updatedas the event, then your connection. Leave Only Identified Visitors on to skip anonymous browsers. - 02
Test the trigger
Run the test. Zapier brings back the three most recent profiles of your account, so the next steps are mapped on a real visitor rather than an empty sample.
- 03
Add a filter
Add a Filter step: pick the email field and a rule that it exists. Profiles known only by a CRM ID stop there. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the CRM action
Add your CRM's create-or-update contact action and map the email and the other profile values the trigger brought back into the matching fields.
- 05
Test, then publish
Test each step and check the contact in your CRM. When it looks right, publish the Zap to switch it on. From then on, each check that finds a changed profile runs it.
Personyze trigger on Zapier
1 event starts a Zap when something happens in Personyze. Zapier checks for them at the interval your plan allows.
Visitor Created or Updated
Polling triggerIn Zapier“Triggers when a visitor profile is created, or when any of its fields change.”
Starts your Zap when a visitor profile appears in Personyze or when one of its fields changes. It is the only way for Zapier to hear from Personyze, so every outgoing flow begins here.
Personyze actions on Zapier
Personyze gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
API Request (Advanced)
ActionIn Zapier“Performs an authorized call against any Personyze REST endpoint. For things the other steps do not cover.”
A free-form step for anything the other seven actions do not cover: you name the method and the path inside Personyze, and Zapier sends the authorized call for you.
Add Visitor to Audience
ActionIn Zapier“Adds an existing visitor to one of your audiences, so campaigns targeting that audience start matching them.”
Drops a visitor Personyze already knows into an audience of your choice. From then on, every campaign built for that audience can reach them.
Create Audience
ActionIn Zapier“Creates a new audience. Audience names are not unique, so prefer "Find Audience" with create-if-missing unless you really want a new one every time.”
Makes a brand-new audience in Personyze from a name you supply.
Create or Update User
ActionIn Zapier“Creates a new user or updates an existing user in Personyze. A user whose email or Facebook ID already exists is merged rather than duplicated.”
Keeps one clean record per person in Personyze: new people are added, known ones are refreshed. When the email or Facebook ID is already on file, the two records become one.
Record Product or Article Interaction
ActionIn Zapier“Records that a visitor viewed, liked, carted or purchased something — so offline and back-office activity counts toward recommendations and targeting, not just what happens on your site.”
Logs that a visitor viewed, liked, carted or bought an item, so activity outside the site, in a shop or a back office, feeds recommendations and targeting too.
Create or Update Product
ActionIn Zapier“Adds a product to your Personyze catalog, or updates the one with this ID. Fields you leave blank keep their stored values.”
Keeps your Personyze catalog in step with your shop: a new ID adds a product, a known ID refreshes it, and any field you skip keeps what was already stored.
Delete Visitor
ActionIn Zapier“Permanently deletes a visitor profile, matched by email or visitor ID. There is no way back.”
Erases a visitor profile for good, found by email or visitor ID, together with its tracked history.
Update Visitor
ActionIn Zapier“Updates the fields of an existing visitor, matched by email or visitor ID. Does not create one.”
Writes new values onto a profile Personyze already holds, which you point to with an email or a visitor ID.
Personyze searches on Zapier
3 search steps look for data that already exists in Personyze, so a later step can use it.
A search step finds something already in Personyze and hands it to the next steps. Searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not the one you expected.
Find Audience
SearchFind or createIn Zapier“Finds one of your audiences by name. Pair it with a create step to make the audience when it does not exist yet.”
Looks up one of your audiences by name, matched exactly but ignoring capitals and surrounding spaces. Find or Create Audience is this same search with creation ticked.
Find Events
SearchIn Zapier“Finds tracked events — the custom events and goals your site reported to Personyze.”
Fetches the custom events and goals your site has reported to Personyze, so a later step can act on them.
Find Visitor
SearchIn Zapier“Finds a visitor profile by email or visitor ID.”
Finds a visitor profile from an email or a Personyze visitor ID, the step to place before Update Visitor or Add Visitor to Audience.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there. Switched on, the Zap carries on without the value.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create: it asks for the fields needed to create the missing item instead.
- If multiple search results are found?Keep the first match (the default), stop the Zap, or hand every match to the next steps at once.
When a Personyze Zap breaks
Zapier lists no help article and no rate limit specific to Personyze. The failures you will meet are the general ones, and each has a plain cause.
Most problems come from volume and loops rather than from Personyze itself. For the general method, the Zapier troubleshooting page walks through the diagnosis.
No catching up on the past
A Zap only reacts to what happens after you switch it on. Visitors, purchases or audiences that existed before are never picked up; moving them is a separate job.The Zap that feeds itself
Visitor Created or Updated followed by Update Visitor on the same profile changes a field, which the next check sees as a new change, and the task count drains fast.Bulk imports held back
After a migration or a mass import into Personyze, the trigger can suddenly return a huge batch. Zapier's flood protection may hold it back instead of running it all.Same profile, only once per change
Zapier remembers what it has already seen on a polling trigger, so the same visitor update does not start the Zap twice on a later check.
Need help automating Personyze with Zapier?
A person reads every message.
