OneLence

View saved version →

---
name: daily-growth-brief
description: Gives the user a short daily briefing from their OneLence workspace covering today's priorities, which traffic sources to scale, hold or stop and why, and anything exceptional. Use when the user asks what to do today, how their site or marketing is doing, or for a morning or daily update from OneLence.
---

# Daily growth brief

Produce a briefing the user can read in under a minute, built only from what the OneLence tools return.

## Steps

1. If you don't know which site to use, call `onelence_get_account`. With one site, use it. With several, ask which one, or use the one the user named. Pass its domain as `site` from then on.
2. Call `onelence_get_briefing` for that site. It returns today's priorities, the Decisions (scale, hold, stop) with their reasons, data sufficiency and alerts.
3. Only when a Decision needs explaining, or the user asks why, call `onelence_get_decision` with that source's `source_id`.
4. If the briefing says data is insufficient, call `onelence_list_evidence_gaps` and name the one fix that matters most.

## Writing the brief

- Open with the one or two things to do today, in the order OneLence ranks them.
- Then list scale, hold and stop: one line per source with OneLence's reason.
- Add alerts only if there are any.
- Close with what limits confidence, if anything.
- Keep to about 10 lines unless the user asks for more.

## Rules

- Decisions come only from `onelence_get_briefing` and `onelence_get_decision`. Never turn performance numbers, signals or evidence gaps into a recommendation to scale, hold or stop.
- Report values for the window the tool states. A missing value is unknown, not zero.
- Do not estimate ROI, profit, CAC, LTV, incremental or causal impact, or revenue at risk. OneLence does not provide those claims, so neither should the brief.
- Link to OneLence with the URLs the tools return when the user needs to act there.

View saved version →

---
name: decision-review
description: Explains one OneLence Decision (scale, hold or stop) for a traffic source or affiliate partner, covering the reasons, evidence, limitations, related signals and the next review step, and can record the user's feedback on it. Use when the user asks why OneLence says to scale, hold or stop a source, wants to dig into a channel, campaign source or partner, or disagrees with a Decision.
---

# Decision review

Walk the user through one source's Decision using what OneLence returns.

## Steps

1. Find the source. If the user named it loosely ("Meta", "the newsletter", a partner), call `onelence_list_sources` or `onelence_list_decisions` and match it. Use `type=affiliate` for partners. Confirm the match when it is ambiguous.
2. Call `onelence_get_decision` with the `source_id`. It returns the Decision, its reasons, the evidence, the limitations, the next review step, and related signals and evidence gaps.
3. When the user wants numbers, call `onelence_get_performance` with `filter_dimension=source` and the source's name as `filter_value`.
4. Set it against another source with `onelence_compare_sources` only when the user asks. That comparison ranks nothing and is not a Decision.

## Explaining it

- State the Decision and OneLence's reasons in plain words.
- Then what the evidence shows, and what it can't show (the limitations).
- Then the next review step: what OneLence is waiting for, and when.
- If evidence gaps limit confidence, name who must act and include the link the tool returns.

## Feedback

If the user says the Decision was useful, already acted on, not relevant, or based on wrong data, offer to record it with `onelence_give_decision_feedback`.

- Pass the posture the Decision showed.
- The tool first returns a summary and a `confirmation_id`. Show the summary.
- Call again with only the `confirmation_id` once the user agrees.

## Rules

- Never create, change or override a Decision yourself. Never derive one from performance or signals.
- No ROI, profit, CAC, LTV, incremental or causal impact, or revenue at risk.

View saved version →

---
name: install-tracking
description: Installs OneLence tracking (the @crelora/mark SDK) in the website or app in the current codebase. Covers pageviews and attribution, the activation event, and browser-side or server-side conversions, then checks in OneLence that events arrive. Use when the user asks to add, install, set up, fix or verify OneLence tracking, or to track signups, purchases or other conversions with OneLence.
---

# Install OneLence tracking

Integrate OneLence into this project so the user can deploy and see visitors, attribution, activation and conversions in OneLence. Make the technical decisions yourself. Ask the user only plain-language questions you can't answer from the code, one at a time.

## 1. Get the site's setup from OneLence

1. Call `onelence_get_setup` with `response_format=detailed`. It returns:
   - the site, and whether events already arrive;
   - the defined conversion events;
   - the install instructions: the publishable key (`pk_…`), site id and host, npm and script snippets, the server-side conversion endpoint, and a step-by-step guide.

   Follow that guide; it is the source of truth for this workspace.
2. If the account has no site for this domain, offer to register it with `onelence_register_site`. That is a two-step confirmed write: show the summary and confirm only after the user agrees.
3. The publishable key is browser-safe. Never put a secret key (`sk_…`) or any server credential in browser code, public environment variables or source maps. OneLence tools never return secret keys. For server-side conversions the user creates a secret key in OneLence (Settings → API keys) and stores it only in the server environment as `ONELENCE_SECRET_KEY`; read it from there and never ask the user to paste it into the chat.

## 2. Inspect the project before changing anything

- Framework, rendering mode (SPA, SSR, static, hybrid), package manager and the app's client entry point.
- The signup or activation flow, and the main conversion: purchase, subscription, lead or booking.
- Whether a backend confirms conversions (payment webhooks, database writes).
- Existing analytics, and any consent or CMP setup.

## 3. Implement

- **Install and initialise once**
  - With a JavaScript build: install `@crelora/mark` with the project's package manager, then call `Mark.init({...})` once in the client root lifecycle, with the values from step 1 and `autocapture: { pageview: true }`.
  - Without a build: use the script snippet from step 1 in the global head or layout.
- **Base tracking**: let the SDK capture pageviews, visitor and session identity, and UTM and click-id attribution. Don't rebuild them by hand. Handle SPA route changes, double initialisation in development mode, and consent gating.
- **Activity**: `Mark.track('Event Name', {...})` for the real activation point and a few high-value actions. Don't create dozens of low-value events.
- **Conversions**: `Mark.conversion('Conversion Name', {...})` only for confirmed outcomes.
  - Prefer server-side or hybrid conversions when the backend confirms them, keeping the visitor attribution context the instructions describe.
  - Never send the same conversion from both browser and server unless the instructions say so.
- **Define the conversions in OneLence**: if a conversion isn't defined yet, add it with `onelence_save_event_definition` (two-step confirmed write) using the exact event name the code sends.
- **Consent**: respect the existing consent mechanism. Don't add a second one.
- **Existing analytics**: leave them as they are. OneLence runs alongside them.

## 4. Verify

1. Run the project's build, typecheck and tests.
2. After the user (or you, locally) visits the site and triggers the flows, call:
   - `onelence_verify_tracking` with a short `minutes` window, optionally passing an `event_name`;
   - `onelence_list_events` to see the event names and page paths that arrived.
3. If nothing arrives, check the init values, consent gating, ad blockers in the test browser and the site host, then verify again.

## 5. Report to the user, in non-technical language

- What OneLence now captures, which activation and conversions are tracked, and whether each conversion is browser-side, server-side or hybrid.
- What they still need to do: deploy, set the server environment variable, or check something in OneLence.
- How to verify it: exactly what to click on the site and what to expect in OneLence.

Docs: https://onelence.com/docs/integrations/start-integration/developer-setup and https://www.npmjs.com/package/@crelora/mark

View saved version →

---
name: record-a-change
description: Records a business change the team made outside OneLence (a budget change, new offer or price, tracking fix, new creative, campaign launch, or partner commission change) so OneLence can observe the period after it. Use when the user says they changed, launched, paused, raised or lowered something in their marketing or product and wants it logged in OneLence.
---

# Record a change

Log a change in OneLence so later reviews can show it next to what was observed afterwards.

## Collect

Ask only for what you can't infer from the conversation:

- **What changed**, in a few words (`label`), e.g. "Raised the TikTok budget".
- **When**: the local date (`occurred_on`, YYYY-MM-DD), an optional time (`time`, HH:MM), and the `timezone` (IANA, e.g. Europe/Rome).
- **Where**: one source, or the whole site. To find a `source_id`, call `onelence_list_sources`.
- **Kind** (`family`): budget, offer, pricing, tracking, creative, campaign or partner, when clear.
- **Amounts**, only if the user gave them (`quantified_change`), e.g. a budget going from 50 to 80 EUR per day:
  - metric `budget`, change `from_to`, before `50`, after `80`;
  - unit `currency`, currency `EUR`, period `day`.
- An optional `note`.

## Record

1. Call `onelence_record_change` with the fields. It returns a summary and a `confirmation_id` and changes nothing yet.
2. Show the summary and ask the user to confirm.
3. Only after they agree, call `onelence_record_change` again with just the `confirmation_id`.
4. If something is wrong, start again with corrected fields rather than confirming.

## Rules

- This only records what the user reports. It changes nothing on ad platforms or anywhere else.
- Never say what effect the change had or will have. OneLence observes the period after it but states no impact.
- To see earlier changes, use `onelence_list_changes`.

View saved version →

---
name: weekly-review
description: Runs a weekly marketing review from OneLence covering how the site performed against the previous week, which sources moved, what changed, the changes the team recorded, and the Decisions to review. Use when the user asks for a weekly review, a weekly report, a recap of the last 7 days, or a summary to share with their team.
---

# Weekly review

Build a review of the last 7 days that the user can paste into a team update, from OneLence data only.

## Steps

1. Resolve the site as in any OneLence task. `onelence_get_account` lists the sites; pass the domain as `site`.
2. Set the window: the last 7 full days, ending yesterday, in the user's time zone when known. Use `start` and `end` as YYYY-MM-DD.
3. Call these:
   - `onelence_get_performance` with the window and `compare=previous_period`, for visitors, conversions, conversion rate, observed revenue and the top sources and channels.
   - `onelence_list_signals` for material observed changes in the period.
   - `onelence_list_changes` for what the team recorded (budget, offer, pricing, tracking, creative, campaign, partner).
   - `onelence_get_briefing` for the current Decisions and priorities.
4. When a source moved a lot, `onelence_get_breakdown` with `dimension=source`, or `onelence_compare_sources` for two sources, gives the detail.

## Structure

1. **Headline**: three numbers against the previous week, as the tool returns them.
2. **What moved**: sources or channels with the largest observed change, and the signals about them.
3. **What the team changed**: recorded changes with their dates. Put them next to the observed movement only as timing. OneLence never states that a change caused a result, so the review must not either.
4. **Decisions to review**: scale, hold and stop from the briefing, with OneLence's reasons.
5. **Confidence**: data sufficiency or evidence gaps that limit the reading.

## Rules

- Present observed values only. A missing value is unknown, not zero.
- No ROI, profit, CAC, LTV, incremental or causal impact, or forecasts.
- Decisions come only from the briefing and decision tools.