Understand participation with numbers that have a definition.

Keep the report close to its scope

Personal reports cover the appropriate owner’s actions. Workspace reports require an owner or editor and use that workspace owner’s licensed history. Action-specific reports also check editing or ownership permission. A user cannot obtain site-wide financial metrics by changing a client-side selector.

The date range uses UTC days and is limited by the relevant plan. A broad requested window can therefore be reduced by the server. Reports do not fabricate earlier history when the feature was not installed. Read the scope and date before comparing two exports or presenting a trend to a team.

Know what participation and completion mean

First participation records an identity’s initial saved response. Editing that response is not another new participant event. Closing an action records a lifecycle completion event; it does not establish that every task was independently verified, every guest attended or every outside obligation was fulfilled.

Recorded sharing reflects explicit platform operations rather than every copy of a URL across messaging applications. A challenge score remains self-reported. A bill calculation remains separate from settlement. The report is useful when its event definition stays attached to the number instead of being replaced with a stronger unsupported claim.

Optional visits are a partial measure

Public visit measurement requires the configured optional consent. Someone who chooses essential-only browsing is absent from that optional count. The result is not a complete visitor census and should not be used as an unqualified denominator for conversion claims about all visitors.

Operational reporting avoids raw participant-message bodies and raw IP addresses. It still deserves appropriate handling, especially for small private projects where context can identify activity. Aggregate does not automatically mean suitable for public release. Choose exports and recipients according to the team’s actual need.

Keep commercial reporting separate from accounting

Administrators can review recorded paid conversions and plan-sale revenue grouped by currency. That helps observe the commercial funnel without displaying fake sales. It is a gross operational record, not a reconciled refund-adjusted profit, tax or bank statement.

Use the actual WooCommerce or provider records for formal reconciliation. An eligible CSV export makes the defined report portable, but does not certify an external event or financial outcome. If a number looks wrong, check the event, UTC date, scope and consent boundary before assuming a data loss or purchase failure.

Illustrative interpretation: a response is edited

An owner creates a request and a participant saves an initial answer. The participant later corrects that answer from the same identity. Operational reporting records the first participation once, rather than claiming that the correction brought a second new person. When the owner closes the request, the closure is a lifecycle event; it does not independently verify the practical outcome outside the site.

Suppose some public visitors choose optional visit measurement and others choose essential-only browsing. The measured visits are then a consent-dependent subset. A participation-to-visit ratio needs that qualification and cannot honestly be presented as a complete conversion rate for every visitor. The same care applies to commercial metrics: gross recorded plan sales by currency are useful signals, while provider records remain necessary for refunds, fees and formal reconciliation. These are explanatory examples rather than invented platform growth statistics.

Before you share

1. Prepare: select the authorized personal, action or workspace scope.
2. Review: read the UTC window, event definition and consent boundary.
3. Handover: export only the needed report and keep its qualifications attached.

Make the next request clear.

Create an action ↗ · Read the detailed guide · Compare current plans