Commands

tracee analytics

Performance, engagement and tracking health.

analytics

What posts and campaigns brought in (contacts, MQLs, spend).

tracee analytics [--days <n>]

Calls getPerformance.

tracking-health

Tracking health. Where ad platforms and the CRM disagree, and how each contact was (or wasn't) matched.

tracee analytics tracking-health [--days <days>]
  • --daysintegerdefault: 30

    Window in days, ending today

    1–365

Example
tracee analytics tracking-health --days 30
Calls GET /api/v1/analytics/tracking-health

engagement

Engagement per post and channel. What the platforms report per post (views, likes, comments, shares) and per channel (followers), plus clicks on Tracee short links, with totals per platform.

tracee analytics engagement [--days <days>] [--platforms <platforms>]
  • --daysintegerdefault: 30

    Window in days, ending today

    1–365

  • --platformsstring[]

    Only these networks, e.g. ["linkedin", "x"]; all by default Repeat the flag or separate values with commas.

    up to 40 itemseach up to 30 characters

Example
tracee analytics engagement --days 30
Calls GET /api/v1/analytics/engagement

website

Website analytics. The website, from whichever is connected: Google Analytics (sessions, users, key events by source/medium, top landing pages), Search Console (clicks, impressions, CTR, position, top queries and pages) and PostHog (visitors, pageviews, top pages, referrers).

tracee analytics website [--days <days>]
  • --daysintegerdefault: 30

    Window in days, ending today

    1–365

Calls GET /api/v1/analytics/website

revenue

Revenue by source, post and campaign. Payments from connected Stripe, Gumroad and Lemon Squeezy, net of refunds and per currency, matched to leads by email: revenue by source, by Tracee post and by ad campaign.

tracee analytics revenue [--days <days>]
  • --daysintegerdefault: 30

    Window in days, ending today

    1–365

Calls GET /api/v1/analytics/revenue