User Source is one of the key criteria for measuring ROI on marketing efforts. Source analysis is used for traffic quality measurement and engagements and is essential for knowing the best traffic sources, mediums, or campaigns.

Source analysis is used to:

• Compare user activity or event based on the Source, Campaign, or Medium
• Split Funnels or Cohorts using the Source or Campaign or Medium
• Analyze Sessions or App Opens from a specific source
• Compare Campaign Types for MoEngage Campaigns
• Analyze Conversion and Revenue by Source  

Source Analysis Overview

Source Analysis Details

Source analysis is deeply coupled with Session analysis. When the Source properties change or the Source changes, MoEngage considers it a new Session. Source analysis has a distinct three-step journey.

Source Properties

Two types of Source properties are available: UTM and User-Defined Parameters.

UTM Parameters

UTM parameters are used to analyze different traffic sources. MoEngage SDK, by default, reads the UTM parameters from the URL for the web and the deep link for mobile apps.

MoEngage supports these UTM parameters:

• utm_source: Determines the website or app, or link that sent the traffic. (For example - YouTube, Instagram, or Google)
• utm_medium: Determines the type of channel. (For example - push, banner, email)
• utm_campaign: Determines the name of the campaign. (For example - Newyear, Bigbillionday)
• utm_term: Determines search terms for paid traffic. (For example - Mobile+sale)
• utm_content: Determines the content. (For example - banner, video, product image)

For example, in the given URL, 'utm_source' and 'utm_medium' are source properties, and "MoEngage" and "Email" are the corresponding values.

"https://www.testdomain.com/?utm_source=MoEngage&utm_medium=email&utm_campaign=Newyear &utm_term=mobile+sale&utm_content=image"

User-Defined Parameters

Many marketers use custom source parameters that are specific to their business. MoEngage supports custom source parameters as well. Besides the UTM Parameters, you can also define five custom parameters for your Apps/Websites. MoEngage SDKs will include the new parameters in the URL as source properties and append them for all events.

In push notifications, if there is no deep link or the deep link does not have source information, the system (SDKs) will look for source properties in the key-value pair.

Attribution

MoEngage supports the last-click attribution model. All the user activity/events will be attributed to the last click done by the user. The attribution window here is the session duration.

For example, if the user came from Google Ads, stayed for a session of 5 minutes, and performed 15 events. The source property value for all these 15 events will be Google Ads. For the next session, if the user came organically, all the events in that session will not have any source information.

Source Reports

The following reports are available:

Session Count

Session count shows the total session count across the source properties such as Source or Medium.
The source properties are explained below in this document.

Avg. Session Duration

Avg. Session Duration shows the average session duration for the selected source properties.
Avg. Session Duration = Sum(Session Duration)/(Total No of Session)

Avg. Session / User

Avg. Session / User shows the average number of sessions per user across selected source properties.

Avg. Conversion / Session

Avg. Conversion / Session shows the average number of conversions per session across selected source properties.

Conversion Count

The conversion count shows the total number of conversions across the source properties. For Conversion report calculation, the MoEngage system takes conversion activity/event present in MoEngage Dashboard > Settings > App >General.

Revenue

The revenue report shows the total revenue for the selected source properties. For the Revenue report calculation, the MoEngage system takes Conversion activity/event and Revenue attribute present in MoEngage Dashboard > Settings > App >General.

Bounce Rate

All sessions with fewer than 10 seconds duration are defined as Bounced Sessions. Bounce Rate is the percentage of bounced sessions concerning the total number of sessions. This report is available across selected source properties.

 

 

Report Filters

Filter reports based on one source property. For example, filter reports on a medium like an email.

The Session and source analysis can be performed on the desired group of users. You can filter uses in 2 ways. First, select All users or Filter users by User property, User behavior, User affinity, and Custom segment. To filter users:

1. Select All users or Filter users by
2. In the case of Filter users by, select appropriate filter categories.
3. Select the correct user attribute, user behavior, user affinity, or segment.
4. In both the filter options, All users or Filter users by, you can exclude a specific set of users by selecting User property, User behavior, User affinity, and Custom segment.

You can add multiple filters and apply all filters or only one filter.

Source Properties

All reports are analyzed based on the Source Properties. Select a maximum of two properties for the analysis. By default, reports are not split by any property.

 

Report Analysis

All reports are displayed in the chart and table format. 

Chart Analysis

All reports are, by default, shown in Line chart format, sorted by the highest count. This report can also be viewed in the Bar chart, Columns chart, Area chart, Pie chart, 

Reports can be analyzed in the granularity of Hourly, Daily, Weekly, or Monthly for the desired visualization.

Key Performance Indicators (KPIs) can be analyzed with one click to access overall and quick analysis of the chart reports. KPIs represent comprehensive information and are calculated based on data available in the chart.

Session & Source charts can be saved to any desired dashboard. Click the Save to Dashboard button to save the User Source analysis in custom dashboards. For more information, refer to Custom Dashboards.

Defining KPIs

Linear and Area Charts:

1. For Non-Split and Single Entity Lines: 

   • Average of all data points with the time period (Primary)

   • Number of the last data point with the time period

   • Percentage change from the previous data point

   • Percentage change from the first data point

   • Granularity will be Daily, Weekly, and Monthly
     
     
2. For 2 Entities:

   • Average of all data points for the first entity (Primary)

   • Average of all data points for the second entity (Primary)

   • Value of the last data point with a time period for the first entity

   • Value of the last data point with a time period for the second entity

   • Granularity will be Daily, Weekly, and Monthly
3. For 3-4 Entities:

   • Average of all data points for the first entity/source

   • Average of all data points for the Second entity/source

   • Average of all data points for the third entity/source

   • Average of all data points for the fourth entity/source (if exists)

   • Granularity will be Daily, Weekly, and Monthly
4. For more than 4 Entities
   • Not Applicable (KPIs not allowed for more than four distinct entities)

Bar, Column, and Pie Charts:

1. For Non-Split and Single Entities

   • The aggregate value for the entity with entity name.
   • Granularity will be aggregated.
2. For up to 4 Entities

   • The aggregated value of the data point for the first entity/source with the entity/source name

   • The aggregated value of the data point for the second entity/source with entity/source name (if exists)

   • The aggregated value of the data point for a third entity/source with entity/source name (if exists)

   • The aggregated value of the data point for the fourth entity/source with entity/source name (if exists)

   • Granularity will be aggregated.
     
     
3. For Split sources more than four entities
   • Not Applicable (KPIs not allowed for more than four distinct value entities)

 

Downloading Reports

Download the report after viewing the report. The charts are downloaded in PNG format, and the table is exported in CSV format.

You can transpose the table, it allows you to view and download the table in your preferred format by shifting the vertical and horizontal orientation of the table.

Source Properties in Campaigns

Push Campaigns

To add source properties or UTM parameters in MoEngage push notifications, on the Messaging page of the campaign creation, Actions should be specified.

For Android, iOS, and Windows, Actions for the primary message should be one of - Navigate to a screen, Deeplinking, or Richlanding.
Navigate to a screen - select the specific screen name and add Additional Key-Value pairs.
Deeplinking - The deeplinking URL can have source properties (as specified above in the UTM parameter section), or the user can specify Additional Key-Value pairs.
Richlanding - The rich landing URL can have source properties (as specified above in the UTM parameter section), or the user can specify Additional Key-Value pairs.

For the Web, the Action button URL should have the source properties.

 

 

If URL/URI/Deeplink has been added along with Key-Value pairs, URL/URI/Deeplink will be given preference for selecting the source properties.

Email Campaigns

All the email links should have source properties (as specified above in the UTM parameter section) to analyze the traffic landing on the app/website from the email campaigns.

For Source & Session analysis, the app should have android SDK on or above version 9.7.01, and iOS SDK should be on or above version 5.2.5.

To enable this feature, reach out to us directly from your MoEngage Dashboard -> Need Help? -> Contact Support or send an email to support@moengage.com.