The post Calculated metrics appeared first on Piwik PRO.
]]>Pages per visitor: Similar to the default metric: Page views in a session. It shows you the average number of pages a visitor viewed on your site.
Name: Pages / visitors
Formatting: Number
Formula: {page_views} / {visitors}
Visitor e-commerce conversion rate: Focuses on e-commerce conversions based on visitors (not sessions).
Name: Visitor e-commerce conversion rate
Formatting: Percentage.
Formula: {ecommerce_conversions} / {visitors}
No-bounces: The opposite of the default metric: Bounces. It helps you focus on traffic that didn’t bounce after the first-page view.
Name: No-bounces
Formatting: Number
Formula: {sessions} – {bounces}
The post Calculated metrics appeared first on Piwik PRO.
]]>The post California Privacy Rights Act (CPRA) appeared first on Piwik PRO.
]]>For more information on the CPRA, CCPA, and other laws in the US, check out our blog content:
The post California Privacy Rights Act (CPRA) appeared first on Piwik PRO.
]]>The post Call to action (CTA) appeared first on Piwik PRO.
]]>In most cases CTA is represented by a distinctive button. CTA should be visible, clear and promising. CTAs should be a vital part of A/B testing .
More about the call-to-actions on the Piwik PRO blog:
The post Call to action (CTA) appeared first on Piwik PRO.
]]>The post Campaign tracking appeared first on Piwik PRO.
]]>What’s more, campaign tracking helps you with conversion attribution, that is, assigning credit for conversions in a customer journey that spans more than one channel.

Campaign tracking requires tagging the links you use in campaigns. Tagging means adding special parameters to URLs so your analytics software can recognize a particular campaign and assess exactly how your ad or marketing initiatives are performing.
Tagged URLs contain information about source, medium, keywords and the campaign name.
An example of a tagged URL using PK parameters (used only in Piwik PRO):
https://www.example.com/?pk_source=google&pk_medium=cpc&pk_campaign=Winter2019
An example of a tagged URL using UTM parameters (used in multiple analytics and marketing platforms, also in Piwik PRO):
https://www.example.com/?utm_source=google&utm_medium=cpc&utm_campaign=Winter2019
In both examples, we can extract the following information:
More about campaign tracking on the Piwik PRO blog:
To get more technical perspective on campaign tracking, visit our help center: Campaign report
Feel free to use our own tagging tool: Piwik PRO URL builder
The post Campaign tracking appeared first on Piwik PRO.
]]>The post Cart abandonment rate appeared first on Piwik PRO.
]]>The post Cart abandonment rate appeared first on Piwik PRO.
]]>The post Churn rate appeared first on Piwik PRO.
]]>The post Churn rate appeared first on Piwik PRO.
]]>The post Click analytics appeared first on Piwik PRO.
]]>Marketing performance analytics
The post Click analytics appeared first on Piwik PRO.
]]>The post Click path appeared first on Piwik PRO.
]]>
More about click path and user flow on the Piwik PRO blog:
For more technical aspects of the user flow, read Piwik PRO help center articles:
The post Click path appeared first on Piwik PRO.
]]>The post Click-through rate (CTR) appeared first on Piwik PRO.
]]>The post Click-through rate (CTR) appeared first on Piwik PRO.
]]>The post Client-side analytics appeared first on Piwik PRO.
]]>The characteristics of client-side analytics include:
Client-side analytics differs from server-side analytics, which involves tracking and collecting website data on a dedicated server of a website or app.
A hybrid tracking method known as server-side tracking with a first-party collector combines the benefits of server-side and client-side analytics. In this approach, cookies are set on the client side, and the tracking requests come directly to a first-party domain instead of a third-party analytics platform.
Learn more:
The post Client-side analytics appeared first on Piwik PRO.
]]>