For Lifecycle
Measure a lifecycle campaign by what customers do in the product.
A trial-conversion reminder is an experiment with a goal. Engineering ships the product events behind its conditions and results, and Skene checks that they exist. Your campaign tool still owns eligibility and sending.
A real answer / Skene’s own workspace
Check that a trial can be tied to its paid plan.
9 investigation steps
To answer this question we need the following events:
| Event | Why | Parameters | Status |
|---|---|---|---|
public. | This table should show the subscription or plan linkage needed to determine whether a trial workspace later moved onto a paid plan. | workspace_ | Verified |
public. | This table can provide the workspace identity and current lifecycle state needed to join the trial record to the later paid subscription. | workspace_ | Verified |
When an event is missing
A named requirement gives engineering a starting point.
- 01 / Skene
Names the gap
When an event the campaign needs, such as
trial_expiring, is missing, Skene names it and writes a How to fix brief. - 02 / Coding agent
Prepares the change
Adds the tracking from the brief, with the properties it lists.
- 03 / Engineering
Reviews the change
Confirms when the event fires and which fields it sends.
- 04 / Skene
Checks again
Compares the requirement with your data. The requirement is met once the event arrives there.
Bring the campaign and its goal.
Your workspace owner connects the code and data sources behind the campaign’s events. Skene drafts the requirements and checks the evidence those sources supply.
Audience rules and sending stay in your campaign tool.
Use the observed outcome to change the message or the audience for the next campaign. Skene sends nothing to your customers.
Check the events behind your next campaign.
Your first experiment is free, with no card.
Measure your first experiment free