---
title: "Shared journey context and pull request checks | Skene Cloud"
description: "Connect product sources, review journey context and check each experiment’s tracking in Skene Cloud. Keep source evidence, tracking coverage and measured outcomes distinct."
url: https://www.skene.ai/developers/cloud
doc_version: "d60348ad2b72"
last_updated: 2026-11-05
---

Skene Cloud

# Skene Cloud keeps each experiment’s plan, tracking checks and pull request reviews in one workspace.

Connect your repository and data sources to a shared workspace. Skene maps each milestone the growth team measures to the tracking calls and tables behind it, and rechecks them as the code changes.

[Measure your first experiment free](https://www.skene.ai/signup) [Read the Cloud docs](https://www.skene.ai/resources/docs/cloud)

Issues

See if tracking can answer it.

Ask a question. Skene names what is missing.

Ask a question Auto

- Marketing ops

- Sales ops

- CS ops

- Product ops

- RevOps / GTM ops

- Data ops

- Can we tell whether acquisition events are tied to a known user or anonymous visitor?

- Can connected analytics sources support attribution by provider and source role?

- Do ingested analytics events carry the properties needed to identify an acquisition path?

The Agent page in Skene’s own skene-web workspace. Captured from the live app on 29 October 2026 and redrawn. The text is the app’s own.

Agent **I want to increase retention with our customers**

I want to increase retention with our customers

14 investigation steps

To answer this question we need the following events:

| Event | Why | Parameters | Status |
| --- | --- | --- | --- |
| `first_value` | This marks when an account reaches the product outcome, which is the key point to measure retention from. | `plan` `timestamp` | Not found |
| `feature_used` | This shows which parts of the product customers keep returning to after activation. | `feature` `plan` `timestamp` | Not found |
| `onboarding_step_completed` | This identifies where customers stop during setup, which helps find early drop-off that hurts retention. | `step` `timestamp` | Not found |
| `subscription_cancelled` | This captures churn directly so you can measure how retention changes over time. | `plan` `timestamp` | Not found |
| `support_ticket_opened` | This helps connect support issues to later churn or repeated use patterns. | `timestamp` | Not found |

Open coverage

A saved Agent answer in Skene’s own skene-web workspace. Captured from the live app on 29 October 2026 and redrawn. The text is the app’s own.

## Read each state for what it establishes.

A plan your team has reviewed is ready to check, and reaching its target is a separate result that needs data from the measurement window.

| State | What it establishes | What comes next |
| --- | --- | --- |
| Found in code | The tracking call exists in scanned source. | Check received activity separately. |
| Evidence received | Activity is available from a connected source. | Verify the plan’s requirements. |
| Requirement verified | The plan’s required evidence is available. | Evaluate results for the measurement window. |
| Target reached | The measured result meets the plan’s target. | Your team decides what to do. |

## Review changes to the plan and its tracking.

Proposed canvas edits wait for the growth team to accept them, while tracking changes go through review in the repository like any other code.

Journey context

### Inspect the proposed milestone.

Accept a suggested canvas change to save it into the journey definition. A journey file you upload or push from the CLI overrides the one the analysis generates.

Changed code [Inspect a review finding](https://www.skene.ai/developers)

### Check what the changed code still tracks.

Enable GitHub reviews to identify removed or broken tracking. You review the proposed correction or hand its prompt to your coding agent.

## Choose the working surface.

[See the CLI](https://www.skene.ai/community/open-source)

### Skene OSS

Run uvx skene analyse-journey . on your machine with your chosen model provider. It writes skene-context/journey.yaml.

[Review connections](https://www.skene.ai/product/integrations)

### Skene Cloud

Share source connections, journey artifacts and review history. With reviews on, each pull request is checked for removed or broken tracking.

[See the MCP server](https://www.skene.ai/developers/mcp)

### Hosted MCP

Authorize your coding agent to use scoped workspace tools. The skene_gap tool returns coverage gaps against the planned baseline.

## Create a workspace and connect a source.

[Measure your first experiment free](https://www.skene.ai/signup)

Your first experiment is free with no card, and pull request reviews come with every plan, Free included.

## Sitemap

- [Markdown sitemap](https://www.skene.ai/sitemap.md): every page on this site, with its markdown counterpart.
- [Index for language models](https://www.skene.ai/llms.txt): the same set as a link-dense index.
- [Full corpus](https://www.skene.ai/llms-full.txt): reference content concatenated as plain text.
