SaaSquatch Help Center

SaaSquatch integrates with AppsFlyer. This technical reference explains the specifics fields, features, API calls, and functionality that are used in the integration.

πŸ”— New to AppsFlyer?

This page is a technical reference of the AppsFlyer integration. Just getting started for the first time? Check out this article instead: AppsFlyer Getting Started Guide

πŸ”— How it Works

The SaaSquatch integration with AppsFlyer works as follows:

  • SaaSquatch sharelinks will start redirecting to AppsFlyer links

  • SaaSquatch will create AppsFlyer links dynamically by appending custom attribution parameters to the link provided in your AppsFlyer configuration.

    • These links will have data for: af_web_dp, utm_source, utm_medium, utm_campaign, rsCode, rsShareMedium, rsEngagementMedium and _saasquatch

    • You can use _saasquatch to attribute referrals and the other parameters to customize the mobile landing experience.

SaaSquatch will redirect all link clicks through AppsFlyer. Mobile users will be directed by AppsFlyer according to your OneLink configuration and desktop users will be directed to the landing page URL you configured for your SaaSquatch program. SaaSquatch passes this URL through the af_web_dp parameter. If you set the value for af_web_dp in AppsFlyer it will overwrite the value configured for your SaaSquatch program.

IMPORTANT: If you have both Branch Metrics and AppsFlyer integrations enabled, share links will still be redirected to AppsFlyer links, however the Branch deep link will be passed to the AppsFlyer integration instead of your landing page link (in effect, both integrations are applied, Branch first, then AppsFlyer).

When SaaSquatch creates AppsFlyer links dynamically the resulting link and it’s custom attribution parameters produce a deep link similar to the following example:

    "pid": "saasquatch_int",
    "c": "saasquatch",
    "af_web_dp": "",
    "utm_source": "invite",
    "utm_medium": "link",
    "utm_campaign": "saasquatch",
    "rsCode": "REFERRALCODE",
    "rsShareMedium": "UNKNOWN",
    "rsEngagementMedium": "UNKNOWN",
    "_saasquatch": "eyJhcHAucmVmZXJyYWxzYWFzcXVhdGNoLmNvbSI6eyJ0ZXN0XzEyMzQ1NjdfQ09ERSI6eyJjb2RlcyI6eyJyZWZlcnJhbCI6IlJFRkVSUkFMQ09ERSJ9LCJjb2Rlc0V4cCI6eyJSRUZFUlJBTENPREUiOjE2Mjk1ODIxOTl9LCJsaW5rcyI6eyJyZWZlcnJhbCI6Imh0dHBzOi8vc3NxdC5jby9temFBMjIifSwibGlua3NFeHAiOnsiaHR0cHM6Ly9zc3F0LmNvL216YUEyMiI6MTYyOTU4MjE5OX19fX0="

There may be other parameters added by AppsFlyer depending on how your OneLink is configured.

πŸ”— Data Fields

When SaaSquatch creates AppsFlyer links dynamically, it includes a number of custom attribution parameters. These includes fields from AppsFlyer, as well as the standard set of parameters usually passed in the query string to your program landing page by SaaSquatch. The fields are detailed below.


Media source, set as 'saasquatch_int' in AppsFlyer when configuring your custom attribution link


Campaign name, set as 'saasquatch' in AppsFlyer when configuring your custom attribution link


The URL where desktop users will be redirected. Set as the landing page for your program in the SaaSquatch portal. Do not configure a value for this parameter when creating your custom link in AppsFlyer.


Google Analytics-compatible traffic source identifier


Google Analytics-compatible advertising or marketing medium


Google Analytics-compatible campaign name


The Referrer's referral code.


The medium through which the Referrer shared their referral (e.g. Twitter share button)


The medium from which the Referrer engaged with the referral program (e.g. embedded widget)


The Base64URL encoded attribution cookie values. This is necessary to attribute the referral. When decoded, the schema will resemble the following: {"": {"tenantAlias_CODE": {"codes": {"program1": "CODE1"},"codesExp": {"CODE1": 1234567}}}}