Pricing
Lifecycle

Catch the signal change before your campaign sends.

Say a release moves the welcome trigger from setup finishing to a row being inserted. The campaign still runs. It now welcomes people who never finished setup.

Start freeSee a flagged release

Sign in, connect a source, run one free audit. No card.

Illustrative product view. The same trigger can mean another moment.
plan
CreateSet upComplete
before→→send
aftersend→→
check
setup_completed
changed meaning

The welcome still sends. A newly inserted row does not mean the person has finished setup.

  • Check the signal behind the condition

    A campaign condition depends on a named signal. Skene checks the recording that feeds it.

  • Review the source change

    The pull request review names a missing event and the location that needs attention.

  • Keep your lifecycle tool

    The release check flags the recording change. Your existing campaign still controls who gets a message.

SupabasePostHogMixpanelBigQueryResend
What breaks

A campaign wired to a broken signal does not fail loudly.

Before editing a campaign condition, distinguish a signal with no recent activity from one whose activity could not be checked.

The campaign that does not error.

Silent means no activity in the coverage window.

Unknown means activity is unavailable.

Start free
Illustrative product view. Activity belongs to a defined reporting window.
analytics
setup_completed
128
events · 30 daysActive in last 30 days

Keep the source change connected to the campaign decision.

A signal can remain present while its implementation changes. Review the finding with engineering before changing the message condition.

This real, redacted review shows a missing event and a later passing review. It does not claim to reproduce a lifecycle campaign.

check
1
missing event
08:14 UTC
verdict
Passed
later review
09:20 UTC
Skene's own review, 7 Aug 2026, identifiers redacted

The map is read out of your code and your schema.

Skene OSS defines seven stage categories; Cloud uses five by default. The OSS file keeps the source evidence with each milestone.

Analysis confidence describes the reading of the sources, not live event volume. Inspect the full OSS file format.

Every milestone points back to its source.
plan
7 stages
milestone → evidence
code
path
database
table

Generated from the public OSS schema, 8eb7942. No customer result is shown.

FAQ

What lifecycle owners ask first.

Start free
Onboarding changed last sprint. Does the map go stale?
Re-run the analysis against the updated source. Keep the source revision with the result so the map can be read in context.
Where do the counts beside a milestone come from?
The count requires an event-activity source. A path in code or a table in the schema does not itself establish recent activity.
Does the release check change my lifecycle campaign?
No. The release check reviews the code that records your events. It does not edit your campaign or send its messages. Skene Cloud also has separate, optional Automations that require read-write database access.

Check the trigger before you change the campaign.

Start with the event the campaign depends on. Inspect its source evidence and recent activity before changing who receives the message.

Start freeSee a flagged release