Testing
Review product and campaign economics with ROAS, break-even context, decision rules, and supporting evidence.
What this module does
Testing is the performance decision workspace in CapitalOS. It organizes product and campaign evidence so an organization can compare advertising spend, revenue, break-even economics, profit context, setup health, and recommended actions.
The workspace changes its presentation by platform. The combined view rolls performance up by product, the Meta view focuses on product ROAS, and the Google view organizes decisions around campaigns and their products.
When to use it
Use Testing when your team needs to decide whether a product or campaign should continue, be reviewed, be stopped, or receive more attention. It is also useful for finding missing economics, weak attribution, incomplete setup, and differences between platform and blended performance.
Testing is a decision aid. It does not replace checking the source advertising and commerce accounts when data is delayed, incomplete, or disputed.
How it fits into CapitalOS
Testing uses the shared product and SKU identity together with commerce, order, cost, and advertising data. Product economics from Quotation and operational sales evidence can affect break-even and profitability context.
The product detail view can show testing history alongside other module records. This allows a team to review performance without losing the product’s research, sourcing, sales, and returns context.
Main concepts
- Platform filter: switches between the combined portfolio, Meta product, and Google campaign perspectives.
- ROAS: revenue attributed to advertising divided by advertising spend for the selected evidence.
- Break-even ROAS: the ROAS level at which the available product economics indicate break-even.
- Decision action: a rule-informed label that helps prioritize review; it is not an automatic business decision.
- Decision reason: the evidence explaining why a row received its current action.
- Setup health: signals that required matching or economics may be incomplete.
- Review state: organization-user tracking for rows that need or have received attention.
- Date and evidence: the time window, orders, campaigns, spend, sales, and product matches behind the result.
Typical workflow
- Select the active organization and the relevant platform view.
- Confirm the date range and any action, platform, or search filters.
- Review spend, revenue, ROAS, break-even ROAS, profit context, and setup health.
- Open a row to inspect its decision explanation and supporting order or campaign evidence.
- Check whether cost, SKU, product, order, or campaign matching is incomplete.
- Apply the organization’s testing rules and business judgment.
- Update the review state or export the view when the team needs a working list.
Permissions and prerequisites
You need Testing access for the organization. Meaningful results also depend on connected and synchronized commerce or advertising data, valid SKU matching, and sufficient product economics.
Meta and Google views require their respective organization integrations. A blank metric or setup warning should be investigated before a product is classified as a winner or loser.
Guides planned for this module
- Read product and campaign performance.
- Review Meta product ROAS and break-even context.
- Review Google campaign and product evidence.
- Configure and interpret testing decision rules.
- Investigate missing economics or setup-health warnings.
- Use search, action filters, review state, and exports.
- Read a product’s testing history.