Skip to main content
All CollectionsJ+ Search & Looker Studio
Looker Studio tutorial ๐Ÿš€
Looker Studio tutorial ๐Ÿš€

Display data from Myposeo in Google Data Studio through Connectors.

Thomas Hรฉnault avatar
Written by Thomas Hรฉnault
Updated over a month ago

This tutorial enables you to synchronise a tracking campaign and display the data directly in Google Data Studio.

Contents:

In this article you will learn how to synchronise Myposeo data in Google Data Studio. Overview includes:

How to synchronise Myposeo data in Google Data Studio?

The first step is to synchronise your Myposeo account with Google Data Studio.

1. Within your Myposeo account

First step, retrieve your API Key, available via your configuration page https://account.myposeo.com/account/configuration/api

2. In your Google Data Studio account

You must create a data source by clicking on the CREATE button.


To do this, you will need to add the Myposeo connector, among the list of connectors tools available. In order to simplify your search, we advise you to use the search bar provided (see image).

Once you have added the Myposeo connector, you need to fill in your API Key, previously retrieved from your Myposeo account.

Before submitting your API key to Google Data Studio, we strongly recommend that you rename your data source to make it easier to find (example: MYP - Site Entity (daily) - Project Name).

At this stage, your synchronisation with Google Data Studio is theoretically done. To display your first data in the interface you will now have to setup a data source.
The next steps are as follows;

How to create Myposeo data sources in Google Data Studio?

1. Select the entity from which you wish to collect data (site, keyword groups, keywords, detailed keywords, competitors, page tags, pages...).

2. Select the language (French or English) of the Myposeo indicators.

3. Choose the aggregation (day, week or month) on which you wish to display your data. Everything will depend on the expected result in your dataviz (choice of charts...). Be aware that this parameter is linked to the calendar that you find in the Myposeo interface (see image below).

Goal in your dashboard

Myposeo project frequency

GDS connector aggregation

I want to display Daily data.

Daily

I want to display weekly data

Weekly

I want to display monthly data

Monthly

Example: If you want to display data at the month level (January to December) then you will have to choose the month aggregation. Not the day or week aggregation, as the data calculations will be different and you will not have similar data.

4. You then need to select the Myposeo campaign (id) from which you want to collect the data (all your projects are listed automatically), retrieve the best positions or all positions and finally the website(s) to display.

5. If you need to display the data for your domain and those of your competitors, then we invite you to select more than one and to tick the checkbox to be able to display the data of different domains at the same time.

6. You can also breakdown your data by keyword groups. Please note that if you leave this field empty, then all keyword groups will be taken into account by default.

7.

  • If you are synchronising a Simple or Competitive project:

    • There is no need to use the Positions parameter as it only applies to the full project.

  • If you are synchronising a Full project:

    • Then you will have the possibility to select the Positions parameter to be able to split your data by Block position, Type position and/or with your Absolute position (Position).

Then click on "Connect".

Once the data source is created, you have two choices:

  • Either create a report

  • Or go back to the main interface of Google Data Studio and continue to create other Myposeo data sources. This step can allow you to use our Google Data Studio template. We will see together how to reuse our template with your own Myposeo data.

How to duplicate our Google Data Studio template?

NOTE: This template was built on a daily basis campaign.

If your campaign collects data once a week, then the data sources to create afterwards will have to be aggregated on a weekly basis and not on a daily basis.
As for the monthly data sources, this does not change.

Example :
โ€‹MYP - Site Entity (daily) - DEMO SOURCE > MYP - Site Entity (week) - DEMO SOURCE


As a preamble, you need to create several data sources, as follows:

1. Site Entity

Example :

  • MYP - Site Entity (daily) - DEMO SOURCE

  • MYP - Site Entity (month) - DEMO SOURCE

Field to fill

Site Entity (daily)

Site Entity (month)

Entity

Site

Site

Language

English

English

Aggregate by

Day

Month

Campaign

id campaign

id campaign

Source

Best position

Best position

Site

my website + competitors

my website + competitors

Site parameter (checkbox)

Allow

Allow

Keyword Groups*(checkbox)

Allow

Allow

Positions

To activate if the campaign id is a Full Project

To activate if the campaign id is a Full Project

Positions parameter (checkbox)

Allow if Full Project

Allow if Full Project

*In the creation of the data source, if you wish to take into account all the Keyword Groups, then you must leave the "Keyword Groups" field EMPTY.

2. Keywords Groups Entity

Example :

  • MYP - Keywords Groups Entity (daily) - DEMO SOURCE

  • MYP - Keywords Groups Entity (month) - DEMO SOURCE

Field to fill

Keywords Groups Entity (daily)

Keywords Groups Entity (month)

Entity

Keywords Groups

Keywords Groups

Language

English

English

Aggregate by

Day

Month

Campaign

id campaign

id campaign

Source

Best position

Best position

Site

my website + competitors

my website + competitors

Site parameter (checkbox)

Allow

Allow

Keyword Groups*(checkbox)

Allow

Allow

Positions

To activate if the campaign id is a Full Project

To activate if the campaign id is a Full Project

Positions parameter (checkbox)

Allow if Full Project

Allow if Full Project

*In the creation of the data source, if you wish to take into account all the Keyword Groups, then you must leave the "Keyword Groups" field EMPTY.

3. Keywords Entity

Example :

  • MYP - Keywords Entity (daily) - DEMO SOURCE

  • MYP - Keywords Entity (month) - DEMO SOURCE

Field to fill

Keywords Entity (daily)

Keywords Entity (month)

Entity

Keywords

Keywords

Language

English

English

Aggregate by

Day

Month

Date dimension

Yes

Yes

Campaign

id campaign

id campaign

Site

my website + competitors

my website + competitors

Site parameter (checkbox)

Allow

Allow

Keyword Groups*(checkbox)

Allow

Allow

Positions

To activate if the campaign id is a Full Project

To activate if the campaign id is a Full Project

Positions parameter (checkbox)

Allow if Full Project

Allow if Full Project

*In the creation of the data source, if you wish to take into account all the Keyword Groups, then you must leave the "Keyword Groups" field EMPTY.

4. Pages Tags Entity

Example :

  • MYP - Page Tags Entity (daily) - DEMO SOURCE

  • MYP - Page Tags Entity (month) - DEMO SOURCE

Field to fill

Pages Tags Entity (daily)

Pages Tags Entity (month)

Entity

Page Tags

Page Tags

Language

English

English

Aggregate by

Day

Month

Campaign

id campaign

id campaign

Site

my website + competitors

my website + competitors

Site parameter (checkbox)

Allow

Allow

5. Pages Entity

Example :

  • MYP - Pages Entity (month) - DEMO SOURCE

Field to fill

Pages Entity (month)

Entity

Pages

Language

English

Aggregate by

Month

Date dimension

Yes

Campaign

id campaign

Site

my website + competitors

Site parameter (checkbox)

Allow

Keyword Groups*

Empty

Keyword Groups parameter (checkbox)

Allow

Positions

To activate if the campaign id is a Full Project

Positions parameter (checkbox)

Allow if Full Project

*In the creation of the data source, if you wish to take into account all the Keyword Groups, then you must leave the "Keyword Groups" field EMPTY.

6. Site (competitors) Entity

Example :

  • MYP - Site (competitors) Entity (daily) - DEMO SOURCE

  • MYP - Site (competitors) Entity (month) - DEMO SOURCE

Field to fill

Site (competitors) Entity (daily)

Site (competitors) Entity (month)

Entity

Site

Site

Language

English

English

Aggregate by

Day

Month

Date dimension

Yes

Yes

Campaign

id campaign

id campaign

Site

my website + competitors

my website + competitors

Site parameter (checkbox)

Allow

Allow

Keyword Groups*

Empty

Empty

Keyword Groups (checkbox)

Allow

Allow

Positions

To activate if the campaign id is a Full Project

To activate if the campaign id is a Full Project

Positions parameter (checkbox)

Allow if Full Project

Allow if Full Project

*In the creation of the data source, if you wish to take into account all the Keyword Groups, then you must leave the "Keyword Groups" field EMPTY.

Once you have created all of them, you will have to go to our Google Data Studio template by clicking on this link.

On the interface, you will have to make a copy of our template...


By duplicating the template you will not have access to the original data sources (Unknown).
โ€‹
This will not allow you to sort your data sources in the right order. Yes the order of the data sources have an importance in the display of the data afterwards.


To fix this, please add them in this exact order:

  • MYP - Site Entity (month) - DEMO SOURCE

  • MYP - Site Entity (daily) - DEMO SOURCE

  • MYP - Site (competitors) Entity (daily) - DEMO SOURCE

  • MYP - Keywords Groups Entity (daily) - DEMO SOURCE

  • MYP - Keywords Groups Entity (month) - DEMO SOURCE

  • MYP - Keywords Entity (month) - DEMO SOURCE

  • MYP - Keywords Entity (daily) - DEMO SOURCE

  • MYP - Page Tags Entity (month) - DEMO SOURCE

  • MYP - Page Tags Entity (daily) - DEMO SOURCE

  • MYP - Pages Entity (month) - DEMO SOURCE

  • MYP - Site (competitors) Entity (month) - DEMO SOURCE


...then you will have to click on the "Create Report" button

Once the copy of the report is done, don't hesitate to check your graphs, dimensions, metrics as well as the parameters Site, Keyword Groups... to detect any anomaly.

Did this answer your question?