The Site Traffic page displays general information on the activity of customers on your website, as collected by the Web Extend scripts.
Please note that when a contact is deleted, all of the data relating to that contact is also deleted. This will retrospectively affect any reports which use contact-level data, such as the ones on this page.
Viewing the reports
Select the time period from the calendar on the right and click Apply to refresh the graph. Hover your mouse over the graphs to see the exact figures for any given day.
Site traffic statistics are updated daily at around 09:00 UTC.
What the reports show
Each report shows data for a different type of activity:
Total Page Views – The total number of page views we tracked on your website. It equals the number of times the
gocommand was called on your website.
Total Product Views – The total number of product views we tracked on your website. It equals the number of times the
viewcommand was called on your website.
Total Orders – The number of individual orders that we tracked on your website. It equals the number of times the
purchasecommand was called on your website.
Total Order Lines – The number of unique items included in the tracked orders. It equals the number of order lines found in the orders reported by the
Total Revenue Tracked – The total sum of the order values reported by the
Downloading Site Traffic data
You can also download all the data for this period in .csv format and use it for further reporting, or compare it against your internal order database or an external analytics tool.
You can only export data for a maximum of 30 days. If the time period selected is greater than this, it will download data from the last 30 days of that period.
The number of total orders shown on the Site Traffic page is higher than the number of unique order IDs I can see in the downloaded .csv. How is that possible?
This is most probably due to the fact that your website passes the same order with the same order ID twice (or even more times) to Emarsys. It usually happens when the
purchase command is not implemented properly and is issued again whenever the user reloads the purchase confirmation page.
As currently we do not deduplicate purchases based on the submitted order IDs, such repeated submissions, which have the same content but a different timestamp, will be considered separate orders on our side.