Metrics and dimensions in R7K12¶
Metrics are quantitative values. The Visits (sessions) metric is the total number of visits (sessions). Dimensions are data attributes. For example, the City dimension shows which city the user was in during the session, and the Device type dimension contains the type of device used for the visit. In R7K12 reports, each dimension value corresponds to a specific row, and each metric corresponds to a column.
Metrics¶
Table 1 - Terms and descriptions of metrics in R7K12
| Metric | Description | Comments |
| Visits | Number of site visits. | |
| New users | Number of new users. | Visitors (their devices - PC, smartphone, etc.) who came to your site for the first time. |
| Time on site | Time the user spent on the site. | |
| Average time on site | Average time on site = Time on site / Number of visits | |
| Events | Number of events sent. | |
| Pageviews | Number of site pageviews. | |
| JavaScript errors | Number of JavaScript errors. | |
| 404 errors | Number of 404 errors. | |
| Cost (unattributed) | Marketing costs. | |
| Cost | Cost distributed across higher-level campaigns that have visits. | In some cases, ad platforms do not provide full statistics for ads. In that case, the following happens: cost is allocated by UTM tags. First, utm-term values are matched; if there are no visits there, matching is done by utm-content, and so on up to utm-medium. |
| Inquiries | All types of user interactions with the site that require a response. | This is any client call, request from the site, or email. This inquiry is not yet in the CRM |
| Requests (Qualified requests) | Requests (leads) are any qualified inquiries your business received. For example: submitted forms on the site, calls, online chat conversations, etc. | A request is a deal that has entered the status group: - “In progress”; - “Completed”; - “Canceled”. If a request leaves these statuses, it is no longer counted as a request. |
| Deals | Deals - the number of deals created in your CRM system. | Deals can have different statuses. These statuses are divided into groups: “Not counted”, “In progress”, “Completed”, “Canceled”. |
| Contacts | Contacts - the number of contacts created in your CRM system. | If a person contacts you for the first time (there is no such contact information in the CRM database), we create a contact and create a deal for it. |
| Revenue | Amount received from deals in the “Completed” status. | |
| Revenue from canceled requests | Revenue from requests with “Canceled” statuses. | |
| Absolute conversion rate | Absolute conversion rate = Sales / Visits * 100% | |
| Request conversion rate | Request conversion rate = Requests / Visits * 100% | |
| Sales conversion rate | Share of sales out of the total number of requests Sales / Requests * 100% | |
| Margin, % | Margin,% = (Profit / Cost of goods) * 100% | |
| Canceled requests | Requests with the “Canceled” status. | |
| Potential revenue | Amount from deals in “In progress” statuses. | |
| Forecast revenue | Revenue from requests with “Completed” and “In progress” statuses | |
| Forecast profit | Maximum possible profit from requests with “Completed” and “In progress” statuses | |
| Forecast sales | Requests with “Completed” and “In progress” statuses. | |
| Forecast average order value | Potential average order value = Forecast revenue / Forecast sales | |
| Profit | Profit = Revenue - Cost of goods | |
| Sales | Requests with the “Completed” status. | |
| Net profit | Net profit = Profit - Cost | |
| Cost of goods | The cost of goods for a request can be set in the “Settings” section or imported from the CRM. | |
| Average time on site | Average time users spend on the site. | |
| Pages per visit | Number of pages a user viewed per visit. | |
| Ad spend share, % (share of advertising costs) | Ad spend share = (Cost / Profit) * 100% | |
| Forecast CPO | Forecast CPO = Cost / Forecast sales | |
| Forecast ROI | Forecast ROI = (Forecast profit - Cost) / Cost * 100% | |
| Average order value | Average order value = Revenue / Sales | |
| ROI | ROI = (Profit - Cost) / Cost * 100% | |
| ROMI | ROMI = (Revenue - Cost) / Cost * 100% | |
| Average profit | Average profit = Profit / Sales | |
| CPC (Cost per Click) | CPC = Cost / Visits | |
| CPL | CPL = Cost / Requests | |
| CPO (Cost per order) | CPO = Cost / Sales | |
| CTR (Click-through rate) | CTR = Visits / Impressions * 100% | |
| Cost per visit | Cost of one visit = Cost / Visits | |
| Inquiry conversion rate | Inquiry conversion rate = Inquiries / Visits * 100% | |
| Inquiry-to-request conversion rate | Inquiry-to-request conversion rate = Requests / Inquiries * 100% | |
| Clicks | Number of ad clicks. | |
| Impressions | Number of ad impressions. | |
| Bounce rate | Number of bounces / number of Visits * 100% | |
| Cost per inquiry | Cost per inquiry = Cost / Inquiries | |
| Revenue from canceled requests | Revenue from deals in the “Canceled” status | |
| Number of payments | Number of payments for the selected time interval | |
| Canceled payment amount | Amount of canceled payments for the selected time interval | |
| Number of canceled payments | Number of canceled payments for the selected time interval | |
| Confirmed payment amount | Amount of confirmed payments for the selected time interval | |
| Number of confirmed payments | Number of confirmed payments for the selected time interval |
Dimensions¶
Table 2 - Terms and descriptions of dimensions in R7K12
| Metric | Description | Comments |
| Visit ID | Unique visit number. | |
| Client ID | Unique client number (a client can make several unique visits). | |
| Google Analytics client ID | A unique random ID called client id, which is created by the Google Analytics tracking code and sent to the Google Analytics server. | |
| Yandex.Metrica client ID | A unique random ID called client id, which is created by the Yandex Metrica tracking code and sent to the Yandex Metrica server. | |
| User ID | If the site has authorization, you can pass the user ID | |
| Client IP address | Client IP address. | |
| Visit number | Sequential visit number for the same user. | |
| Visit start date/time | Date and time the visit started. | |
| Visit end date/time | Date and time the visit ended. | |
| Visit date | Visit date. | |
| Year | Year the visit started | |
| Month | Month the visit started | |
| Day of month | Day of the month the visit started | |
| Day of week | Day of the week the visit started | |
| Hour | Hour the visit started | |
| Minute | Minute the visit started | |
| Second | Second the visit started | |
| Page URL | Full URL of the page the user visited. | |
| Domain | Domain where the visit took place | |
| Landing page | Landing page. | |
| Query parameters | Everything after "?" in the URL. | |
| Request hash | Everything after "#" in the URL. | |
| Source (UTM) | Ad platform (utm_source). | |
| Medium (UTM) | Traffic type (utm_medium). | |
| Campaign (UTM) | Ad campaign (utm_campaign). | |
| Content (UTM) | Information that helps distinguish ads when other parameters match (utm_content). | |
| Keyword (UTM) | Keyword that triggered the ad (utm_term). | |
| Has UTM tags | Boolean metric: whether UTM tags are present - “Yes”/”No”. | |
| Source group name | - | |
| Source name | Traffic source name | For example: Yandex Direct, Google AdWords, Direct visit, etc. |
| Source (level 1) | Source (source) | |
| Source (level 2) | Medium (medium) | |
| Source (level 3) | Campaign (campaign) | |
| Source (level 4) | Ad content (content) | |
| Source (level 5) | Keyword (term) | |
| Source (level 6) | - | |
| Source (level 7) | - | |
| Google AdWords ClickId | Google click ID. | When a user clicks an ad, the auto-tagging feature adds a parameter to the landing page URL: gclid. |
| Direct visit | Boolean metric: whether the visit was a direct visit - “Yes”/”No”. | |
| Bot | Boolean metric: whether the visit was made by a bot - “Yes”/”No”. | |
| Offline visit | Boolean metric: whether the visit was offline - “Yes”/”No”. | Offline visit - an inquiry to the company without visiting the site |
| Device | Type of device used to visit the site. | |
| Browser | Name of the browser used for the visit. | |
| Browser version | Version of the browser used for the visit. | |
| Operating system | Operating system of the device used for the visit. | |
| Operating system version | Operating system version of the device used for the visit. | |
| City | City the visit came from. | |
| Region | Region the visit came from. | |
| Country | Country the visit came from. | |
| Deal ID | Unique deal number | |
| Inquiry type | This dimension determines where the inquiry came from - its type. | Inquiry type divides inquiries into requests from site forms, calls from call tracking, callback requests, etc. |
| Deal status | Deal (order) status in the CRM system | |
| Deal status group | The deal status group assigned to deal statuses from the CRM | There are 4 deal status groups in total: “Not counted”, “In progress”, “Completed”, “Canceled”. |
| Inquiry page URL | URL of the page the inquiry came from | |
| Inquiry page domain | Domain of the page the inquiry came from | |
| Inquiry page path | Path of the page the inquiry came from | |
| Deal name | Deal name in the CRM system | |
| Manager ID | Unique manager number | |
| Manager name | Manager's name in the CRM system (full name) | |
| Contact phone | Client (contact) phone number in the CRM system | |
| Contact email | Client (contact) email in the CRM system | |
| Contact name | Full name of the client (contact) in the CRM system | |
| Store | ||
| Parameter #1 | - | |
| Parameter #2 | - | |
| Parameter #3 | - | |
| Parameter #4 | - | |
| Parameter #5 | - |