Email Get Code statistics

Measure every Get Code widget pasted into your third-party email tool — Mailchimp, Klaviyo, SendGrid, HubSpot, whatever you use. Personyze doesn’t send the email, so measurement starts at Viewed (when the widget renders inside the open). Start with an all-campaigns roll-up or drill into a specific campaign’s variants. Read docs

1 Statistics for

Get Code funnel

Metrics

Funnel dynamics · by day · Viewed → Clicked → Cart → Purchased

Revenue attribution · Get Code, by day

Filters

Email Get Code statistics — docs

What Get Code means, how the all-campaigns roll-up and single-campaign scope work, and what each funnel step counts.

1What is an Email Get Code campaign?

For Email Get Code campaigns, Personyze generates a block of embedded HTML (with a tracked iframe or pixel) that you paste into an email built and sent by your own ESP — Mailchimp, Klaviyo, HubSpot, SendGrid, and so on. Personyze never sends the email itself, so there is no Sent step, no bounces, no unsubscribes. Counting starts the moment the recipient's email client renders the widget.

Why it matters for this page. This dashboard rolls up every Get Code campaign on the site. All numbers here are "after the ESP" — we only see recipients whose email client actually loaded the Personyze widget.

2Two-level scope picker

The top card has two steps. Step 1 switches between All Get Code campaigns (site-wide roll-up) and a single campaign. Picking a campaign reveals Step 2, where you choose either the whole campaign or a specific action variant inside it (e.g. Desktop inbox vs. Mobile inbox, or a specific fallback branch).

Why two levels? A single Get Code campaign often renders multiple action variants — a desktop widget, a mobile widget, a plain-text fallback. Each variant has its own render and conversion rates. The two-level picker keeps you from accidentally averaging variants together.

3Funnel steps (what each metric counts)

Viewed — unique widget renders (pixel-tracked in the email client). This is the first measurable event. Shown as an absolute count, not a percentage.
Clicked — users who clicked a product or CTA inside the Get Code widget and landed on the site. % of Viewed.
Added to cart — users who added a product in the same session as their Get Code click. % of Clicked.
Purchased — users who completed a transaction. % of Added to cart.

Cart + Purchased now show in every scope, including "All Get Code campaigns". At the roll-up level they're a best-effort, last-click estimate — a single cart or transaction can't always be cleanly attributed to one Get Code sender across the whole site — so treat the all-campaigns commerce numbers as directional.

4Attribution strip (Transactions · Totaling · Contribution)

The always-visible strip under the scope picker shows attributed commerce for the current scope: last-click, 7-day window. Transactions is the order count, Totaling is revenue, and Contribution is Get Code revenue as a share of all-channel revenue (all-campaigns scope) or this campaign's share of all Get Code revenue (single-campaign scope). Numbers update live when you change scope.

5Clicking "Users >" on any card

Every KPI card has a clickable "Users ... >" link underneath the headline. Clicking it opens the drill-down drawer with the exact users who qualified for that step. The drawer shows every Personyze user attribute as a column — you can toggle columns, add filters (e.g. Country = Greece), export the list to CSV, or call the same query over API.

6Filters, columns, and API

Filters — stackable. Each filter is Column + Operator + Value. Applies to the current metric's user list.
Show columns — checkbox panel. Your picks persist per user, not per metric.
Export — CSV of the currently filtered rows, respecting column visibility.
Import — upload a CSV to update user attributes for the users in the list.
Use API — deep-link to API docs with the current filter as a ready-to-paste query.

7Row actions

The sticky "User list" column shows inline action chips for each user:

View Profile — full-session timeline for this user.
User lists — segments they belong to.
Interests — categorical affinities from the Behavioral Targeting engine.
Product Interactions / Article Interactions — their pairs history.
Delete user — wipes the user record (GDPR-style).

8Timeline chart

Below the KPI grid, a line chart shows the daily volumes of the four funnel metrics (Viewed / Clicked / Added-to-cart / Purchased). Click any legend item to hide a series. Prior period shows as a dashed line if Compare-to is active.