Tracking Link Parameters

More Guides for Integrated Partners • More Guides on Singular Links for Customers

Tracking link parameters play a crucial role in ensuring accurate data collection and attribution for ad network partners. Singular tracking links support a wide variety of parameters that allows ad networks to append valuable information about clicks and impressions. By populating these parameters, ad networks can pass critical data to Singular, enabling more precise measurement of campaign performance.

Once a tracking link is triggered, the Singular tracker processes the embedded parameters and utilizes them in various ways, such as:

Tracking links are a key component of your integration as an integrated media source with Singular. They allow you to pass essential data about clicks and impressions, ensuring accurate attribution and campaign measurement. If your company also supports postbacks, be sure to review the Postback Macros and Passthrough Parameters for Ad Networks section before you submit an integration request with Singular. Once you have gathered all the necessary details, you can apply here to be an integrated media source with Singular.

Show: All Device Data Granularity Parameters Singular Links Behavior Website Links Parameters

Disabling Parameter Overrides for Short Links

By default, you can append redirect and deeplink parameters to a Singular Link (such as _dl , _fallback_redirect , _ios_redirect , etc.) at click time to dynamically override the link's saved settings. This is useful when you need to serve different redirect destinations from the same base link.

However, in some workflows — for example, when many team members share links internally — you might want to prevent link override and reuse.

The Disable short link parameters overrides feature lets you lock a shortened custom link so that parameters already set in the base link cannot be overridden via URL appending. Parameters not set in the base link can still be appended as new values.

How it works

The following redirect and deeplink parameters are specifically protected from override when they are set in the base link:

_dl , _android_dl , _ios_dl , _ddl , _android_redirect , _android_ddl , _ios_redirect , _ios_ddl , _fallback_redirect

Any other parameter already defined in the base link is also protected.

How to enable it (UI)

1. Go to Links → Manage Links in the Singular platform.
2. Locate your custom link and click to edit it (or create a new one).
3. If you do not see the Disable short link parameters overrides toggle, try toggling Shorten Link on first.
4. Enable the Disable short link parameters overrides toggle.
5. Save the link.

How to enable it (API)

This setting is also supported when creating or updating a link via the Singular Links API . Pass the disable_short_link_parameters_overrides boolean optional parameter in your request body:

• false (default) — parameters in the base link can be overridden by appending them to the short link.
• true — parameters already set in the base link are locked and cannot be overridden.

If you use the Dynamic Short Links API , any generated short link automatically inherits the disable_short_link_parameters_overrides value from its base Singular Link. No additional configuration is required.

Limitations

• This feature is available for custom (source) links only . It is not available for partner links.
• This is a per-link setting . For account-level control over which redirect destinations are allowed across all links, see Limiting Override Destinations .

URL Encoding Required for Dynamic Deep Links and Third-Party Store Redirects

URL encoding is mandatory for all dynamic deep link parameters and third-party store redirect parameters (for example, _samsung_redirect or _android_dl ).

We’ve observed multiple cases where customers or partners append Singular links without URL-encoding query parameter values, resulting in links failing to resolve correctly or unexpectedly falling back to the Play Store.

To ensure consistent and reliable behavior across devices and browsers, always use URL-encoded values. Proper encoding:

• Ensures correct resolution of dynamic deep links
• Enables reliable third-party store redirects
• Prevents unintended fallback behavior (such as Play Store redirects)

Example

Correct (URL-encoded):

&_samsung_redirect=samsungapps%3A%2F%2FProductDetail%2Fnet.singular.deviceassist2

Incorrect (not encoded):

&_samsung_redirect=samsungapps://ProductDetail/net.singular.deviceassist2