Sign-up → trial → paid funnel

The website-stats funnel counts sessions, and its drop-offs do not open people; the behavior-analysis funnel counts people and opens who stopped at a step. Trial has no built-in event name, so it has to be a name you already send.

Prerequisites

All three events are already being sent. Sign-up can be signup and payment can be purchase. Trial is your own name, for example trial_start. If that name is never sent, the step stays at zero.

Steps

1. Add three steps in behavior analysis

   Open ConsoleAll-platform analyticsBehaviorBehavior analysis. Use Add step to add signup, trial_start, and purchase in order. Leave Order at Ordered (other events allowed) and Counting at Unique users (first entry), which are the defaults.

2. Allow different sessions and set the window

   Require same session is off by default; leave it off. Sign-up and payment often happen on different visits. Conversion window defaults to 7 days and can be at most 180 days. Set it to your trial length.

3. Open the people who dropped

   In the step table, click the dropped count on a step and choose View users. The list is people who reached the previous step but not this one. The website-stats funnel does not have this action.

Verify

After real events arrive, the first step is above zero, and people who finish are fewer than or equal to the first step. Clicking a drop-off opens people, not only a session count.

Common failures

What you see	Why	What to do
Trial is zero	That event name is not sent	Emit it from the client or the server first
Almost everyone drops at payment	Require same session is on, and payment is a later visit	Turn it off and widen the window
You cannot open people	You used the website-stats funnel	Use the behavior-analysis funnel

Define purchase and generate RFM / PES

There is no generate-segments or generate-score button. Once purchase events become orders, the commerce page shows eleven RFM segments; the product engagement score is computed from the core events you name, on a 0 to 100 scale.

Prerequisites

Payment success is reported from the server with a key that has Server track. Do not leave the amount only on a browser click. Changing business settings and rebuilding orders requires an owner or admin.

Steps

1. Send purchase under the default name

   POST purchase to /api/v1/track with at least revenue, currency, and order_id. Use the order id as insert_id so a retry does not become a second order. Refunds use refund with the same order id.

2. Check the mapping

   Open the Commerce tab at ConsoleAll-platform analyticsConfigurationBusiness settings. The defaults are purchase event purchase, amount property revenue, currency property currency, and order id property order_id. Saving the mapping or the base currency rebuilds the order table automatically. To refresh by hand, click Rebuild orders on ConsoleAll-platform analyticsBusinessCommerce & revenue.

3. Read segments and the engagement score

   RFM segments on the commerce page scores recency, frequency, and monetary value from 1 to 5 and shows eleven segments. People with no purchase are left out. For the score, open the PES tab in business settings, enter event names separated by commas in Core events (≤10), then open ConsoleAll-platform analyticsBusinessProduct engagement. If the list is empty, Adoption is estimated from all custom events.

Verify

The commerce page shows orders and an order-table update time. After there is a buyer, at least one segment has a count above zero. The score page shows the average of Adoption, Stickiness, and Growth. A part that cannot be computed stays empty instead of becoming 0.

Common failures

What you see	Why	What to do
Orders stay at zero	The event name or amount property does not match the mapping	Align purchase and revenue, then rebuild
Segments are empty	Nobody has a successful purchase yet	Wait until the order table has a buyer
Adoption looks far too low	Too many core events, or names few people ever send	Keep events that mean the product was actually used

Alerts and a weekly report

When you finish, a metric notifies you when it moves past your percent versus the previous period, and a weekly report goes to your enabled channels every Monday. The period change in the create dialog always compares with the previous period; the same period last year is not offered.

Prerequisites

Creating a monitor requires an analyst or above. Saving channels and the subscription requires an owner or admin, and a plan that includes scheduled reports.

Steps

1. Add a channel that can send

   Open ConsoleConfigurationSettingsNotifications, add WeCom, DingTalk, Feishu, or a Webhook, and click Send test. Email can be added, but mail delivery is not enabled yet, so tests and real sends are recorded as skipped.

2. Create a period-change monitor

   Open ConsoleAll-platform analyticsOperationsMonitors and click New monitor. Under Builtin, uv is fine. Set Condition to Period change, then pick an operator, a percent, and a Granularity, for example greater than 30 percent by day. After saving, click Dry-run on the monitor card to see whether it would fire now.

3. Turn on the weekly report

   Back on the notifications page, under Scheduled reports, turn on Weekly report. It covers the previous Monday through Sunday and sends on Monday at the send hour you pick, in the site time zone. Select the channel, click Preview to read the body, then save. To send one right away, click Send now in the preview.

Verify

The dry run shows the current value and how many times the last 30 days would have fired. It does not send. Weekly deliveries appear in the Delivery log at the bottom of the notifications page, with status sent, failed, or skipped. Email stays skipped until mail delivery is enabled.

Common failures

What you see	Why	What to do
You wanted last year	Period change only compares with the previous period	Use the previous period, or a Threshold condition
The weekly report never arrives by email	Mail delivery is not enabled	Send it to a group bot or a Webhook
The monitor never fires	There is no previous-period data, or the move is under your percent	Read the dry run. The five ops alerts on the settings page are separate rules

Export and share by permission

A share link and a raw export are two separate controls. When you finish, the right role can open a read-only share, and a member with a data scope cannot take the raw rows.

Prerequisites

You know the five roles: owner, admin, analyst, viewer, and agent only. An agent-only member cannot open stats. Changing members and public sharing requires an owner or admin.

Steps

1. Decide who can turn sharing on

   Open ConsoleConfigurationSettingsMembers and set each person to a role. In a saved analysis's menu, Enable share link is shown only to an owner or admin. An analyst can build an analysis but cannot turn that link on.

2. Public sharing exposes only the modules you pick

   Open ConsoleConfigurationSettingsPublic sharing and turn on Enable public dashboard to get a read-only link. Visible modules are Overview, Pages, Sources, Audience, and Bots. You can set a password and a Maximum visible range. Filters for modules you did not enable are stripped, so they cannot be pulled in through link parameters.

3. Leave raw export to people without a data scope

   Open ConsoleAll-platform analyticsDataData export. The kinds are events, sessions, persons, autocapture, and consent_log. Export requires the Pro plan or above. A member who has a data scope is rejected with the message that members with a permission scope cannot export raw data.

Verify

A viewer can open reports and does not see the analysis share switch. A public link opened while signed out shows only the modules you checked. After you add a channel or domain scope to a member, that account fails to create an export. An owner with no scope can create one.

Common failures

What you see	Why	What to do
An analyst cannot find the share switch	Only an owner or admin sees it	Have an admin turn it on, or use public sharing
Export is rejected	The account has a data scope, or the plan is below Pro	Export from an admin with no scope; upgrade from Free first
An agent-only member sees no reports	That role only opens the workbench	Use viewer or analyst when they need numbers