RightLinks

RightLinks onboarding

Step-by-step setup for marketers: create a template, create a link, test it, and measure your results.

This guide walks marketers through setting up RightLinks from scratch: first a reusable template, then a campaign link, then testing and measurement.

RightLink setup has two roles:

  • Marketer - creates templates and links in AdShift, chooses campaign names, media sources, redirects, and reporting parameters.
  • Developer - makes sure the app can open from links and report attribution data through the AdShift SDK.

Everything below lives under Engage -> RightLink Management.

RightLink Management empty state


Before you begin

You need:

  • An AdShift project with at least one app added. Android, iOS, or both can be used in one template.
  • RightLink manage permission in the project.
  • The AdShift SDK integrated in the app if you want attribution, deferred deep linking, and in-app routing. Without the SDK, a RightLink can still redirect users, but it will not credit installs or opens to your campaign.
  • Android App Links / iOS Universal Links configured if installed users should open the app directly instead of following the fallback redirect.
  • A campaign naming convention. Decide how media source and campaign names should appear in reports before creating links.

For a paid media campaign, use the same campaign name in AdShift and in the ad platform whenever possible. This makes cost and performance reporting easier to join later.


A template defines the shared rules for a family of links:

  • which Android and/or iOS app the links belong to,
  • which rightlink.me subdomain the links use,
  • where users go when the app is not installed,
  • whether installed users can open the app through Android App Links or iOS Universal Links,
  • where desktop clicks should go.

From RightLink Management, open the three-dot menu and click Add template.

Add template menu

General information

Enter a clear template name, for example:

  • Listonic production
  • Listonic app campaign links
  • Retail app Android + iOS

The name is internal and helps your team choose the right template when creating campaign links.

Platforms

Select the app or apps covered by the template:

  • Android - select the Android app package.
  • iOS - select the iOS app.
  • Both - select both apps if one link should handle Android and iOS traffic.

Create template general settings

Subdomain

Choose the RightLink subdomain, for example:

listonic.rightlink.me

The subdomain becomes part of every link generated from this template. Once links are generated, treat it as permanent: changing it later can break existing campaign URLs and app association files.

Use a branded, stable subdomain. Avoid names tied to a single campaign if the template will be reused.


Step 2 - Configure redirection

Redirection settings define what happens after a user taps the link. These defaults apply to links created from the template, although individual links can override some destinations.

Template redirection options

Users without the app installed

For each platform, choose the fallback destination:

  • Android
    • Google Play - send users to the app listing.
    • Web URL - send users to a landing page instead.
  • iOS
    • App Store - send users to the app listing.
    • Web URL - send users to a landing page instead.
  • Desktop
    • App Store website or a custom Web URL.

For app-install campaigns, the usual setup is:

  • Android -> Google Play
  • iOS -> App Store
  • Desktop -> a web landing page, app website, or store page

Users with the app installed

Installed users can open the app directly only when the app and template are configured for platform linking:

  • Android App Links require the app package and SHA256 certificate fingerprint.
  • iOS Universal Links require Team ID and Bundle ID.

If App Links / Universal Links are not configured, installed users follow the same fallback path as users without the app installed.

Developers must also implement the in-app behavior: when the app opens, it should read the deep link value from the AdShift SDK and route the user to the right screen.


After the template exists, return to RightLink Management, select the template, and click New link.

In the link wizard, configure the campaign-specific settings.

Experience and media source

Choose the experience that matches your campaign, for example:

  • social-to-app,
  • referral-to-app,
  • QR-to-app,
  • custom.

Then choose the media source. The media source is stored in the link as the pid parameter and becomes the source name in AdShift reports.

For a source that is not listed as a predefined partner, choose Custom media source and enter a stable name, for example:

wp_ads

Campaign name

Enter the campaign name. This is stored in the link as the c parameter and appears in campaign-level reporting.

Use a name that matches the campaign in the ad platform, for example:

wp_ads_october_test

Avoid changing naming conventions mid-campaign. If costs are imported later, the media source and campaign name are the keys that let AdShift join spend to installs.

Retargeting

Turn on Retargeting only if the link is meant to re-engage existing users.

For user acquisition or app-install tests, leave retargeting off unless your campaign is explicitly aimed at returning users.

If you enable retargeting, make sure re-engagement is also enabled in App Settings.


In Deep linking & redirection, decide where the app should open when the app is installed.

Use Deep link value for the in-app destination, for example:

shopping_list

or:

promo_screen

This value is passed to the SDK so the app can route the user to the correct screen. Your developer decides which values the app supports.

Use Additional deep link value for an optional secondary value, such as an item ID, promo code, or content slug.

The link starts with the template's redirection defaults. You can override some destinations for this specific link, for example:

  • send Android users to a custom store listing,
  • send iOS users to a campaign landing page,
  • send desktop users to a specific web page.

Use overrides only when a campaign genuinely needs different behavior from the template default. Otherwise keep redirection centralized in the template.


Step 5 - Add reporting parameters

Use Additional parameters to enrich reporting and downstream analysis.

Common examples:

Parameter Use it for
as_channel Channel or placement group
as_ad Creative/ad name
as_sub1 - as_sub5 Custom dimensions

For paid campaigns, you can also configure:

  • Lookback window - attribution window for the link.
  • Cost parameters - if each click or install has a known fixed cost.

Only use fixed cost parameters when the price is stable and you understand how the ad network bills the campaign. For auction-based campaigns, importing cost reports is usually more accurate.


Step 6 - Generate and use the URL

After saving the link, open Get URL in the link row.

The URL looks like this:

https://your-subdomain.rightlink.me/{templateId}?as_xp=custom&pid=wp_ads&c=wp_ads_october_test&is_retargeting=false

Use this URL as the destination URL in the ad platform, message, QR code, or campaign asset.

Do not manually remove the query parameters. They carry the source, campaign, retargeting flag, cost values, and other attribution data.


Step 7 - Test before launch

Test every link before putting budget behind it.

Android

  1. Open the link on an Android device.
  2. If the app is not installed, confirm it goes to Google Play or the configured Web URL.
  3. If the app is installed and App Links are configured, confirm it opens the app.
  4. Install or open the app and confirm the event appears in AdShift.

iOS

  1. Open the link on an iPhone.
  2. If the app is not installed, confirm it goes to the App Store or configured Web URL.
  3. If the app is installed and Universal Links are configured, confirm it opens the app.
  4. Confirm attribution data appears in AdShift.

Desktop

Open the link on desktop and confirm it follows the configured desktop destination.

Reporting

After test clicks and installs, check AdShift reports for:

  • media source,
  • campaign,
  • installs,
  • re-engagements, if enabled,
  • click volume.

If you used a custom media source such as wp_ads, make sure the same value appears in reports.


Troubleshooting

Check that:

  • Android App Links or iOS Universal Links are configured in the template.
  • The app contains the matching App Links / Universal Links configuration.
  • The app is installed from a build that includes the correct association settings.
  • The device is opening the link in a browser that supports platform links.

Installs are not attributed

Check that:

  • The AdShift SDK is integrated and initialized.
  • The app sends install/open events to AdShift.
  • Android uses Play Install Referrer.
  • The link was used before install.
  • The media source and campaign parameters are still present in the URL.

The wrong campaign appears in reports

Check the link URL:

  • pid should match the media source.
  • c should match the campaign name.
  • The ad platform did not strip or overwrite query parameters.

Cost does not appear

Cost can come from:

  • fixed cost parameters added to the link, when appropriate,
  • cost imports from supported partner APIs,
  • cost files imported into AdShift.

If costs come from a CSV export, make sure the media source and campaign names match the RightLink values.


See also