WordPress Plugin — Connect, Feed and Personalize a WordPress Site

The Personyze System Integration plugin is the bridge between a WordPress site and a Personyze
account. It does four things:

1. Installs the tracker on every page, with no theme edits.
2. Feeds the catalog — posts, pages and WooCommerce products — so recommendations, the
   AI chat agent and AI search have something to work with.
3. Reports what the visitor is reading, by post ID rather than by URL.
4. Hosts the Personyze AI agent inside wp-admin, so campaigns can be built without leaving
   WordPress.

Campaigns, recommendations, A/B tests and designs are still built in Personyze. The plugin connects the two and puts
the agent where the content is.

Requires WordPress 5.6 or later and PHP 7.0 or later. Tested to WordPress 7.0.3.
Get it from the
WordPress plugin directory.

Connecting, in one click

The plugin comes first now. There is no account number to copy, no tracking code to paste, no API
key, and no application password to create by hand.

1. Plugins → Add Plugins, search for Personyze, install and activate.
2. Personyze → Settings, then Connect to Personyze.
3. Approve on the WordPress screen, then confirm the account on the Personyze screen.

WordPress issues the application password itself during approval and hands it to Personyze. You need to be signed in
to Personyze for the confirmation step.

What happens underneath

Worth knowing if you are reviewing the integration:

• The plugin sends you to WordPress’s own authorize-application.php with a stable app id and a
  one-time state, stored for thirty minutes and checked when Personyze posts the account back — so
  a third party cannot bind your site to an account of their own.
• WordPress redirects to Personyze with the site URL, user login and the new password in the query string.
  Personyze immediately moves those into a short-lived HttpOnly cookie and redirects to a clean URL, so
  the password does not stay in the address bar or in browser history.
• The connection is never made on that redirect alone. Personyze shows what is about to be connected
  — the site, the WordPress user, the Personyze account — and waits for a confirmation click.

Manual setup, still supported

Unchanged: create an application password under Users → Profile, then enter the site URL,
username and password in Personyze under Settings → Integrations → WordPress.

Where the plugin lives

A top-level “Personyze” menu in the WordPress admin sidebar, with two screens. Both
require the manage_options capability, so administrators only.

The AI agent inside WordPress

The same agent as in the Personyze panel, on the same account — not a cut-down version. It appears in three
places:

• Personyze → AI Agent — a full-width screen.
• A launcher in the bottom-right corner of every wp-admin screen.
• A launcher on your own site’s front end, while you are signed in as an administrator —
  also reachable from the WordPress toolbar as Personyze AI.

The AI actions meter

Under the prompt box, mirroring the panel. It counts AI actions — never tokens, never
dollars — and has five states:

• Normal: “42 AI actions left this month · renews Sep 1”.
• Under a quarter remaining: amber.
• Out on a paid plan: “Monthly AI allowance used — further AI is added to your invoice.”
• Out on a free plan: red, with an Add AI credits link.
• No allowance configured: the meter hides itself entirely.

How it behaves

• The conversation is built when you first open it, not on page load — it may be sitting on a visitor-facing
  page, and most page views never open it.
• Open or closed is remembered. Esc closes it; Enter sends and
  Shift+Enter makes a new line.
• Multi-step answers show what is being consulted while they work, rather than a blank wait.
• It is never visible to visitors. It renders only for signed-in users with
  manage_options.

What it can and cannot do

It can build a campaign from a description and style it to your brand, compile targeting from plain
words and read it back to you, suggest what to improve from your own traffic, answer performance questions from real
numbers, manage existing campaigns, and open a support ticket. New campaigns are created in staging,
shown only to visitors arriving from a staging IP — publishing stays your own act.

The feeds

Both are on by default, and the product feed appears only where WooCommerce is active. They are
controlled from Personyze → Settings → Feeds in WordPress, not from the Personyze
panel — whatever WordPress says wins, and Personyze adopts it.

They are re-read once a day, each account in its own hour, so posts you publish or edit reach
recommendations without anyone pressing anything. Flipping a switch tells Personyze immediately rather than waiting for
the next pass; if Personyze cannot be reached at that moment the setting is still saved, picked up on the next run, and
the screen says so.

What each feed carries

Content — published posts and pages, excluding password-protected ones:

id (the WordPress post ID) · title · description (the excerpt)
· publish_date (last modified, GMT) · name (slug) · author
· type · comment_count · categories ·
interests (tags) · content_url (the permalink) · thumbnail (the
featured image)

Products — published products, with the same fields plus price (regular) ·
sale_price · is_in_stock · inventory (stock count).

Looking at what Personyze reads

The settings screen shows the two Feed URLs. Opening one is the fastest way to answer “is it
picking up my posts?”, and you can point another system at the same catalog.

https://SITE/?rest_route=/personyze/v1/sitemap     content
https://SITE/?rest_route=/personyze/v1/products    products

Add &limit=20 to look at the first few rows. They page with id-from and
limit, 100 rows at a time.

Knowing what the visitor is reading

This is the part most personalization tools make you configure, and here there is nothing to configure. On a single
post, page or product the plugin tells Personyze the WordPress post ID directly:

personyze.push(['Article Viewed', 123]);   // or ['Product Viewed', 55]

The feed exports that same id, so the catalog key and the view event match exactly. No
page groups, no URL patterns, and no container scraping the address bar.

It is deliberately silent everywhere else: category and tag archives, the posts index, search results, and post types
neither feed exports. Turning a feed off also stops its view reporting.

WooCommerce

• Product sync — on by default wherever WooCommerce is active.
• Add-to-cart tracking — cart changes are reported as Product Added to cart with the
  quantity, and Products Removed from cart on a clear.
• Purchase tracking — on the order-received page, each line becomes Product Purchased
  with its quantity.
• Add to cart from a Personyze campaign — a recommendation widget or popup can add a product to
  the real WooCommerce cart, through an endpoint the plugin exposes for it.

Unlike the two feeds, add-to-cart and purchase tracking are switched in the Personyze panel.

Your own templates, through shortcodes

Personyze can ask your site to render a WordPress shortcode and use the result inside a campaign. Personalized blocks
can therefore use your own templates and page-builder output and match the theme exactly, instead of being rebuilt in
Personyze.

It is also how the connection tests itself: after connecting, Personyze sends a token through the shortcode route and
checks it comes back — so “connected” means the whole path works, not merely that credentials were
stored.

Changing accounts, and disconnecting

Personyze → Settings → “Connect to a different account, or disconnect”.
Disconnecting:

• Revokes the application password Personyze was using, so the old account can no longer read the
  site. Only passwords this plugin created are touched — another integration’s are left alone.
• Stops the Personyze tag being served.
• Clears the stored account, feeds and key.
• Leaves everything built in Personyze untouched. It unlinks the two, nothing more.

When something looks broken

• The agent shows a link out instead of the chat. A site connected before 0.27 has no API key until
  Personyze’s next configure run. Clicking Test in the panel’s WordPress widget fixes it
  immediately.
• A new post is not in recommendations yet. Feeds are re-read daily, not instantly — normally
  live within 24 hours. Sync sitemap in the panel forces it now.
• The agent launcher does nothing. A full-page cache that caches pages for signed-in administrators
  leaves the security nonce embedded in the page stale. Most caches bypass signed-in users and are unaffected.
• The one-click button is missing. The site is on HTTP; use the manual steps.
• No product feed or switch. WooCommerce is not active.

Reference

REST routes, under personyze/v1

/config and /content additionally require the caller to resolve to
personyze.com, because they change settings and execute shortcodes. The read-only feeds are gated on the
capability alone, which is what makes their URLs usable by you and by other systems.

Options stored in WordPress

personyze_account_id · personyze_tracking_domains ·
personyze_api_key · personyze_sync_articles ·
personyze_sync_products · personyze_track_add_to_cart ·
personyze_track_purchase

Staging

The personyze_connect_url filter overrides where the one-click connection sends its credentials, for
non-production environments.

What you can build on a WordPress site

Everything Personyze can put on a page works here, using the catalog the plugin feeds it. Four of the most
common:

Edit the page you already have

A popup or banner from a template

Recommendations from your own posts

Or build the design yourself

The Canvas Builder assembles a popup, banner or inline block from
elements — headline, image, countdown, form, recommendation strip — when no template is close enough.

Related

• Start here — the other ways to install Personyze.
• Product / content feeds — what
  Personyze does with what the plugin sends.
• AI chat agent and AI search — they answer from these
  feeds with no separate indexing step.
• Personyze AI agent — the same agent, in the panel and from Claude or
  ChatGPT.