Help & DocumentationSystem AdministrationControlling Access to Metric InsightsMobile AppDeploying Mobile Apps with Support for Deep Links (Links to the Metric Insights Mobile App)

Deploying Mobile Apps with Support for Deep Links (Links to the Metric Insights Mobile App)

This document describes the basic process for deploying a mobile app with support for Deep Links (e.g. a link is clicked in an email from Metric Insights, and the Metric Insights mobile app is opened rather than the web browser.

NOTE: This cannot be done without a custom build from the Metric Insights Engineering Team.

Deep linking for the following tools is configured automatically:

  • Power BI
  • Tableau
  • MS SharePoint

Refer to this article for the instructions for QlikSense.

Provide List of Supported Domains

In order for deep linking to work, the mobile app (iOS or Android) needs to know which domains to route to the Metric Insights app instead of a web browser.

This is done by including a list of Associated Domains, e.g:


This would support 3 separate metric insights environments (product, development and QA)

Associated Domains need to be applied both in the custom build prepared by Metric Insights, and in the customer's own Apple Developer Enterprise account:

Important: You will need to provide the Metric Insights Engineering team with your list of Associated Domains for a custom build with Deep Linking to be prepared.

Define App ID on Metric Insights Server

To set the site association, you'll need to include your Team ID into the MOBILE_APPLE_APP_ID system variable.

1. Get Team ID

  1. Access > Account > Certificates, IDs & Profiles
  2. Copy your Team ID located at the top right corner of the screen

2. Configure the System Variable

  1. At Metric Insights, access Admin > System > System Variables
  2. Find MOBILE_APPLE_APP_ID variable, click on its gear icon
  3. Enter iOS App Identifier in the following format:, where XXXXXXXXXX is your Team ID
  4. [Save]

This information is provided for your understanding, but we recommend sticking to the system default ("deep_link") and not making any modifications.

There is a single system Config Variable, MOBILE_DEEP_LINKING_PREFIX that defines the prefix to place before the trailing URL, e.g. https://<domain>/<deep link prefix>/<remainingurl> or, expressed more clearly,

MOBILE_DEEP_LINKING_PREFIX is set to deep_link by default and does not need to be changed.

All links in Bursts and other email distributions that include an Element will use this URL pattern.

Scope of Objects that Support Deep Linking

Deep linking will work for the following Element types:

  1. Reports (including Dimensions)
  2. Metrics (including Dimensions)
  3. External Reports (including Dimensions)

Technically, each Element supports the following URL pattern

  • https://<domain>/deep_link/report/index/index/element/<int value>/segment/<int value>
  • https://<domain>/deep_link/chart/index/index/element/<int value>/segment/<int value>
  • https://<domain>/deep_link/extreport/index/index/element/<int value>/segment/<int value>