Plausible Analytics integration

What it does

The Plausible Analytics integration lets your agency run privacy-friendly analytics operations on behalf of your clients without leaving TaskJuice. Connect a client's Plausible site once and you can track server-side events and goals, run v2 Stats API queries with full dimension and filter control, fetch aggregate metrics over a period, pull day-bucketed timeseries, and break a metric down by page, source, country, or any other Plausible property. A daily polling trigger snapshots the timeseries so you can fan out scheduled digests, retention reports, or anomaly alerts to the rest of your workflow.

Connect a Plausible account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Plausible Analytics and click Connect.
3. Pick the right host. Use https://plausible.io for Plausible Cloud, or the base URL of a self-hosted Plausible install.
4. In Plausible, open the account menu, choose Settings, scroll to API Keys, generate a new Stats API key, and paste the value into TaskJuice. Stats API access requires a Business plan.
5. Enter the client's site domain exactly as it appears in their Plausible dashboard (for example example.com). Plausible uses this domain as the site_id on every Stats API request.

See the Plausible Stats API docs for the full key-scoping flow and the rate-limit budget.

Triggers

• plausible/daily-stats-snapshot polls the Plausible timeseries endpoint each cycle and emits one activation per cycle with items carrying every day-bucket observed in the configured lookback window. Configure the period, metrics, and poll interval per workflow.

Plausible does not push event webhooks, so polling is the supported trigger shape. Day-bucket granularity means an hourly or daily interval is appropriate; sub-hourly polling burns the Stats API budget without surfacing new data.

Actions

• plausible/track-event posts a pageview or custom goal to Plausible's Events API. Supply the event name (pageview or any configured goal), URL, optional referrer, optional custom properties, and the original client User-Agent and IP when ingesting from a server.
• plausible/query-stats runs a v2 Stats API query. Supply metrics, date range, optional dimensions, filters, ordering, and pagination. Returns one row per dimension tuple.
• plausible/get-aggregate returns aggregated metrics (visitors, pageviews, bounce rate, visit duration, events) over a preset or custom period. Optional compare=previous_period adds period-over-period change.
• plausible/get-timeseries returns a time-bucketed series of metrics with date, month, hour, or minute interval.
• plausible/get-breakdown returns a metric broken down by a property (page, source, country, browser, device, UTM tag, etc.) with page-number pagination.

Known limitations

• Stats API access is a Business plan feature. Free and Starter plans can use the Events API endpoint but not the query, aggregate, timeseries, or breakdown endpoints.
• Stats API keys default to a 600 requests per hour budget. When the budget is exhausted Plausible returns a 429, which TaskJuice surfaces as a retryable error so downstream resilience policies can back off.
• The Events API does not require an API key; it identifies the destination site by the domain value in the request body, which TaskJuice fills from the connection's site ID.
• When ingesting events from a server, supply the original client User-Agent and IP. Forwarding your own server's IP causes Plausible's bot filter to drop the event. The track-event action surfaces the x-plausible-dropped response header on the action output.
• Self-hosted Plausible instances must be reachable from TaskJuice's network. Behind-VPN or local-only deployments are not supported.
• Plausible does not push event webhooks. Realtime fan-out is not possible; use the polling trigger or the action set inside a scheduled workflow.