For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deep Linking Standard

DataLayer Standard

After reading the deeplink values from the framework you are using with your SDK, we created a JENTIS standard for passing this information to our system so that JENTIS standards can be applied.

Category
Mandatory
Property
Description

Link Identity

deeplink_url

the full raw deeplink URL (e.g. myapp://product/123?ref=email)

Link Identity

deeplink_scheme

the URI scheme (e.g. myapp://, https:// for Universal Links)

Link Identity

deeplink_path

the path component (e.g. /product/123)

Source & Attribution

deeplink_source

where the link came from (e.g. email, push_notification, sms, qr_code, social)

Source & Attribution

deeplink_medium

marketing medium (maps well to UTM conventions)

Source & Attribution

deeplink_campaign

campaign name if applicable

Source & Attribution

deeplink_referrer

the app or domain that triggered the open

Context

deeplink_type

deferred vs direct (deferred = user didn't have the app yet)

Context

deeplink_match_type

how it was resolved: exact, fuzzy, none

Context

deeplink_target_screen

the screen/route the app navigated to (e.g. ProductDetailScreen)

Context

deeplink_fallback_triggered

true/false if the fallback URL was used instead

Here is an example data layer command:

iOS Implementation:

TrackingService.shared.push([
  "track": "deeplink_opened",
  "deeplink_url": "myapp://product/123",
  "deeplink_scheme": "myapp://",
  "deeplink_path": "/product/123",
  "deeplink_source": "push_notification",
  "deeplink_campaign": "spring_sale_2026",
  "deeplink_type": "direct",
  "deeplink_target_screen": "ProductDetailScreen",
  "deeplink_fallback_triggered": false
])

try await TrackingService.shared.submit()

Android Implementation:

Coding Example

It is very important, when choosing a technology, that it is able to read URL parameters so this information can be passed to the JENTIS DataLayer — for example, to include them in a pageview request.

But how can these parameters be read?

We have created a code example (Server-Side Variable) that demonstrates how to read URL parameters:

Last updated

Was this helpful?