There are 3 different categories of parameters in Google Analytics 4. These are; User Parameters, Event Parameters, and Event Metrics. Below you'll find all of our implemented parameters for Vitec Visiolinks Modular App.
The parameters below differs from our previous Google Analytics 4 implementation mentioned here: https://support.visiolink.com/hc/en-us/articles/8204969185810-Guide-Set-up-Custom-Dimensions-parameters-in-GA4
This guide will go through each type of parameter and what needs to be implemented to fully benefit from Vitec Visiolinks standard tracking. We have redesigned some events, but all events still contain the same, if not more, information than our previous Google Analytics 4 implementation. You can read more about our new standard events for Google Analytics 4 here: https://support.visiolink.com/hc/en-us/articles/21445515663762-Guide-Modular-App-Tracking-GA4
Standard Events in Google Analytics 4 for the Modular App:
1. vl_event_download
2. vl_event_publication
3. vl_event_page
4. vl_event_article
5. vl_event_media
6. vl_event_search
7. vl_event_interstital
8. vl_event_hotspot
9. vl_event_module_interaction
This guide is split into 3 sections:
Section 1 - User Parameters
Section 2 - Event Parameters
Section 3 - How to add User or Event Parameters to your Google Analytics 4 Property
Section 1 - User Parameters
User Parameters are applied to all events are generally parameters that don't change often. There are two tables below for User Parameters. The first table contains the most important User Parameters that we highly recommend to implement. The second table contains the User Parameters needed to fully capture the push token. These should be implemented, if you need the token for sending push messages.
Here is the overview of the recommended User Parameters:
|
Dimension Name |
Description |
Scope |
Parameter (Code) |
|
App_id |
Name of the app/bundle id/application id |
User |
vl_value_app_id |
|
Client |
Platform: iOS, Android, Desktop, Desktop Web App, Fallback |
User |
vl_value_client |
|
Client_id |
Unique hashed id |
User |
vl_value_client_id |
|
User_id |
Unique id that can be connected through the SSO or just be a hashed id |
User |
user_id |
|
User_id_source |
Takes the values: Custom, Server or Client - Depends on how the user id is created. |
User |
vl_value_user_id_source |
|
Version |
Generic platform version |
User |
vl_value_version |
|
Orientation |
Device Orientation: Landscape or Portrait |
User |
vl_value_orientation |
Here is the overview of the Push Token User Parameters:
|
Dimension Name |
Description |
Scope |
Parameter (Code) |
|
Push_token1 |
Part of the push token |
User |
vl_value_push_token1 |
|
Push_token2 |
Part of the push token |
User |
vl_value_push_token2 |
|
Push_token3 |
Part of the push token |
User |
vl_value_push_token3 |
|
Push_token4 |
Part of the push token |
User |
vl_value_push_token4 |
|
Push_token5 |
Part of the push token |
User |
vl_value_push_token5 |
|
Push_token6 |
Part of the push token |
User |
vl_value_push_token6 |
|
Push_token7 |
Part of the push token |
User |
vl_value_push_token7 |
|
Push_token8 |
Part of the push token |
User |
vl_value_push_token8 |
Section 2 - Event Parameters
Below you'll find the overview of Event Parameters. Event Parameters hold information about each event and are needed for all of the event information to be stored. These should always be implemented, so no information is lost.
|
Dimension Name |
Description |
Scope |
Parameter (Code) |
|
Info |
|
Event |
vl_value_info |
|
Publication_date |
Publication Release Date |
Event |
vl_value_publication_date |
|
Publication_title |
Publication Title from HUB |
Event |
vl_value_publication_title |
|
Authentication_method |
|
Event |
vl_value_authentication_method |
|
Source |
Source tracking |
Event |
vl_value_source |
|
Section_number |
Number: 1, 2, 3… |
Event |
vl_value_section_number |
|
Section_name |
Text: Section 1, Section 2, Section 3… |
Event |
vl_value_section_name |
|
Page_number |
Number: 1, 2, 3… |
Event |
vl_value_page_number |
|
Title |
|
Event |
vl_value_title |
|
Author |
|
Event |
vl_value_author |
|
Category |
|
Event |
vl_value_category |
|
Click |
|
Event |
vl_value_click |
|
ID |
|
Event |
vl_value_id |
|
Method |
|
Event |
vl_value_method |
|
Share |
|
Event |
vl_value_share |
|
Saved |
|
Event |
vl_value_saved |
|
Length |
|
Event |
vl_value_length |
|
Search |
|
Event |
vl_value_search |
Below is the table for Event Metrics. There is only one currently, but as with the Event Parameters, this should be implemented to capture all event information possible.
|
Dimension Name |
Description |
Scope |
Parameter (Code) |
|
Duration |
Time spent |
Event |
vl_value_duration |
Section 3 - How to add User or Event Parameters to your Google Analytics 4 Property
Step 1
Go to your Google Analytics 4 Property and click on the Admin-panel in the bottom left.
Step 2
Click on "Custom definitions" located in the "Data display" section.
Step 3
Click on "Create custom dimension".
Step 4
Fill out the form using the information found in this guide. Below example is using the information for the User Parameter "vl_value_orientation" (See section 1 for this information).
Step 5
Save custom dimension.
You have now added one of the parameters needed to capture valuable data. We highly recommend that you repeat step 3 through 5 until all parameters are added.
Comments