Every page in Jandex, and when to open it.

Every page is built from your own sending history. Nothing is estimated and nothing is sampled. Campaigns, flows, subscribers and orders are pulled on a schedule and stored, so you can look at trends that go back further than the platform lets you.

Treat Jandex as the place you go to decide what to send next, and your email platform as the place you go to send it.

One connected Klaviyo or Omnisend account.

Open Integrations, pick Klaviyo or Omnisend, and approve the permission screen on their side. You get sent back and the first sync starts on its own.

Connect the store you actually want to report on. If you run several stores, connect each one, then switch between them from the account selector at the top of the dashboard.

Admin access on the Klaviyo or Omnisend account you are connecting.

Day one pulls a limited slice of history, day two pulls more, and after about two days the account moves to the normal sync schedule. Campaign and flow numbers appear first. Anything based on orders takes longest because there is the most of it.

Do not judge the numbers on the first evening. Check again after two full days, when the backfill window has closed.

Nothing. This runs by itself once you connect.

Omnisend does not expose order history to apps. Orders placed through your store never reach the app through their API, so anything that needs an order timestamp cannot be built. That is why Omnisend accounts have no LTV Curve, no Cohort Retention, no Replenishment and no Churn Risk Radar. In exchange, Omnisend accounts get Customer Value and Lifecycle Trends, which Klaviyo accounts do not need because they have the real order data.

Use the provider switch at the top of this page. Anything dimmed is not available for that platform, and the article tells you why.

Nothing. Availability is set by which platform the account is connected to.

Revenue, sends and engagement for the current period, with the change against the period before it. Alerts surface here first.

Open it at the start of the week. If nothing is flagged, the account is behaving and you can go straight to whichever page you came for.

A connected account that has finished its first sync.

Recipients, open rate, click rate and attributed revenue per send. Rates are recipient weighted, so a large send and a small send are compared fairly.

Start here when someone asks how a specific campaign did.

Campaign history synced from your platform.

The same metrics laid out for direct comparison, so differences in performance are visible without scrolling.

Use it when comparing a set of related sends, like every campaign in one promotion.

At least two sent campaigns.

A rendered preview of what went out, paired with how it performed.

Use it when you are trying to work out whether the creative or the offer drove the result. Numbers alone will not tell you that.

Campaigns with creative captured during sync.

More columns, less decoration. Sortable so you can rank by whichever metric you are judging on today.

Use it for quarterly reviews, or any time you need to rank a lot of campaigns quickly.

Campaign history synced from your platform.

Each send sits on the day it went out, so gaps and clusters are obvious. It opens on the most recent month with activity.

Use it to check cadence before planning next month. Three sends in one week followed by ten quiet days is easier to see here than in any list.

Campaign history synced from your platform.

Weekly, bi-weekly and monthly views of performance with the comparison against the previous period already worked out.

Use it on report day instead of rebuilding the same summary by hand every time.

At least one full period of synced history.

Bounce, spam complaint and unsubscribe behaviour by send, with the trend line that matters more than any one campaign.

Check it before you increase sending volume, and any time open rates fall without an obvious creative reason.

Campaign history synced from your platform.

Flow level totals so you can see which automations carry the account and which are decoration.

Start here before building anything new. Most accounts have more upside in fixing a live flow than in adding another one.

Flow history synced from your platform.

Where people drop out, which message underperforms the rest, and what to change first.

Use it when you know a flow is weak but cannot tell which step is responsible.

A Klaviyo account with flow history and enough sends for the step level numbers to mean something.

Four summary cards, then one row per email with a weekly revenue sparkline. Three flags appear where earned: Engagement decaying, for three straight weeks of falling open rate on fifty or more sends. Revenue falling. Underperformer, for an open rate below sixty percent of the account median on one hundred or more sends. Automations that are switched off are dimmed and tagged OFF.

Work top down. The highest earning email with a decay flag is the most valuable thing you can fix this week.

An Omnisend account with at least a few weeks of automation history.

Every step, branch and delay in order, including the paths most people forget they built. Changes are detected automatically, so the view stays current.

Use it to audit an inherited account, or to confirm a flow is actually built the way the brief said it was.

A connected account with at least one automation.

The refresh schedule and its last run.

You rarely need this. It exists for accounts with unusual volume where the default schedule is not the right fit.

A Klaviyo account.

The tracking state for each automation on the account.

Use it to stop pulling data for retired flows so they stop appearing in reporting.

A Klaviyo account with at least one automation.

Every headline metric for both periods and the change between them.

Use it before a client call so you can answer whether this month beat last month without doing arithmetic live.

Two periods of synced history.

A grid where the strongest cells are the times your list genuinely engages. The human and machine split matters because privacy proxies open email automatically and will otherwise flatter your best hours.

Use the human side to choose a send time. Ignore the machine side for that decision.

Enough send history to fill the grid. Accounts that send once a week take longer to produce a usable pattern.

The distribution of time between delivery and click, rather than a single average.

Use it to set flow delays. If most clicks arrive within four hours, a twenty four hour delay to the next step is wasting attention.

A Klaviyo account with click history.

The conversion at each stage rather than one blended number, so you can see where new subscribers stall.

Use it to decide how long a welcome series should run and where the offer belongs.

A Klaviyo account with order history synced.

Revenue and engagement grouped by how many emails a subscriber received in a window, so the point where more sending stops helping is visible.

Use it to settle the send more or send less argument with evidence instead of instinct.

A Klaviyo account with order history and a reasonable spread of sending frequency.

A line for the share over time, with a table underneath showing email revenue, store revenue and the resulting percentage for each month.

This is the number to open a client meeting with. It answers what email is worth to the business, not just what email did.

Store revenue available to the account. Without it the share cannot be calculated.

A card per lifecycle stage with its customer count, its share of scored customers and a bar for scale, plus buyer counts and spend tiers.

Use it as the Omnisend stand in for RFM. Champions falling and At risk climbing over a few weeks is the signal to act on.

An Omnisend account. Jandex creates a small set of read only segments in your Omnisend account to measure this. They are named so they are obvious and must not be deleted.

Stages, buyers and spend as separate views, one point per day, with the underlying numbers in a table below the chart.

Use it to answer whether the base is improving. A single day tells you where you stand, this tells you which way you are moving.

An Omnisend account with a few days of measurement behind it.

A chart you can switch between customers, revenue and percent returning, with controls for the period and whether points are grouped by week or by month.

Use it to check whether growth is coming from new buyers or from the base buying again. Those two need completely different email programs.

A Klaviyo account with order history synced.

Cumulative value plotted against time, so you can see when most of a customer's lifetime value actually arrives.

Use it to justify acquisition spend and to decide how long to keep emailing a lapsing customer.

A Klaviyo account with order history synced.

Named segments such as champions, loyal and at risk, with the size of each.

Use it to pick who a campaign goes to. Sending the same email to a champion and to someone who lapsed a year ago wastes both.

A Klaviyo account with order history synced.

The retention picture in a form you can hand to a client without editing.

Use it on report day when the client cares about repeat business rather than campaign performance.

A Klaviyo account with order history synced.

A grid where each row is a starting month and each column is a month after it, showing how much of that group came back.

Use it to tell whether recent customers are better or worse than the ones you acquired a year ago. It is the cleanest read on whether the business is improving.

A Klaviyo account with at least several months of order history.

Both rates over time rather than as a snapshot.

Use it as the health check for the base. A rising churn rate is a problem long before revenue shows it.

A Klaviyo account with order history synced.

A ranked list based on how far past their normal buying gap each customer is.

Export the top of the list and give it a win back campaign. This is the most directly actionable page in the section.

A Klaviyo account with order history synced.

The typical gap between orders, which is the correct timing for a reorder reminder.

Use it to time replenishment flows to your actual data instead of a guess like thirty days.

A Klaviyo account with repeat order history.

Who improved, who slipped, and how many did each.

Use it to prove a retention program is working. Movement out of at risk is the result, revenue is the lagging effect.

A Klaviyo account with order history across several periods.

The distribution of the gap between first and second order.

Use it to set the timing of the post purchase flow. The second order is the one that decides whether a buyer becomes a customer.

A Klaviyo account with repeat order history.

Best and worst performing lines with the numbers behind each.

Use it before writing. Your own winners are a better starting point than a swipe file from another brand.

Campaign history synced from your platform.

Words that appear in your sends, with the average performance of the sends that used them.

Use it to find the language your list responds to. Treat small samples carefully, one lucky send can carry a word up the list.

Enough campaign history for word level patterns to appear.

The split between discounted and full price sends, and what each earns.

Use it to catch the slow slide into a list that will not buy without a code. Fixing that early is much easier than fixing it late.

Campaign history synced from your platform.

What was tested, what won, and by how much.

Use it so the same test does not get run twice a year apart. Klaviyo only, because Omnisend does not report variant level data to apps.

A Klaviyo account with tests that have run.

Active subscriber counts tracked over time, with growth and loss.

Check it monthly. A list that is growing in size while falling in engagement is heading for a deliverability problem.

A connected account with subscriber data synced.

People who have stopped engaging for long enough that continuing to email them costs more than it earns.

Run it before a large send. Cleaning is the cheapest deliverability improvement available.

A connected account with engagement history.

People whose spending puts them near the top of your list but whose engagement or segmentation has them grouped with everyone else.

Use it to find the VIP list you should already have had.

A connected account with customer value data.

A builder that works on real engagement, including opens filtered down to human opens only.

Use it when the segment you want cannot be expressed in Klaviyo's own segment builder.

A Klaviyo account with engagement history.

Creative Strategist for subject lines, copy and campaign ideas in your brand voice. Data Assistant for quick answers about campaigns, flows and account data. Personal Analyst for deeper analysis and recommendations.

Ask the Data Assistant before opening a page. It is usually faster than navigating for a single number.

A connected account that has finished its first sync.

Copywriting and design tools with your brand and past sends as context, including import from Figma.

Use it to take a campaign from idea to built email without leaving the account it belongs to.

A connected account.

A shareable review link. Clients comment on the work itself instead of replying to an email thread.

Use it to stop feedback arriving in four different channels.

An email or design ready to review.

The numbers that matter to them, without the working parts of the platform.

Send it instead of building a slide deck for every check in.

A connected account with synced history.

A date for each send with a brief attached, plus notes and files the team can see. Clients can comment on any planned send.

Use it as the single agreed plan so the calendar, the brief and the feedback all live together.

Nothing beyond an account to plan for.

Collected competitor email, organised so you can look for patterns rather than one off examples.

Use it for cadence and offer benchmarking, not for copying creative.

Nothing beyond an account.

A design you upload, sliced into pieces sized for email with the boundaries under your control.

Use it when the design arrived as one tall image and needs to become a real email.

A design file to slice.

Captured images of your sends, attached to the account so assistant feedback is grounded in the real creative.

Run it before asking an assistant to critique creative. Without it the assistant is working from metrics alone.

A connected account with campaigns or flow emails.

A countdown you can generate and drop into any email as an image. It renders from the current time whenever it loads, so it stays accurate.

Use the countdown for a genuine deadline. It stops working on you the moment customers learn the deadline is not real.

Nothing beyond an account.

Every connected store, its platform and its current state.

Open it from the account menu at the top right, not the sidebar. Come here to add a store, or to disconnect one. Disconnecting revokes the access Jandex was given.

Admin access on the account you are connecting.

Products ranked by revenue attributed to email.

Use it to choose what to feature. The best seller in the store is not always the best seller in the inbox.

A connected account with product level order data.

Flagged changes in sending and performance, including a live flow that has gone silent, which is the one most likely to be quietly costing money.

Check it weekly. It is designed to catch the problems nobody thought to look for.

A connected account with enough history to establish what normal looks like.

Current plan, what is covered, and how to change it.

Open it from the account menu at the top right, not the sidebar. Come here to upgrade or to check what your plan allows.

Nothing.