Channels Overview not only monitor direct app and web entities such as event and properties, but also query parameters that represents channels and campaigns. This is not only interesting for analytics people, to know e.g. which channel attract most leads, but can also be interesting to know on individual level, to perform certain channel-related actions.

Channels Overview

Logical channels vs utm_source/utm_medium.

When a group of marketers decide to add utm query parameters to ads and referring articles, tracking origins of website visits to understand where people come from, they often make mistakes. A channel facebook could be represented by {utm_source=facebook/utm_medium=social} by most. Yet, {utm_source=face_book/utm_medium=organic} by others. And then, just as typically seen in Google Analytics, you suddenly see 2 entries for the same logical channel, and manual work begins to sum it all up...

Since deals with actionable items, we allow users to manage their channel values, to group different {utm_source/utm_medium} values together into one logical channel entity, to subsequentially share it with other 3rd parties apps.
Was this article helpful?
Thank you!