Plausible

• Get site totalsThe numbers across the top of a Plausible dashboard - unique visitors, visits, pageviews, bounce rate and average visit duration - for a period you choose. One number per metric, returned on 'totals' so a later step can read totals.visitors directly. Add filters to ask the same question about a slice of the traffic.
• Get visitors over timeTraffic split into time buckets - by hour, day, week or month - for charting a period or comparing one day against the next. Every bucket valid for the period is also returned on 'time_labels', including the empty ones the rows leave out, so a chart has a complete axis.
• Get current visitorsHow many people are on the site right now, as the count of unique visitors in the last few minutes. Returned on 'visitors'. Use it to watch a launch, or to alert when traffic spikes or falls away.
• List top pagesThe most-visited pages, with visitors and pageviews for each. This is the one breakdown where scroll depth and time on page are available, because both are measured per page.
• List entry pagesThe pages visits started on - the first thing each visitor saw. Bounce rate here needs Plausible Cloud or a self-hosted Community Edition on 3.1.0 or newer; drop it from the metrics on an older instance.
• List exit pagesThe pages visits ended on - the last thing each visitor saw before leaving.
• List traffic sourcesWhere visitors came from, as the tidied-up source names Plausible shows on its dashboard - 'Google', 'Hacker News'. Use 'List referrers' instead for the raw referring host.
• List acquisition channelsTraffic grouped into channels - organic search, paid search, referral, social, email, direct. The level above individual sources, and the one to report on month over month. Plausible works the channel out itself from the referrer and the campaign tags.
• List referrersThe raw referring hosts visits arrived from, before Plausible tidies them into source names. Use this when you need the actual domain that linked to you.
• List campaign trafficCampaign traffic broken down by whichever UTM tag you pick - source, medium, campaign, content or term. One action rather than five, because the question is always the same and only the tag changes.
• List countriesVisitors by country, by name rather than by code. Turn on 'Include country codes' as well if a downstream system wants the two-letter ISO code.
• List regionsVisitors by region or state, by name. Plausible works the region out from the IP address and does not store it, so coverage is good but not complete.
• List citiesVisitors by city, by name. Plausible also has a numeric city ID, which is no use in a workflow, so the name is what this returns.
• List browsersVisitors by browser, or by browser version if you need to know whether anyone is still on an old one.
• List operating systemsVisitors by operating system, or by OS version.
• List device sizesVisitors by device size - desktop, laptop, tablet or mobile. Plausible works these out from the screen width, so they are size buckets rather than detected hardware.
• List goal conversionsHow each goal is converting - unique visitors, total conversions and conversion rate per goal. The revenue metrics are off by default and only work on a site with revenue goals configured; asking for them on a site without any is refused by Plausible.
• List custom property valuesThe values one custom property took, and how many visitors saw each - the author of a post, the plan on a pricing page, whatever your events carry. Give the property's bare name, such as 'author'. Custom properties are a Business plan feature and a site with none returns no rows.
• Run a stats queryAsk Plausible anything its Stats API can answer: pick the metrics and the dimensions to group by yourself. Use this when no other step here is the shape you want - two dimensions at once, or a dimension the other steps do not offer. Plausible's own rules still apply: 'percentage' needs a dimension, scroll depth and time on page need event:page, and the conversion and revenue metrics need event:goal.
• Send eventRecord a pageview or a custom event against a site - a signup completing, an order being placed, anything that happens somewhere a tracking script cannot see. This is the one step here that works on every Plausible plan, because the events endpoint needs no API key. Two things to know: Plausible answers 'accepted' without promising to count it, so check 'dropped' on the result; and it works out who the visitor is from the User-Agent and IP address it is sent, so leaving both blank attributes every event to this server as one visitor.

No actions match that.