Our pricing is based on the monthly number of actions tracked in Piwik PRO. Here’s a list of actions in Piwik PRO:
Basic actions
| Action name | Tracked by default | Description |
|---|---|---|
| Broken event | An event that wasn’t tracked correctly due to some error. Broken events are reported only in the tracker debugger and contain a message that can help you fix the issue. | |
| Custom event |
A visitor performs a custom event. By default, Piwik PRO tracks as custom events: page scrolls and JavaScript errors. (Page scrolls can be turned off in Administration > Sites & apps > Data collection > Page scrolling > Measure scroll depth. JavaScript errors can be turned off in Tag Manager > Piwik PRO tag (tracking code) > UX issues > Detect JavaScript errors.) Other custom events can be set up additionally. |
|
| Content impression |
A visitor sees a custom popup or content. It can be turned on in Tag Manager > Piwik PRO tag (tracking code) > Data collection > Interactions with popups and content.) |
|
| Content interaction |
A visitor interacts with a custom popup or content. It can be turned on in Tag Manager > Piwik PRO tag (tracking code) > Data collection > Interactions with popups and content.) |
|
| Custom ping | Any ping that is sent by the user. For example, a custom ping to inject the time after a visitor clicked on something. | |
| Download | A visitor downloads a file. | |
| Goal conversion |
A visitor completes a goal. Goals can be turned on in Analytics > Goals > Add a goal. |
|
| Heartbeat ping |
A ping requests responsible for counting the time spent on a page. You can turn off heartbeat pings in Menu > Tag Manager > Tags > Piwik PRO > Data collection > Count session time precisely (off). Read more |
|
| Internal search | A visitor uses your internal search engine. | |
| Outlink | A visitor clicks the link to an external website. | |
| Page performance metric | A ping request responsible for calculating page performance metrics used in the page timing report. | |
| Page view | A visitor visits a page. |
Consent actions
| Action name | Tracked by default | Description |
|---|---|---|
| Consent form impression | A visitor sees a consent form on your site. | |
| Consent form click | A visitor clicks on a button on a consent form on your site. | |
| Consent decision | A visitor makes a decision using a consent form on your site. |
Ecommerce actions
| Action name | Tracked by default | Description |
|---|---|---|
| Ecommerce order | A visitor buys your product. | |
| Abandoned cart | A visitor abandons the cart. |
SharePoint actions
| Action name | Tracked by default | Description |
|---|---|---|
| SharePoint | Additional events tracked when you’re using SharePoint integration. |
Before signing a contract, we’ll help you estimate the number of actions for your plan and propose the pricing for you. However, if you want to check the number of actions beforehand, you can do it in the following ways:
Google Analytics
Check the number of hits. The hits in Google Analytics are similar to our actions. They are not identical though. So the number you’ll come up with will be an estimated value.
For selected date range
- Page views + events = Hits
- Google Analytics > Behavior > Overview > Pageviews
- Google Analytics > Behavior > Events > Overview > Events
For last 30 days
- Google Analytics > Admin > Property Settings > Property Hit Volume
Google Analytics 4
Check the number of events. Events in Google Analytics 4 are similar our actions. They are not identical though. So the number you come up with will be an estimated value.
For selected date range
- Google Analytics 4 > Events > Overview > Event count
Piwik PRO
Check the number of actions in Piwik PRO.
Available from 16.2.3
- Piwik PRO > Administration > Settings > Subscription > Plan
Custom reports (for versions below 16.2.3)
- For a single site or app: create a custom report
- For all sites and apps: create a meta site and a custom report
Other methods
- Check the number of page views on your website. In most cases, the number of actions consists of over 90% page views. But this is not a rule for ecommerce websites where visitors perform many events during the session. Also, if you’re planning to use many custom events or merge data through Audience Manager, the proportions will be different.
- Check the monthly number of requests in your server log. This will give you a rough number of actions — 10-20% of the original number. The inaccuracy of this calculation is because visitors tend to perform more than one action during one session, some of the visitors use tracking blockers or don’t agree to being tracked.