Skip to content
All routines
MarketingEvery Monday

Monday growth report

Compare signups, activation, churn, and revenue with the previous week, then explain the changes worth discussing.

Starting request

Tell OpenTag exactly what to repeat

“Every Monday at 09:00 [timezone], compare last week's signups and activation in PostHog with subscription and revenue changes in Stripe. Post a sourced summary in #growth.”

Use this as a starting point, then replace the example details with the sources, scope, and destination your team uses.

After setup, paste this into Slack and review the first result before scheduling it.

A weekly report your team can act on

Bring product analytics and subscription reporting into one weekly Slack update. OpenTag reads the PostHog project and Stripe account you connect, compares the periods you specify, and prepares a report your team can check against its sources.

Example output

Illustrative example with invented data. This is not a customer result or a captured OpenTag run.

Signups
150 this week versus 120 last week: up 25%. Source: the selected PostHog signup insight.
Activation
36% versus 40% for the fully observed signup cohorts. State the activation event and observation window beside the comparison.
Revenue
$8,600 versus $8,000 in collected subscription payments: up 7.5%. Source: Stripe. This is a payment measure, not MRR.
What needs attention
Signups grew while activation weakened. Check the affected segments before attributing the change to onboarding or a marketing campaign.
Sources and gaps
Include the PostHog and Stripe source links, reporting dates and definitions. Name any unavailable data rather than filling in the missing result.

Decide these details first

  1. Choose the reporting window

    Use the same timezone and complete week for both sources. Say whether the report covers calendar weeks or rolling seven-day periods.

  2. Define activation and revenue

    Name the signup and activation events and the observation window. Choose collected revenue, recurring revenue or another explicit measure; payments and MRR are different quantities.

  3. Choose who receives it

    Name the Slack channel or DM and confirm that its audience should receive the report. Review a one-off result before enabling the recurring schedule.

Access and limits

  • Stripe is read-only in OpenTag. This workflow does not refund payments, change subscriptions or edit account records.
  • PostHog access is limited to the project and permissions you connect. This reporting request does not require changing feature flags or dashboards.
  • A period-over-period change does not establish its cause. Recent signup cohorts may also need time to complete the activation window.

Setup and source guides

Shape it around your team

The example gives you a useful structure. The connections, scope, and schedule should match the way your team actually works.

  1. 1

    Connect the sources

    Connect PostHog and Stripe. OpenTag can only use the accounts and records those connections allow.

  2. 2

    Make the scope explicit

    Name the exact accounts, projects, owners, date range, and time zone that matter. Replace the example details with your team’s own.

  3. 3

    Check the first run

    Run it once, review the source links and Slack destination, then keep or adjust the every monday timing.

Keep the same team context and find another recurring job to hand off.

View all marketing
  • MarketingEvery Friday

    Paid social performance

    Summarise spend and results on Meta Ads using the same comparison window each week.

    • Meta Ads
    • Slack
    Example request

    “Every Friday at 15:00 [timezone], compare this week's Meta Ads spend and results with last week using the same attribution window. Post the largest changes in #marketing.”

    View routine
  • MarketingEvery Monday

    Website and SEO pulse

    Bring traffic and search performance into one weekly report with links to the source data.

    • Plausible
    • Search Console
    • Slack
    Example request

    “Every Monday at 10:00 [timezone], compare last week's website traffic in Plausible and search performance in Google Search Console with the week before. Post the changes and source links in #marketing.”

    View routine

Describe the job. OpenTag builds the routine.

Name what to read, the period to cover, the result you need, when it should run, and where it should go. Run it once and check the result before relying on the schedule.

  • Sources
  • Time window
  • Output
  • Schedule
  • Destination