Easy online data management with DataOrganizer π
Gain access to up-to-date data from your e-commerce store. Our robots automatically analyze information from various sources, giving you full control over your e-commerce.
What you will find in the reports
Here you will find answers regarding DataOrganizer data from store systems such as WooCommerce, Idosell and Magento 2, as well as Google Analytics statistics and Google Ads, Facebook Ads, Criteo and Tradetracker advertising data. If you have any questions, our support team is ready to help.
The graph shows Net Revenue for the last 30 days. Net revenue per day from the store system(s) (from selected markets) whose data is connected to Datadiary. Net revenue only applies to orders with the status fulfilled and in progress for the given period.
The graph does not show statistical data from Google Analytics, but full revenue data from the store system(s).
The graph shows all Media Costs from the last 30 days. It shows the total costs for media expenses including advertising and affiliate commissions from all connected data sources, i.e. Google Ads, Meta Ads etc. to Datadiary per day.
The table presents data from the last periods: yesterday, last 7 days, last 30 days and the current month. For each of these periods, a comparison to the previous period is available, with information on whether the current period is better or worse than the previous one, along with a visual indicator of the difference.
In the table, you will find KPIs such as:
- Net revenue β Information on revenue without VAT, only for orders completed and in progress.
- Media costs β Total media costs from connected advertising and affiliation systems.
- Media cost share β Ratio of media costs to net revenue. A lower indicator means a higher margin and profitability of the company.
- Number of orders β Orders fulfilled and in progress according to data from the store system.
- Discount granted β The sum of the discount, as the difference between the regular price and the actual selling price of the products.
Google Analytics needs time to process the data, so full information is only available after 72 hours. Data from the last three days may be incomplete. The table includes data from periods such as yesterday, last 7 days, last 30 days and the current month. You can compare it with previous periods, and the differences are highlighted in color. You will find key metrics such as the number of users (new and returning), sessions, interactions with products (e.g. adding to cart, views) and the number of purchases. All data is collected in accordance with GDPR regulations and may be subject to user consent for cookies.
The chart shows net revenue and media costs for the selected period for specific markets.
– Net revenue per day from the store system(s) whose data is connected to Datadiary. Net revenue only applies to orders with the status fulfilled and in progress for the given period.
– Media costs is the sum of costs for media expenses including advertising and affiliate commissions from all data sources connected, i.e. Google Ads, Meta Ads, etc. to Datadiary per day.
The chart does not show statistical data from Google Analytics, but full revenue data from the store system(s).
The graph shows net revenue from the last 4 days and the revenue prediction calculated from the last four days and the revenue prediction for the next 4 days.
– Net revenue per day from the store system(s) whose data is connected to Datadiary. Net revenue applies only to orders with the status fulfilled and in progress for the given period.
– Revenue prediction is the estimated net revenue calculated based on Datadiary’s predictive models based on collected and processed data in the research and analytical methodology.
The pie chart displays all Media Costs broken down by source in percentage and dollar terms when you hover over the chart for the selected time period.
Delivery type β Information whether the delivery was free or paid for by the customer.
Number of orders β Number of orders completed and in progress from the store system.
Percentage share β Percentage share of a given delivery method in all orders in a given period.
Fee cost β Total costs incurred by customers for a given type of delivery.
Revenue β Revenue excluding VAT from completed and in progress orders.
Media cost β Total costs from connected advertising and affiliation systems.
Number of orders β Total number of orders completed and are being completed in the store system.
GAds cost β Total costs incurred for Google Ads ads.
Meta Ads cost β Total costs incurred for Meta Ads ads.
Tradetracker cost β Total commissions for accepted and completed orders acquired through ads from Tradetracker.
Criteo cost β Total commissions for accepted and completed orders acquired through ads from Criteo.
COS β Cost of sales indicator, calculated as the sum of media costs divided by net revenues from completed and in progress orders.
Source, Medium, Campaign β Data can be passed to Google Analytics in three ways:UTM β Adding
utm_source
, utm_medium
, utm_campaign
parameters to store links.
Google Ads Auto Tagging β Automatically adding UTM parameters to ad URLs.
Referral β Referrer pages that provide the source and medium.
Market β Information about the store or market the product comes from.
Product β Unique product name with variant, assigned to the identifier.
Source β A parameter that specifies where the user’s traffic comes from, e.g. utm_source
.
Medium β A parameter that specifies the advertising medium, e.g. utm_medium
.
Campaign β A parameter that describes the advertising campaign, e.g. utm_campaign
.
Products Viewed β The number of times a product was viewed on different store pages, from Google Analytics.
Products Added to Cart β The number of times a product was added to the cart from Google Analytics.
Products Purchased β The number of times a product was purchased from Google Analytics.
GA Product Revenue β The gross sum of orders excluding shipping costs from Google Analytics, which does not reflect the exact data from the store.
The table presents specific metrics and data for the selected period along with the ability to check the comparison of data to the previous period with information whether the current period is better or worse than the previous one along with a color-coded difference.
Information about the Source, Medium and Campaign can be transferred to Google Analytics in three ways:
- Through UTM parameters, i.e. adding the utm_source, utm_medium, utm_campaign parameters to the store links.
- Through Google Ads automatic tagging – Google Ads automatic tagging is a feature that allows you to track Google Ads campaigns in Google Analytics. This feature automatically adds UTM parameters to the URLs of Google Ads ads. In the case of Google Ads automatic tagging, the medium parameter takes the value “cpc” (i.e. – cost per click) and the Campaign parameter is determined based on the Google Ads campaign from which the user comes. For example, if a user came to a website from a Google Ads ad whose campaign name is “spring_campaign”, the value of the campaign parameter will be “spring_campaign”.
- Through referring pages, so-called referrals, which can pass the source and medium parameters. – When a user enters the store from another page through a link placed on it without UTM parameters, the source will indicate the address of the page from which the user came to the store, and the medium will be indicated as “referral”.
- SourceΒ – A parameter informing about which advertising source or page the user came to the store from. In the case of the source parameter, you can use the UTM parameter called utm_source, which is used to determine the source of traffic. For example, if the utm_source parameter has the value “google”, the source will be “google”.
- MediumΒ – A parameter informing about which advertising medium the user came to the store from. In the case of the medium parameter, you can use the UTM parameter called utm_medium.
- Campaign – A parameter informing about the advertising campaign from which the user came to the store. In the case of the campaign parameter, you can use the UTM parameter called utm_campaign.
- Number of GA purchases – The number of orders regardless of their status that were recorded in Google Analytics as statistical information in accordance with GDPR, consent expressed to cookies and Behavioral Modeling.
- GA revenue – The gross sum of the order value together with the cost of delivery from Google Analytics shows only the sum of orders without verifying the status of these orders and does not present the real sum of orders from the store. This is because Google Analytics is only a statistical tool collecting data from devices that have agreed to cookies or when data is transferred in accordance with GDPR if data transfer to Behavioral Modeling is set correctly. Google Analytics revenue with unknown status will never be equal to store system revenue for orders with order status completed or in progress from store data.
The table presents specific metrics and data for the selected period along with the ability to check the comparison of data to the previous period with information whether the current period is better or worse than the previous one along with a color-coded difference.
Information about the Source, Medium and Campaign can be transferred to Google Analytics in three ways:
- Through UTM parameters, i.e. adding the utm_source, utm_medium, utm_campaign parameters to the store links.
- Through Google Ads automatic tagging – Google Ads automatic tagging is a feature that allows you to track Google Ads campaigns in Google Analytics. This feature automatically adds UTM parameters to the URLs of Google Ads ads. In the case of Google Ads automatic tagging, the medium parameter takes the value “cpc” (i.e. – cost per click) and the Campaign parameter is determined based on the Google Ads campaign from which the user comes. For example, if a user came to a website from a Google Ads ad whose campaign name is “spring_campaign”, the value of the campaign parameter will be “spring_campaign”.
- Through referring pages, so-called referrals, which can pass the source and medium parameters. – When a user enters the store from another page through a link placed on it without UTM parameters, the source will be indicated by the address of the page from which the user came to the store, and the medium will be indicated by the value “referral”.
- MarketΒ – Presents information about the store/market from which the presented product comes and information about it.
- ProductΒ – The unique name of the product with its variant, if any, assigned to the unique identifier. The product name is a pair with the identifier.
- SourceΒ – A parameter informing about the advertising source or page from which the user came to the store. In the case of the source parameter, you can use the UTM parameter called utm_source, which is used to specify the source of traffic. For example, if the utm_source parameter is “google”, then the source will be “google”.
- MediumΒ – A parameter that informs which advertising medium the user came to the store from. In the case of the medium parameter, you can use the UTM parameter called utm_medium.
- CampaignΒ – A parameter that informs about the advertising campaign that the user came to the store from. In the case of the campaign parameter, you can use the UTM parameter called utm_campaign.
- Products ViewedΒ – The number of times products were viewed on category cards, product cards, and in sections presenting products on the store page with Google Analytics. This metric does not only show the view_item event but also products from the view_item_list metric.
- Products added to cartΒ – The number of times a product was added to the cart from Google Analytics.
- Products purchasedΒ – The number of purchases of a given product from Google Analytics.
- Product GA revenueΒ – The gross sum of the order value excluding shipping costs from Google Analytics only shows the sum of orders without verifying the status of these orders and does not present the real sum of orders from the store. This is because Google Analytics is only a statistical tool that collects data from devices that have agreed to cookies or when data is transferred in accordance with the GDPR if data transfer to Modeled Behavioral is set correctly. Google Analytics revenue with an unknown status will never be equal to the revenue from the store system for orders with the order status completed or in progress from store data.
<div><strong>Table</strong> shows key metrics and data comparison to the previous period, with a color-coded highlight of the difference.
<strong>Data source</strong> in Google Analytics can be passed in three ways:
<strong>Via UTM</strong> β Adding <code>utm_source</code>, <code>utm_medium</code>, <code>utm_campaign</code> parameters to store links.
<strong>Google Ads auto tagging</strong> β Adds UTM parameters to Google Ads URLs.
<strong>Referral</strong> β For non-UTM links, the source is the site address and the medium is βreferralβ.
<strong>Source</strong> β Set by <code>utm_source</code>, e.g. βgoogleβ.
<strong>Medium</strong> β Defined by <code>utm_medium</code>.
<strong>Campaign</strong> β Defined by <code>utm_campaign</code>.
<strong>Product Views</strong> β Number of times a product was viewed on a product card from Google Analytics.
<strong>Added to Cart</strong> β Number of times a product was added to a cart from Google Analytics.
<strong>E-commerce Purchases</strong> β Number of purchases recorded in Google Analytics.
<strong>GA Purchase Revenue</strong> β Total gross order value including shipping from Google Analytics, not reflecting exact order totals from the store.</div>
Data source in Google Analytics can be passed in three ways:UTM parameters β Adding
utm_source
, utm_medium
, utm_campaign
parameters to store links.
Google Ads auto tagging β Adds UTM parameters to Google Ads URLs, where the medium parameter is “cpc” and the campaign parameter is determined based on the Google Ads campaign name.
Referral β When a user enters the store from another site without UTM, the source is the site address and the medium is “referral”.
Source β Informs what source the user came to the store from, e.g. utm_source
= “google”.
Medium β Specifies the medium from which the user came, using utm_medium
.
Campaign β Specifies the campaign from which the traffic came, using utm_campaign
.
Conversions β Number of conversions in Google Analytics, it is recommended to mark a purchase as a conversion.
GA Revenue β Total order value recorded in Google Analytics, regardless of order status.
Market β Indicates which store or market the product comes from.
ID β Unique product identifier in the store system.
Product name β Unique product name, including variants, assigned to the identifier.
Net revenue β Information on revenue without VAT, applies to orders completed and in progress.
Number of orders β Number of orders completed and in progress in the store system.
Number of ordered items β Number of ordered items in completed and in progress orders.
Average discount percentage β Percentage difference between the regular price and the purchase price in orders completed and in progress.
Market β Indicates which store or market the product comes from.
ID β Unique product identifier in the store system.
Product name β Unique product name and its variants, assigned to the identifier.
Average discount percentage β Percentage difference between the regular price and the purchase price without additional discounts.
Number of products viewed β Number of “view_item” events from Google Analytics, recorded when the user views the product page.
Number of orders β Number of orders fulfilled and in progress in the store system.
Number of ordered items β Number of ordered items of a given product in orders fulfilled and in progress.
Revenue β Revenue excluding VAT, relating only to orders completed and in progress.
Market β Information about the store or market from which the product comes.
ID β The unique identifier of the product in the store system.
Product name β The unique name of the product, along with its variants, assigned to the identifier.
Net revenue β Revenue excluding VAT, relating only to orders fulfilled and in progress.
Number of products viewed β The number of βview_itemβ events from Google Analytics, recorded when interacting with the product.
Number of adds to cart β The number of βadd_to_cartβ events from Google Analytics, recorded when users add a product to the cart.
Add to cart rate β A metric calculated by dividing the number of times a product is added to a cart by the number of times it is viewed.
Market β Information about the store or market from which the product comes.
ID β A unique product identifier in the store system.
Product name β The name of the product along with its variants, assigned to the identifier.
Price β The current price of the product, as displayed on the product card.
Revenue from the day β Daily revenue from the store system excluding VAT, only for products from orders fulfilled and in progress.
Market β Information about the store or market from which the product comes.
ID β Unique product identifier in the store system.
Product name β Name of the product along with its variants, assigned to the identifier.
Daily date β Price of the product on a given day, as displayed on the product card.
The chart shows Net Revenue only from orders with a discount granted. Net revenue only applies to orders with the status fulfilled and in progress for a given period from the store system.
The chart presents the percentage difference between the regular price of products in the store’s assortment and the price at which the product can be purchased in the store on given days of the period.
- Sales after discountΒ – Information from the store system about revenues without VAT for discounted orders. The presented revenue applies only to orders with the status completed and in progress.
- Number of ordersΒ – The number of all orders with the status completed and in progress from the store system.
- Number of orders with discountsΒ – The number of orders discounted only with the status completed and in progress from the store system.
- Percentage total discountΒ – The percentage difference between the regular price in the product feed and the price at which the products were purchased with additional discounts or coupons.
- Number of orders with couponsΒ – The number of orders in which a discount coupon was used. Orders only with the status fulfilled and in progress from the store system.
- Percentage discount couponsΒ – The percentage difference between the regular price in the product feed and the price at which the products were purchased, only for purchases in which a discount coupon was used.
- Average discount in the feedΒ – The percentage difference between the regular price in the feed and the price at which the product can be purchased in the store without additional discounts or coupons in the selected period.
- SessionsΒ – Number of “session_start” events. A session is the time during which a user, as a unique identifier, interacts with the store. A session starts when a user opens the store page when no session is active (e.g. due to the previous session timeout). By default, a session ends (times out) after 30 minutes of user inactivity. There is no limit to the length of a session.
- Product viewsΒ – Number of “view_item” events. The event should be sent to Google Analytics every time a user opens a product page, changes its variant, size, or color on the product page, or composes a set of products sold under a single product identifier.
- Added to cartΒ – Number of “add_to_cart” events. The event should be sent to Google Analytics every time a user adds a product to the cart through an action, e.g. clicking. Adding a product to the cart in many cases can occur not only from the product page, but also from the category page, section page, or even the home page, or the cart itself by increasing the number of products in the cart.
- Payment startsΒ – Number of “add_payment_info” events. The event should be sent to Google Analytics every time the user selects a payment method through their activity in the purchasing process.
- OrdersΒ – Number of “purchase” events. The event should be sent to Google Analytics once after the order confirmation page is displayed. The number of purchases from Google Analytics only shows the total number of orders without verifying the status of these orders and does not present the real number of orders from the store. This is because Google Analytics is only a statistical tool that collects data from devices that have agreed to cookies or when data is transferred in accordance with the GDPR if data transfer under Modeled Behavioral is set correctly. The number of orders from Google Analytics with unknown status will never be equal to the number of purchases with the order status completed or in progress from the store data.
- Percentage to previousΒ – Information about the percentage of a given step to the immediately preceding step in the funnel.
- Percentage to firstΒ – Information about the percentage of a given step to the first step in the funnel.
- Percentage to periodΒ – Information about the percentage of a given step to the same step in the preceding period.
The table presents data on what events and in what numbers occurred in the store, divided into specific sources, mediums and campaigns of traffic on the site.
Information about the Source, Medium and Campaign can be transferred to Google Analytics in three ways:
- Through UTM parameters, i.e. adding the parameters utm_source, utm_medium, utm_campaign to the store links.
- Through Google Ads automatic tagging – Google Ads automatic tagging is a function that allows you to track Google Ads campaigns in Google Analytics. This function automatically adds UTM parameters to the URLs of Google Ads ads. In the case of Google Ads automatic tagging, the medium parameter takes the value “cpc” (i.e. – cost per click) and the Campaign parameter is determined based on the Google Ads campaign from which the user comes. For example, if a user came to a website from a Google Ads ad whose campaign name is “spring_campaign”, the value of the campaign parameter will be “spring_campaign”.
- Through referring pages, so-called referrals, which can pass the source and medium parameters. – When a user enters the store from another page through a link placed on it without UTM parameters, the source will indicate the address of the page from which the user came to the store, and the medium will be indicated as “referral”.
- SourceΒ – A parameter informing about which advertising source or page the user came to the store from. In the case of the source parameter, you can use the UTM parameter called utm_source, which is used to determine the source of traffic. For example, if the utm_source parameter has the value “google”, the source will be “google”.
- MediumΒ – A parameter informing about which advertising medium the user came to the store from. In the case of the medium parameter, you can use the UTM parameter called utm_medium.
- CampaignΒ – A parameter informing about the advertising campaign from which the user came to the store. In the case of the campaign parameter, you can use the UTM parameter called utm_campaign.
- EventΒ – The name of the event from Google Analytics according to the GA documentation or the custom configuration of triggering events on the store page.
- Number of eventsΒ – The total number of events per event name
Orders Per Day Chart β Presents the number of orders per day for the selected period, divided by customer type.
Store Data β Number of orders from the store systems (from selected markets), applies only to orders completed and in progress.
Customer β Defined by a unique phone number or email address (if no phone) provided during the order.
New Customer β First purchase made to a unique number or email, or a purchase after a break of more than a year since the previous purchase.
Returning Customer β A customer who places another order to the same number or email, if the break between orders does not exceed 365 days.
Second Purchase β Second order placed by the same customer within 365 days.
Chart does not present data from Google Analytics, only full revenue data from the store systems.
Store Data β Net revenue from store systems (from selected markets), applies only to orders completed and in progress.
Customer β Specified by a unique phone number or email address provided during the order.
New Customer β First purchase to a unique number or email, or purchase after a break of more than a year.
Returning Customer β A customer who places another order to the same number or email, if the break between orders does not exceed 365 days.
Second Purchase β Second order placed by the same customer within 365 days.
Note: The chart does not use Google Analytics data, only full revenue data from store systems.
Number of customers β Number of unique phone numbers or email addresses provided during the order.
Net revenue β Revenues excluding VAT from the store system, regarding orders completed and in progress.
Average revenue from the day β Average revenues excluding VAT for a given day of the week, regarding orders completed and in progress. When selecting a period longer than a week, the data is averaged.
Average net basket β Average revenue excluding VAT per order, regarding orders completed and in progress.
Number of orders β Number of orders completed and in progress from the store system. Average number of orders β The average number of orders completed and in progress from the store system, given for the last 7 days. The number changes and is averaged when a longer period is selected.
ID β Unique product identifier in the store system.
Product name β Unique product name and its variants, assigned to the identifier.
Total product revenue β Revenue excluding VAT for the product on a given day, concerning only completed and in-process orders.
Number of orders β Number of completed and in-process orders from the store system.
Number of ordered items β Number of items of a given product ordered in completed and in-process orders.
ID β Unique product identifier in the store system.
Product name β Product name with its variants, assigned to the identifier.
Total product revenue β Revenue excluding VAT from second purchases for the product on a given day, regarding orders completed and in progress.
Number of orders β Number of second orders per user, completed and in progress.
Number of ordered items β Number of product items ordered from second orders, completed and in progress.
Payment method β Types of payment methods available in the store, according to data from the store system.
Number of orders β Number of orders completed and in progress from the store system.
Delivery method β Types of delivery methods available in the store, according to data from the store system.
Delivery type β Information whether the delivery was free or paid for by the customer.
Number of orders β Number of orders completed and in progress from the store system.
Percentage share β Percentage share of a given delivery method in all orders in a given period.
Fee cost β Total costs incurred by customers for a given type of delivery.
Revenue β Revenue excluding VAT from completed and in progress orders.
Your data ready in 1 day! π
Thanks to our proprietary technology, experience and cloud computing, in 1 day you will independently connect your data to DataOrganizer.
You do not need technical knowledge or knowledge of databases. We will guide you through the entire process of launching and connecting information. Without learning technology and without hours spent studying documentation, you will start collecting and reporting your data.
Key benefits of DataOrganizer π
Discover the benefits of fast analytics, automation, better customer understanding, marketing optimization, and full control over store performance.
Analysis and reports
Szybko analizuj dane e-commerce i otrzymuj gotowe raporty i tabele.
Data processing
Process large volumes of data by combining revenues and costs and organize information in the cloud.
Automation and BI
Automate reports and use built-in BI tools.
Customer Habits
Learn about customer habits and analyze product data to make better decisions.
Marketing optimization
Optimize your store marketing and increase sales with Datadiary.
Data history
Build a history of your data while having full control over your store's performance.
Check out the features π―
Data in the Cloud
We use Google Cloud Platform (GCP) to store and process data, ensuring the highest security standards. Data is encrypted and monitored 24/7, which guarantees full control and protection.
AI Chat
Chat AI in DataOrganizer combines data from various e-commerce systems, enabling advanced analysis and optimization of activities. It offers instant insights, integrates advertising expenditure with sales results, measures ROI, enables advanced filtering and sorting of data, and analyzes global market trends.
Any Date Range
DataOrganizer reports support long-term planning and forecasting. By analyzing historical data, companies can better predict future trends and adapt their strategies to changing market conditions.
Advanced Filtering and Sorting
DataOrganizer offers advanced filtering and sorting features that enable precise data management. With these options, you can quickly find and analyze key metrics, customizing data views to your needs.