The Analytics Suite is at a major turning point in its history. A brand new data model is available in the new Data Query 3, now available in beta. And it will soon be available everywhere in our interfaces.
❓ Wha is the Data Model?
The data model is the way we store your data. Now it is common to all your sites and applications within your organization to make it easier for you to manage and use data.
Standard properties and custom
Each event can benefit from all the properties of your data model. The term "properties" replaces the term "dimensions".
What the Data Model looks like?
The new data model should be seen as a matrix, where the site is only one of many properties:
- in blue: the specific properties of the event, namely the timestamp and its label,
- in grey: the properties of the standard AT Internet data model (OS, Geolocation, page tree, Sales Insights product properties, etc.)
- in yellow: the additional properties you can create. These properties can be used on all types of events, standard or customized.
❓ What are the main advantages of the Data Model?
- Optimized query performance,
- On-the-Fly Unique Visitors and Unique Identified Visitors,
- Custom metrics and Global Segments (usable on all sites, regardless of properties and metrics used),
- Multi-site analyses without constraints (including segmented),
- Crossing properties without constraint,
- We are keeping a few surprises!
❓ How to manage the Data Model ?
We are in a transition phase towards full management of this data model, so there are currently two scenarios. The first is the creation of properties that do not change, you can access your configuration and create your site indicators, pages, commands that will be automatically added to our new data model as properties.
However, a new interface is now available to manage your properties once they are created, this is the Data Management available here. To access it, you need at least access to Data Query.
Find all the properties of your data model
The home screen shows you all the properties available on your data model, whether they are standard or customised.
Each line corresponds to a property for which you have a display name, definition, tags and additional information. If you click on the pencil at the end of the line, you will switch to the edit mode of a property. If this button is not displayed, you do not have the necessary access rights and you can contact your administrator.
Edit the display name of a property
You have the possibility to rename a property in order to see its name modified in Data Query 3 but also in all our interfaces.
This means that if in your data model you have a property called "My custom property" that you rename to "My property". All dimensions called "My custom property", belonging to your organisation will also be renamed. And this even if it is coming from different sites, site, page or order indicators.
Edit the description of custom properties
In your data model you also have the possibility to add descriptions on custom properties to make it easier for all your users to understand. You can edit it at any time.
Add tags to a property
It is now possible to add tags on your properties to simplify access to them. For example, our AT Internet properties have access to tags by default, for example "Browser - Language" contains two tags: Technology and Browser. This will allow you in an interface to filter on the Technology tag and thus display only your properties containing the chosen category. Since you can have several hundred properties this will be extremely convenient for the future! Of course, you can create your own tags and add them to our standard properties but also to your custom properties!
Hide a property
You also have the ability to hide properties so that they no longer appear in Data Query 3. For example, if you do not have audio or video content on your site then the properties related to this content are not useful to you. You can hide them so that you no longer see them in Data Query 3 but of course they will remain accessible in the Data Model interface if you want to reactivate them. In addition, if you use these properties in API calls, don't worry, they will continue to work.