In this article, we will introduce you to all the entities available in the Myposeo connector of Looker Studio. You will learn, from now on, how to use them in detail.

When you create a data source from the Domain entity, you will get global data from the website tracked (domain, sub-domain, url...), the highest level of granularity.

💡What you need to know: this entity allows you to display global data.

Depending on the project (Simple, Competitive or Full) that you synchronise in the connector, you will have a slightly different interface, in the Filters, with the addition or removal of some fields to fill in.

Completing the Filters fields is not mandatory. The method you choose for data retrieval will determine the outcome.

By incorporating filters into your configuration, you can optimise data loading and enhance the speed of data retrieval. This approach enables you to reduce the amount of data being loaded while still achieving faster access to the specific data you need.

💡 In the creation of the data source, if you want to take into account all the elements present in each Filters (Keyword groups, Level groups, Positions, Traffic sources, Type of results, Brand/Non-Brand...) then you will have to leave the field EMPTY + tick the CHECKBOX.

You can take some inspiration from the One Pager and the Domain Overview created from our "template".

When generating a data source using the Keyword Groups entity, the data will be computed based on the categories that have been established.

💡What you need to know: this entity allows you to display data at the level of your Keyword Groups.

❌ BE CAREFUL, IT IS DIFFERENT FROM THE DOMAIN ENTITY:
​
As an example, to obtain the website traffic data, you should avoid adding up the traffic from the Keyword Groups. This total is likely to be higher than the Domain entity's traffic since keywords may appear in multiple categories, leading to duplications.

Depending on the project (Simple, Competitive or Full) that you synchronise in the connector, you will have a slightly different interface with the addition or removal of some fields to fill in.

Completing the Filters fields is not mandatory. The method you choose for data retrieval will determine the outcome.

By incorporating filters into your configuration, you can optimise data loading and enhance the speed of data retrieval. This approach enables you to reduce the amount of data being loaded while still achieving faster access to the specific data you need.

💡 In the creation of the data source, if you want to take into account all the elements present in each Filters (Keyword groups, Level groups, Positions, Traffic sources, Type of results, Brand/Non-Brand...) then you will have to leave the field EMPTY + tick the CHECKBOX.

You can take some inspiration from the Keywords Groups created from our "template".

When you create a data source from the Keywords entity, the data will be calculated at the lowest level of granularity, which is your keywords.

💡What you need to know: This entity allows you to display data at the keyword level.

Depending on the project (Simple, Competitive or Full) that you synchronise in the connector, you will have a slightly different interface with the addition or removal of some fields to fill in.

Completing the Filters fields is not mandatory. The method you choose for data retrieval will determine the outcome.

By incorporating filters into your configuration, you can optimise data loading and enhance the speed of data retrieval. This approach enables you to reduce the amount of data being loaded while still achieving faster access to the specific data you need.

💡 In the creation of the data source, if you want to take into account all the elements present in each Filters (Keyword groups, Level groups, Positions, Traffic sources, Type of results, Brand/Non-Brand...) then you will have to leave the field EMPTY + tick the CHECKBOX.

In this scenario, I've implemented three filters to enhance the information available in my keywords table. But they are not necessary (optional).

You can take some inspiration from the Keywords created from our "template".

When you create a data source from the Page Groups entity, you will be able to display data by page segment. The idea is to categorise your pages and retrieve statistics by page tags such as urls folders.

💡What you need to know: This entity allows you to understand how your page segments are performing by allowing you to have statistics by page groups.

❌ BE CAREFUL, IT IS DIFFERENT FROM THE PAGES ENTITY:

The page entity only gives you access to statistics per page and not per group of several pages.

Depending on the project (Simple, Competitive or Full) that you synchronise in the connector, you will have a slightly different interface with the addition or removal of some fields to fill in.

Completing the Filters fields is not mandatory. The method you choose for data retrieval will determine the outcome.

By incorporating filters into your configuration, you can optimise data loading and enhance the speed of data retrieval. This approach enables you to reduce the amount of data being loaded while still achieving faster access to the specific data you need.

💡 In the creation of the data source, if you want to take into account all the elements present in each Filters (Keyword groups, Level groups, Positions, Traffic sources, Type of results, Brand/Non-Brand...) then you will have to leave the field EMPTY + tick the CHECKBOX.

You can take some inspiration from the Page Groups created from our "template".

When you create a data source from the Pages entity, you will have data and statistics available at page/url level.

💡What you need to know: This entity allows you to display data at the page level and get all their performances.

❌ BE CAREFUL, IT IS DIFFERENT FROM THE PAGES GROUPS ENTITY:

The Pages entity only gives you access to statistics per page and not per groups of several pages.

Depending on the project (Simple, Competitive or Full) that you synchronise in the connector, you will have a slightly different interface with the addition or removal of some fields to fill in.

Completing the Filters fields is not mandatory. The method you choose for data retrieval will determine the outcome.

By incorporating filters into your configuration, you can optimise data loading and enhance the speed of data retrieval. This approach enables you to reduce the amount of data being loaded while still achieving faster access to the specific data you need.

💡 In the creation of the data source, if you want to take into account all the elements present in each Filters (Keyword groups, Level groups, Positions, Traffic sources, Type of results, Brand/Non-Brand...) then you will have to leave the field EMPTY + tick the CHECKBOX.

In this scenario, I've implemented two filters to enhance the information available in my keywords table. But they are not necessary (optional).

You can take some inspiration from the Pages created from our "template".

When you create a data source from the Competitors entity, you will be able to display the data available in the Market Overview tab of your performance tracking.

💡What you need to know: This entity provides you with insights into how your competitors are performing based on a sample of data.
​

For a smoother data recovery process, it's advisable to opt for a one-day retrieval period instead of a whole month.

❌ BE CAREFUL, IT IS DIFFERENT WITH WEBSITES THAT YOU INTENTIONALLY ADD TO YOUR TRACKING:

The websites tracked will have the benefit of being analysed as your own domain. You will be able to study the performance of your chosen competitors.

In contrast, in the market overview, these are all the websites found when we have collected the positions of all your keywords over a page depth of 1 to 10. This is only a sample of your competitive environment.

This entity provides you with a trend analysis and empowers you to recognise competitors within your market.

Depending on the project (Simple, Competitive or Full) that you synchronise in the connector, you will have a slightly different interface with the addition or removal of some fields to fill in.

Completing the Filters fields is not mandatory. The method you choose for data retrieval will determine the outcome.

By incorporating filters into your configuration, you can optimise data loading and enhance the speed of data retrieval. This approach enables you to reduce the amount of data being loaded while still achieving faster access to the specific data you need.

💡 In the creation of the data source, if you want to take into account all the elements present in each Filters (Keyword groups, Level groups, Positions, Traffic sources, Type of results, Brand/Non-Brand...) then you will have to leave the field EMPTY + tick the CHECKBOX.

You can take some inspiration from the Market Overview created from our "template".

For more information, you can always read our latest updates about the Looker Studio connector.