Migrate your data from Piano Analytics


This connector will allow you to re-import your aggregated data history for certain types of reports.


To be as complete as possible, the data requested and synchronized via the connector is in ECO: OFF mode. If you wish to make comparisons, it is imperative to be in the same ECO: OFF mode, otherwise you will see larger differences.


How do I set up data re-import?

In order to set up data re-import, you must:
  • have the API enabled on your Piano Analytics account
  • Create  API access  in your Piano interface
  • Retrieve the two values: ACCESS KEY (access key) and SECRET KEY (secret key)
  • Retrieve the siteId you wish to synchronize; this value corresponds to the ID of the site containing the data to be synchronized.
Once API access is enabled, log in to the Eulerian interface and activate the Piano Analytics Import data re-import connector.

When creating the data re-import connector, an API access check for the target siteId is performed by querying the total number of visits from January 1, 2021, to the connector creation date (but no later than March 16, 2023). This is done to avoid creating connectors that:
  • cannot access the API due to an API credentials issue
  • cannot synchronize an empty site


Data discrepancy with Data Query

We have observed that discrepancies can exist between visit volumes and unique visitors over certain periods; the data visible after re-import comes from Piano API. In some cases, this may differ from what is displayed in the Data Query interface. Unfortunately, we cannot make corrections at this level.


Global site-level data

The following metrics:
  • visits
  • page views
  • unique visitors
  • time past
  • bounce rate
  • visits to a page
The data can be segmented by device type.


Page-level data

The following metrics:
  • page views
  • bounce rate
  • time past
  • visits
  • visits to a page
  • incoming visits
The following additional dimensions are automatically imported and associated with the imported page:
  • Page - 1st level (page_chapter1) becomes Page Label 1
  • Page - 2nd level (page_chapter2) becomes Page Label 2
  • Page - 3rd level (page_chapter3) becomes Page Label 3
  • The URL of the page, if available, is also retrieved and associated with the relevant page.
The data can be segmented by device type.



Overall data by free traffic source

This concerns the following sources:
  • direct access
  • affiliate sites including Portals & Webmails
  • free social networks
  • SEO / search engine optimization
The following metrics:
  • visits
  • page views
  • unique visitors
  • time past
  • bounce rate
  • visits to a page
The data can be segmented by device type.
The following sources are treated with special care:
  • Portals: a 'Portals' referrer is created, grouping the available Portal sites as a source; the URL of the referring site will be found as a sub-element of the main 'Portals' referrer.
  • Webmails: a 'Webmails' referrer is created, grouping the available webmails as a source; the URL of the referring site will be found as a sub-element of the main 'Webmails' referrer.
Keyword-level data for the Natural Referencing source is not available.


Overall data by paid traffic source

This concerns the following sources:
  • Sponsored links
  • push notifications → classified as Generic channel
  • advertisement → classified as channelage Display
  • unclassified campaigns → classified as Display channelage
The following metrics:
  • visits
  • page views
  • unique visitors
  • time past
  • bounce rate
  • visits to a page
The data can be segmented by device type. We create one campaign per medium, so the same campaign name may be duplicated per medium; it is then sufficient to create a higher grouping to find its aggregates.

If you have specific channels to re-import that are not listed above, please contact us.


Global data at the geographical level

We retrieve the data at the following level:
  • country
  • region
  • city

A repository based on ISO codes is not available; therefore, the re-import relies on approximations related to country, region, and city names. Consequently, it is possible that we may not be able to achieve the exact same level of detail despite our best efforts. The following metrics are used:
  • visits
  • page views
  • unique visitors
The data can be segmented by device type.


Global event-level data


Since the taxonomy of click events is not standardized, we can only offer limited synchronization. Data is transferred within the concept of conversion tracking . The event names are cleaned up.
  • removing https:/ from the beginning of the name
  • removal of / at the beginning of the name
The following metrics:
  • clicks
The data can be segmented by device type.


Errors



Creating the connector

When creating the connector, if you get this message
This means the connection information you provided is incorrect. When creating the connector, we test access to the Piano API to ensure it's working. If you receive this error, it means the connection information you provided is invalid. Solution : Please contact Piano support so they can test it on their end. The test we perform to query the API and the associated permissions is as follows:
 So if you have the following parameters:
curl -v -H 'Content-Type: application/json' -X POST -H 'x-api-key: accesskey_secretkey' --data '{"columns":["m_visits"],"max-results":1,"period":{"p1":[{"end":"2023-02-28","start":"2021-01-01","type":"D"}]},"space":{"s":[siteId]},"page-num":1,"sort":["-m_visits"]}' https://api.atinternet.io/v3/data/getData

  • accessKey: 321656894d
  • secretKey: 65465sdfds8sdf32268sdf454g
  • siteId: 5623
You will receive the call:
curl -v -H 'Content-Type: application/json' -X POST -H 'x-api-key: 321656894d_65465sdfds8sdf32268sdf454g' --data '{"columns":["m_visits"],"max-results":1,"period":{"p1":[{"end":"2023-02-28","start":"2021-01-01","type":"D"}]},"space":{"s":[5623]},"page-num":1,"sort":["-m_visits"]}' https://api.atinternet.io/v3/data/getData