Personyze Wiki Personyze Wiki docs
Open Personyze
Docs/ Analytics & Reporting/ Conversion Tracking — Define Goals That Count
Analytics & Reporting

Conversion Tracking — Define Goals That Count

Conversion tracking is where you define the events that count as success — a purchase, a sign-up, a button click, a page visit, a form submission. In Personyze…

3 min read Updated 18 hours ago

Conversion tracking is where you define the events that count as success — a purchase, a sign-up, a button click, a page visit, a form submission. In Personyze these are called goals. Define a goal once and every campaign, action and audience can reuse it for performance reporting, so your numbers stay consistent everywhere.

Where it lives

Open Settings → Conversion Tracking in the left menu. You’ll see every goal on the account, its type, when it was created, its de-duplication limit, recent event count, and whether it’s active. Use the search box and the Type / Status filters to find one quickly.

Create a goal

Click + Add new goal, give it a clear name (for example Checkout Success), then choose what should trigger it. Personyze offers six trigger types:

New goal dialog listing the six conversion trigger types
The New goal drawer. Pick how Personyze should detect the conversion. Click to enlarge.
  • Click or page interaction — fire when a visitor clicks, hovers, or interacts with an element: buttons, links, images. Point it at an element with the visual picker or a CSS selector.
  • Page URL visited — fire when the visitor lands on a URL that matches a pattern. Ideal for thank-you pages and confirmation screens (for example any URL containing /order-complete).
  • Extract data from the page — pull a value from the page, a cookie, browser storage, or a JavaScript variable. Use this to capture the order total, SKU, or plan name so the goal carries a monetary value, not just a count.
  • Import from Google Analytics — reuse goals and events you already track in GA4 or Universal Analytics instead of re-defining them.
  • Import from Google Tag Manager — pull existing tags and dataLayer events configured in GTM.
  • Custom JavaScript trigger — fire the goal from your own code. Useful for server-side events, mobile-app hooks, or checkout callbacks.

Configure the trigger

After picking a trigger type, configure how Personyze detects it. For a click goal, choose Pick it visually (opens the QA simulator so you can click the element on your live page) or Paste CSS selector, then set the event (click, hover, or form submit), an optional text filter, and how often it may fire per visitor.

Click-interaction goal configuration drawer
Configuring a click goal: find the element visually or by selector, choose the event, filter by text, and set frequency. Click to enlarge.

Goal value and de-duplication

A goal can carry a value — a fixed amount, or a number extracted from the page (the order total). Personyze then reports attributed revenue alongside the raw conversion count, so you can see the money a campaign influenced, not just the clicks.

The limit controls de-duplication: count a goal once per visitor, once per session, or every time it fires. Set purchases to count every time; set a sign-up to count once per visitor so a returning user doesn’t inflate the number.

Where goals show up

  • Campaign performance — every campaign’s Performance tab reports impressions, clicks, and the goals it drove, with attributed revenue.
  • Audiences & targeting — you can target visitors by whether they’ve completed a goal (or not), which is how “returning buyers” or “abandoned checkout” audiences are built.
  • Account overview & analytics — site-wide conversion totals and trends.

Tips

  • Define the purchase goal with an extracted order-total value first — most reporting depends on it.
  • Give goals names your whole team recognizes; they appear in every report and audience rule.
  • If you already track conversions in GA4 or GTM, import them rather than rebuilding — the numbers will match your existing analytics.
  • Test a new goal with the tracker’s staging/QA mode before relying on it in live reports.

Goals feed the performance numbers you’ll see throughout Personyze. For where and how personalized content is shown, see Where Content Shows, and for the data you can collect about each visitor, see the Visitor Attributes guide.

Did this page answer your question?
Thank you — that goes to whoever maintains this page.