Skip to main content

​
Introduction

When using Komo Engagement Engine for your marketing or promotional campaigns, it’s crucial to track user interactions effectively. Komo Engagement Engine supports both Google Tag Manager (GTM) and Adobe Launch Tag Manager, which are commonly used to manage and implement tracking. Komo Engagement Engine automatically pushes important events to the respective data layers of these tag managers, giving you deep insights into user behavior without extensive manual configuration. In this article, we’ll explain the events Komo Engagement Engine publishes to the data layers, how to access them, and provide sample code to retrieve the data in Google Tag Manager (GTM) and Adobe Launch Tag Manager.

​
Supported Tag Managers

​
Google Tag Manager (GTM)

Google Tag Manager is a versatile tool that allows you to manage tags and track user interactions without modifying your code base constantly. GTM uses a JavaScript array called dataLayer to hold information about events and their related data.

​
Adobe Launch Tag Manager

Adobe Launch Tag Manager is another popular tool for managing tags and tracking user events. It uses adobeDataLayer to store and pass data from your site to Adobe Analytics or other tools you use within the Adobe Experience Cloud.

​
Events Published by Komo

Komo Engagement Engine automatically publishes key user interaction events to the respective tag manager’s data layer dataLayer for Google Tag Manager, adobeDataLayer for Adobe Launch). Below is a list of the most common events and what they represent:
Event NameDescription
auth-viewTriggered when a user views the authentication page or dialog on the platform.
card-actionTriggered when a user performs a specific action on an interactive card. These actions can include: - Competition - ExternalLink - ScrollToCard - OpenProfileDrawer
card-answeredTriggered when a user answers a question on a card, such as Quiz, Poll, Personality Test or Predictor.
card-finishedTriggered when a user completes a gameplay experience for a card.
card-item-viewedTriggered when a user views an individual item within a card, such as a Vote or Carousel item.
card-sharedTriggered when a user shares a card via the Share options for a card.
card-social-clickTriggered when a user clicks on a social media link within a card.
card-startedTriggered when a user begins interacting with a card.
card-viewedTriggered when a card is viewed by a user.
coupon-redeemedTriggered when a user redeems a coupon offered through a card.
coupon-viewedTriggered when a user views a coupon offered through a card.
cover-clickedTriggered when a user clicks the cover image or button for a card.
embedded-card-page-viewedTriggered when a user views a page that has a Komo card embedded in it.
form-startTriggered when a user begins to fill out a form.
form-submissionTriggered when a user submits a form.
page-viewedTriggered when a user views a specific page on a hub.
single-card-page-viewedTriggered when a user views a standalone single-card page.
survey-form-field-touchedTriggered when a user interacts with a field on a Survey card.
survey-screen-finishedTriggered when a user completes a screen within a Survey card.
survey-screen-startedTriggered when a user starts a screen within a Survey card.
survey-screen-viewedTriggered when a screen within a Survey card is viewed by a user.
survey-submittedTriggered when a user submits a completed Survey card.
survey-viewedTriggered when a user views a Survey card.
trivia-card-action-bar-clickedTriggered when a user clicks a link in the action bar of a Live Trivia card. Includes the gameplayStage (lobby, questions, finished, answers, or rules) and the link that was clicked.
trivia-card-prizes-viewedTriggered when a user views the prize options in a Live Trivia card.
video-card-finishedTriggered when a user finishes watching the video on a Video card.
video-card-pausedTriggered when a user pauses the video on a Video card.
video-card-playedTriggered when a user starts playing the video on a Video card.
video-card-resumedTriggered when a user resumes a paused video on a Video card.
video-card-viewedTriggered when a Video card is viewed by a user.
These events provide granular insight into user activity on Komo Engagement Engine, giving you the ability to measure engagement and adjust your campaigns accordingly.

​
Accessing the Data Layers

​
Google Tag Manager: Accessing dataLayer

When Komo publishes an event, it gets pushed to the dataLayer array in GTM. You can access this data using the following code in your web browser’s developer console or within your GTM tags: 
console.log(window.dataLayer);
To capture specific events, you can create a custom event trigger in GTM:
  1. Open Google Tag Manager and go to your Triggers.
  2. Click on New Trigger and choose Custom Event.
  3. In the event name, add the event you want to capture, for example, card-viewed.
  4. Save and publish your trigger.
Once this trigger is set, you can send data to Google Analytics or other connected services for reporting.

​
Adobe Launch Tag Manager: Accessing adobeDataLayer

In Adobe Launch Tag Manager, Komo pushes events to the adobeDataLayer. You can access the data using the following 
console.log(window.adobeDataLayer);
To create a rule in Adobe Launch for specific events like form-submission:
  1. In Adobe Launch, navigate to Rules and create a new rule.
  2. Choose Event Type as Custom Event.
  3. In the event configuration, define the event name (e.g., form-submission).
  4. Save and publish your rule.
This allows you to capture and analyze data from the Komo platform in Adobe Analytics or any other tools you have integrated with Adobe Launch.

​
Example: Creating a Custom Trigger in Google Tag Manager

Here’s a sample code for creating a custom event trigger for the card-viewed event in GTM:
  1. In GTM, navigate to Triggers and click on New.
  2. Choose Custom Event from the list of available trigger types.
  3. In the Event Name field, enter card-viewed.
  4. Set the trigger conditions if necessary (e.g., only fire the trigger on specific pages).
  5. Click Save to finalize the trigger.
You can now link this trigger to a tag, such as sending data to Google Analytics whenever a user views a card on Komo.

​
Conclusion

By leveraging the events Komo Engagement Engine publishes to dataLayer and adobeDataLayer, you can gain deep insights into user behavior and engagement. Whether you’re using Google Tag Manager or Adobe Launch, these events enable you to track meaningful user actions, analyze campaign performance, and make informed decisions to optimize your platform’s performance. For more information on setting up Google Tag Manager or Adobe Launch, refer to the official documentation linked above.