/Docs
ETEN

Console views

The console is your window into the engine: what is working, who is slipping away, and what to do next. Four views, each with its own role.

Home — what is happening right now

  • Glance tiles: the period's engine revenue, incrementality status, won-back customers, list size. Each tile clicks through to the full view. If your account runs without a holdout, the incrementality tile is replaced by Personalisation reach — how many contacts on your list carry live picks — see lift and incrementality.
  • Suggestions: the engine proposes ready-made next steps — e.g. "cooling customers worth reaching out to" — with a one-click push that creates the matching segment directly in Smaily.
  • Audience health: how your contacts are behaving right now (engagement states).
  • Audience maturity: how well the engine knows your customers, by purchase history — established (4+ orders), developing (2–3), new (1), just arrived (none yet). A large "just arrived" share is normal and simply means personalisation is still bestseller-based for those contacts; see cold start.
  • For interpreting the numbers, see the metrics glossary — the Home tiles are the same metrics in summary form.

Insights — are campaigns making money

  • Period picker + comparison: choose a window and compare with a previous one; KPI cards show the deltas. The engine revenue card carries the store's total revenue for the same period as a sub-line ("of €X store total").
  • Trend: each bar is one send — the full bar height is its click-based email revenue and the darker pink segment the share credited to the engine; open and click rates run as lines (right % axis), with linear trend lines as faint dashes; comparison periods as grey dashed lines; click a bar to preview the email.
  • Campaign table: each send's open/click rate, email revenue ("Email revenue (7d)") and engine revenue as a heatmap. Email revenue is click-based: orders placed within 7 days of the customer's last click on this campaign — any link in the email, not just recommendations; each order counts under one send only (last click wins) and engine-attributed orders are always included. Same methodology as GA/UTM-based "Campaign Revenue" tools, but computed from our data at the contact level — the numbers will NOT match Google Analytics one-to-one (see engine revenue vs total revenue). The campaign name opens an email preview. Test sends can be excluded from analysis. Rows marked "Computed from events" are sends Smaily reports no statistics for — automations and A/B splits — whose numbers the engine counts from email events instead (email metrics).
  • Lift slot: the holdout result if a measurement is running or has finished, otherwise Programme reach & response — reach and fill quality first, credited revenue second, no causal claim (lift and incrementality).
  • Engine sections: daily purchases with vs without a recommendation touch (descriptive — the second line is "no touch detected", not a control group), the weekly win-back trend, and "where credited revenue comes from" by recommendation type.
  • Top products: two side-by-side rankings over the last 30 days — what the engine recommended most (with click counts), and which recommended products customers actually bought, by engine-credited revenue. The lists rarely overlap: broadly pushed best-sellers and actually-converting niche picks are different things. Click counts are undercounted until store-side click tracking is live.
  • Note: yesterday's campaign appears here after it completes in Smaily and the sync runs — see email metrics.

Audience — who your customers are

  • List vs store: how many store customers are on the Smaily list, how many buyers are missing from it.
  • Filters: engagement state, source (on list / in store / both), a "Buyers" quick filter (at least one order), search; the table is sortable, including a "Last purchase" column (distinct from "last active", which also counts email opens and clicks).
  • Customer view (click a row): a timeline of every touch — purchases, emails, clicks, browsing, recommendation issues — with a source filter; each recommendation shows the reason the engine picked it.
  • "Create Smaily segment": turn the currently filtered view into a real Smaily segment for campaign targeting (up to 2000 contacts at a time).

Settings — modes and connections

  • Team: invite colleagues by email — they sign in with a magic link, no passwords. Roles: Owner (full access), Editor (acts on suggestions, creates segments, changes settings), Viewer (results only — Home, Insights, Audience; never sees Settings). Only the owner and editors can manage the team. A member whose access has been switched off stays in the list with a Disabled badge — re-invite the same email to restore access.
  • Appearance: light/dark/auto theme.
  • Privacy mode: the eye icon at the bottom of the sidebar blurs customer names and email addresses everywhere they appear — for demos, screen sharing or working in an open office. It is a visual aid only, not an access restriction, and it stays on per browser until you switch it off.
  • Connections: the Smaily account, store plugin and engine status — see here whether the data flow is healthy.
  • Who gets personalised content: the contact mode (conservative to broader) decides which contacts get recommendation fields written at all. A broader mode requires an explicit acknowledgement.

On your phone

Open the console on a phone and it offers to add itself to your home screen — after that it opens full-screen, without the browser bars, like any other app. On Android, tap Install; on an iPhone, tap the browser's Share button and choose Add to Home Screen. Dismiss the offer once and it stays gone on that device — Settings → App keeps the install option available for good, on the phone and on the desktop alike.

It is the same console, not an offline copy: nothing is stored on the phone, so it still needs a connection and your figures are always live.

Common misreadings

  • "The Home number doesn't match Insights" — check the period: Home shows a fixed window, Insights shows the window you selected.
  • "The Audience filter count doesn't match the KPI" — event vs state; see engagement states.

Last updated: 2026-08-10