Weekly tracker check-ins

Runs once a week. Iterates all active experiment trackers on the project, gathers current metric values, computes deltas vs baseline, and writes a check-in row. Feeds progression data into /analytics?tab=trackers and the daily-brief orchestrator.

A real workflow from the Magister template catalog — the same steps a dedicated agent executes for your brand, shown in full before you run anything.

The steps, in full

  1. 1

    List active trackers

    Call magister_list_trackers with status=active. If none exist, finish successfully with a zero-count summary.

  2. 2

    Record weekly check-ins

    For each active tracker, load it, read its real current persisted analytics values and canonical scorecard, compute movement and goal progress, then call magister_record_tracker_checkin with idempotency_key {workflow_run_id}:{tracker_id}. Isolate errors per tracker and never substitute zero for missing data.

  3. 3

    Summarize check-ins

    Report recorded, skipped, and failed counts. Do not send a separate email; the next Standard Brief reports tracker movement.

Capabilities it uses

Analytics TrackerAnalytics ReadFindings

What it won't do without you

Magister workflows draft and prepare autonomously, but anything externally visible — publishing a page, sending an email, changing a campaign — waits for your approval. You can run this template once, or schedule it and review the results as they land.

Fork it into your own agent

Start free: enter your website, get a full marketing audit, and run workflows like this one in your own stack.

More Orchestrator templates