iWelcome provides integration with tag management platforms by injecting the required JavaScript snippet on all pages. The snippets to add to each page come in different flavours for different tag managers, such as Tealium, Google, Adobe. To operate correctly with most common tag managers, there are four locations on a page where we can add snippets:

  • Immediately after the <head> opening tag
  • Immediately before the </head> closing tag
  • Immediately after the <body> opening tag
  • Immediately before the </body> closing tag

Note: The solution relies on the Tag Manager to include user identifiers in the events that are generated. iWelcome assumes that Tag Managers (such as Tealium) do so by making use of cookies that are shared between pages of the entire set of applications (iWelcome applications and other applications).

Configurability

In each iWelcome tenant/environment multiple segment/brand combinations can be configured. For each of these combinations a separate ‘tag manager’ can be configured. The events generated from one brand’s pages/views are separated from the events generated from another brand’s pages/views. This allows iWelcome customers to analyse the behaviour of consumers for various brands independently. One does not mention the tenant configurable tag manager.

Event Data/ Data Layer

One can configure what data is included in the Tag Manager event for every ‘view’/page:

  • The event data needs to be configured per segment and brand combination.
  • The event data that can be configured is static.

View List

iWelcome Tag Manager support is limited to consumer facing applications. Each one of these applications is a single page web app with multiple views. Each view will trigger the Tag Manager to generate an event. iWelcome features the following consumer facing applications:

  • Self-service application (a.k.a. MyPage);
  • Login-app;
  • Password reset, activation and registration flow apps.
Application View Comment
Self-Service App
Self-Service Security page
Profile page
Privacy page
Timeline
Login Flow
Login-app Primary login page On this page one can enter their username and password. Also a social IDP can be selected.
2FA-OTP page
Help view
Notification not logged in screen Page where the customer is informed about account lockout.
Password Expiry
Login-app Password expiry: expired
Notification screen
Pasword expiry warning screen
Password expiry set password screen
Registration Flow
Workflow Registration screen Enter email
Document consents
Resend activation email screen
Email sent notification screen
Registration screen Enter email
Document consents
Enter customer number screen
Notification clicked on link screen
Set password screen
IDIN bank selection & consent screen
Matching notification screen - OK/ NOK
Phone number entry screen
Phonenumber verification screen
Account ready screen
Password Reset
Workflow Enter identifier
Reset selection screen
Email sent notification
SMS screen
Set password screen
Notification password set
Disconnect devices

This list may extend in the further. For more information about the process flows, please refer to process section. The actual ‘view - identifiers’ that are included in the events generated by the various views, are not yet included in this document. These will be defined further.