Updated by Amalie
Migrating from FIAM 1.0 to FIAM 2.0
As part of the migration from FIAM 1.0 to the FIAM 2.0 measurement system, your current UserReport and Kits account will be updated with a new user interface, a new Kits Explorer tool, and a new reporting engine. This means you will keep your current account. Your login credentials, the settings and the statuses in your account will remain the same. There are no implementation changes to scripts or SDKs needed for the migration from 1.0 to 2.0.
In the following, we will go through the details of the migration, what reporting you have available and what if any changes you may have to do as a Publisher.
Media & Sections definitions
Your Media and Section definitions will remain the same in FIAM 2.0 as they were in 1.0.
Media Title & Media Title sections definitions
Your Media Title & Media Title section definitions will remain the same in FIAM 2.0 as they were in 1.0.
Migrating Group definitions
Your Group definitions in FIAM 2.0 will initially be inherited from the Brand ("Network") definitions in FIAM 1.0. After the migration, it will be possible to request new Groups and to make changes to the definitions meaning you can change which Media Titles belong to which Groups.
Migrating publication type and content label definitions
The Publication Types (media categories) and Content Labels (section categories) will not change, but how these are assigned to Media Titles and Media Title Sections will change.
This means that after migration to FIAM 2.0 all publishers will be asked to define publication types and content labels for all Media Titles and Media Title Sections and to do so before the end of this year.
Migrating Kits & Kits API
AudienceProject will migrate the existing Kits user interface and API from the FIAM 1.0 reporting engine to the FIAM 2.0 reporting engine on the migration date. The Kits' user interface, API, and metrics will not change. New metrics and reporting options are only available in the new tool Kits Explorer.
Your account, your credentials, the user interface and the API queries you are currently running will remain the same as they are today to ensure continuous access to data. You will therefore not have to make any changes to access the data via Kits UI or Kits API after the migration;
- After the migration date, you will be able to create reports with reporting periods that start and end after the migration date using the FIAM 2.0 reporting engine.
- You will not be able to create reports with a reporting period that starts before the migration date and ends after the migration date.
Therefore you should make sure that you have no reports or API queries planned where the reporting period crosses over the migration date.
- You will be able to create reports that start and end before the migration date using the FIAM 1.0 reporting engine up until 4 weeks after the migration.
Reporting 'historic data' with start and end dates before the migration date using the FIAM 1.0 methodology will be supported up until 4 weeks after the migration date during which time you should make sure to pull and export all historic reports that you wish to save.
Migration from the Demographic Dashboard to the new Kits Explorer
On the migration date two things will happen in relation to the onboarding to the new reporting tool "Kits Explorer": (1) The data collection will begin and (2) you will get access to the new Explorer tab in the UserReport user interface.
The data collection begins the same day you get access. On the first day of access, you will therefore not see any data in your account.
From the second day after the migration, you will be able to create reports on the data from the first day after the migration. In week 2 after the migration, you will be able to create reports for week 1.
From the new tool, you will have access to the new reporting metrics and you will be able to create reports including not just your own media entities but also the media entities from all of the FIAM publishers.
Changes to reporting or validation status
If you detect an issue with the measurement of your site or app, and want to make changes to the reporting or validation status of your site, not that during the migration (between november 24th and december 1st) you must make those changes both in the FIAM 1.0 system (using your communication sheet to update reporting status) and in FIAM 2.0 (using this guide to invalidate/ validate your track point)