Average order value (AOV) measures the average value of every order placed over a defined period. It drives key business decisions such as advertising spend, store layout, and product pricing. This metric is calculated by dividing the revenue by the number of orders.
AOV is defined by sales per order, not sales per customer. It means that although one customer may return multiple times to make a purchase, each order would be counted separately.
Average order value (AOV)
-

Anonymous website visitor tracking: How to do useful analytics without personal data [Updated]
Regulations worldwide, like GDPR or the ePrivacy Regulation, set a high bar for collecting user data. For one, GDPR requires consent to process the data if it’s reasonably likely that such data could be used to identify an individual. The problem is that consent opt-in rates typically vary between 30% and 70-80%. The solution? Anonymizing…
-

What is PII, non-PII, and personal data? [UPDATED]
Personally identifiable information (PII) and personal data are two classifications of data that often confuse organizations that collect, store and analyze such data. Both terms cover common ground, classifying information that could reveal an individual’s identity directly or indirectly. PII is used in the US, but no specific legal document defines it. The legal system…
Other definitions
Recent posts from Piwik PRO blog
- Anonymous website visitor tracking: How to do useful analytics without personal data [Updated]
- What is PII, non-PII, and personal data? [UPDATED]
- What is first-party data and how does it benefit your marketing strategy [Updated]
- Digital marketing analytics: The beginner’s guide to data-driven marketing success [Updated]
- We’re introducing Piwik PRO MCP Beta – get answers from your data without building a single report
- Google is changing how GA4 and Google Ads share data: Here’s how it puts your compliance at risk
- HIPAA-compliant analytics for healthcare systems: How hospital marketing teams can measure what matters
- Privacy by design in practice: How “just enough” data beats “just in case” collection