Before diving into listing out the metrics and dimensions available on Google Search Console; it is necessary to understand the structure of data, since this is a unique data source.

Levels

Typically in an advertising channel on Clarisights, we have different levels of data; and attributes at each level together making up the set of dimensions. For e.g. in Google Ads; the levels would be Account, Campaign, Ad Group, Ad and Keyword. Plus, at each level, there would be multiple attributes like Campaign Type, Keyword Match Type, etc. However, in GSC, there are only two levels - Account and "Object". Object is essentially a placeholder generic name, since all the dimensions of GSC such as Query, Page, Search Type etc. are stored at the same level.

This is the first point to note - There are only two levels in GSC data, Account and Object; and all of the dimensions such as page, query, device etc are stored at the Object level.

Object Structure

In Clarisights, all metrics are stored against entities we call as "objects" (not directly related to the Object level above). Each value at a given level constitutes one "object". For example, each distinct campaign in Facebook is an object at campaign level; each distinct Ad Group in Google Ads is an object at Ad Group level, etc. When you look at data for a group of objects - for e.g. looking at a dimension "Country" defined at campaign level - you are essentially looking at the aggregate data in all the objects (in this case, campaigns) that have been tagged with each Country.

With regards to GSC, as we see in the first point above, all objects are stored at the Object level. However, all of these objects do not have the same structure. GSC allows us to pull data for both individual dimensions (page, query, device, etc) and also multiple combinations of these dimensions. For example, we have separate data pulls for -

query
page
device
query & page
together
page & device
together
page & device & query
together
etc.

What that means, is that an object in GSC could correspond to just a query; just a page; or a combination of page & query; or any one of 47 different combinations.

This is the second point to note - The objects in GSC are composed of either individual dimensions, or various combinations of them.

Data Aggregation

The accuracy of the data in GSC changes with the number of dimensions that are being requested in the data pull. For e.g., requesting data for only device versus requesting data of device & page together will yield different aggregate values for each device. Google has an official mention of this, you can find it here under the section 'Why do I lose data when asking for more detail?'.

What this means for you is that the total value of say Impressions that you see for device would be different from the value you see if you were looking at both device and page together in a visualization. So, in order to show you the most accurate value possible, when you request data for an individual dimension like device; we aggregate the data of all objects where only device is present. This ensures that the detail lost when other dimensions are involved with device does not affect the true aggregate data of device.

This is the third point to note - Depending on the dimensions you choose in a visualization, we aggregate data of only those objects which exactly match that combination of dimensions - in order to minimize loss of data.

Those are broadly the specific nuances involved with GSC data.

Metrics

The following metrics are available in GSC on Clarisights - 

  1. GSC: Impressions - Count of views on a search result from your site in the SERP.

  2. GSC: Clicks - Count of clicks on a search result from your site in the SERP.

  3. GSC: CTR - Click-through rate, calculated from the impressions and clicks.

  4. GSC: Avg. Position - The avg. rank of a search result from your site in the SERP.

Dimensions

The following dimensions are available in GSC on Clarisights -

Account Level

  1. Account - This corresponds to your web or mobile site. It is represented as a URL.

Object Level

  1. Search Type - One among web, image or video - the kind of search that users can perform to see a SERP.

  2. Country - The countries from which the searches that were made showed your site in the SERP. This is represented as a 3 letter country code.

  3. Device - One among Desktop, Mobile or Tablet - specifies the device from which the search queries originated.

  4. Page - The pages in your site that were displayed in the SERP and users correspondingly landed on, when they clicked the result.

  5. Query - Search queries that resulted in impressions for your site in a SERP.

Data Filtering

To ensure you are only looking at meaningful data, the Clarisights platform automatically filters out data on a few parameters.

  1. Clicks > 0 - Any object (as described above) that has 0 clicks on any given day is filtered out completely.

  2. Clicks < 50 - All queries that have less than 50 clicks in any given whole month are aggregated together in one query called Clicks less than 50. Note that a query might have been dissolved into this in one month if it has less than 50 clicks in that month; but might be intact in a different month if it has more than 50 clicks in that respective month. In an ongoing month, this aggregation is updated every day - for e.g. if the ongoing month is January - a query might be part of this bucket until the 15th if its clicks were less than 50 then; and subsequently become an independent query if the clicks increased to above 50 by the 16th.

  3. Country - If you have separate Google Search Console accounts with country-specific domains, and don't need the Country dimension, we can exclude this from our data pulls - reducing the volume of data significantly and making your reports quite a bit faster.

  4. Search Type - If you have majority of your traffic coming in from web search and see negligible traffic from image search or video search; we can restrict our data pulls to web-only - reducing the volume of data significantly and making your reports quite a bit faster.

Did this answer your question?