Adjust Migration

This guide is for teams moving from Adjust (Adjust Link / TrueLink) to WarpLink: mapping trackers and link parameters, swapping the SDK, and carrying deep linking, install attribution, and analytics over to WarpLink. It assumes a WarpLink account and app are already set up.

For the provider-agnostic playbook (planning, domains, cutover, decommissioning), see the general migration guide. This page covers only what is specific to leaving Adjust.

Concept Mapping

1. Export Your Links

Tracker list via API. Adjust's Campaign API includes an endpoint that lists trackers for a given app, with cursor-based pagination, so you can pull your tracker list and their parameters programmatically.

Raw click and event data. Adjust exports raw and historical data two ways: real-time server callbacks to your own servers or BI system, or hourly CSV uploads to a customer-owned cloud storage bucket (S3, GCS, or similar), configured under Dashboard > App settings > All Settings > Raw Data Exports > CSV Upload.

Dashboard export. Adjust's Datascape reporting UI lets you filter, visualize, and export reports directly from the dashboard.

2. Recreate Your Links

Recreate each Adjust tracker as a link in WarpLink via the dashboard or the REST API.

Parameter Mapping

Use tags to organize links in the dashboard. On Adjust short links (adj.st/go.link URLs already created), the adj_redirect and adj_fallback query parameters are recognized names but cannot override that short link's destination or fallback, for security reasons. Only tracker-level redirect and fallback control where a link sends a user.

Carry adj_adgroup and adj_creative values as destination_url query parameters.

Create via API

curl -X POST https://api.warplink.app/v1/links \
  -H "Authorization: Bearer wl_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "destination_url": "https://yourapp.com/product/123",
    "ios_url": "myapp://product/123",
    "android_url": "myapp://product/123",
    "utm_campaign": "spring_sale"
  }'

3. Swap the SDK

// Package.swift
dependencies: [
    .package(url: "https://github.com/WarpLinkApp/warplink-ios-sdk", from: "1.2.0")
]

4. Update SDK Initialization

import AdjustSdk

let adjustConfig = ADJConfig(appToken: "{YourAppToken}", environment: ADJEnvironmentProduction)
Adjust.initSdk(adjustConfig)

import WarpLink

WarpLink.configure(
    apiKey: "wl_live_yoursdkkeyhere000000000000000000",
    options: WarpLinkOptions(onLink: { result in
        if case .success(let link) = result, let link {
            navigate(to: link) // taps AND deferred installs (check link.isDeferred)
        }
    })
)

5. Update Domain Configuration

- applinks:f2k5.adj.st
+ applinks:yourapp.aplnk.to

adj.st and branded *.go.link domains are Adjust-owned. The branded domain name cannot be changed once saved, and neither domain can be repointed to another provider, so migrating off either means standing up a new domain on WarpLink and updating every published link. An Enterprise Domain is different: it is your own subdomain, wired to Adjust with an A record in your own DNS. Adjust's own configuration for that domain cannot be changed without contacting Adjust support, but the DNS record itself is yours, so once your links exist on WarpLink you can replace that record (delete Adjust's A record and add WarpLink's CNAME) and keep the domain and its already-distributed links intact. See custom domains.

Keep your existing Adjust Associated Domains and App Links entries in place alongside the new WarpLink ones during the transition, the same approach Adjust itself recommends when adding a new branded domain. This keeps links already distributed (emails, ads, social bios, QR codes) resolving on-device while you cut over.

If Android App Links fail to verify after cutover, the most common causes are a signing-key fingerprint mismatch between assetlinks.json and the APK's actual signature (especially with Play App Signing re-signing), a missing android:autoVerify="true", or assetlinks.json being served via a redirect instead of a direct response.

Moving to a custom domain? Declare it to the SDK too: linkDomains at configure(), or the WarpLinkDomains plist key / app.warplink.DOMAINS manifest entry. See Use it in your app.

6. Migrate Deep Link Handling

The onLink callback set in step 4 already receives resolved links for cold start, warm start, and deferred installs.

func scene(_ scene: UIScene, continue userActivity: NSUserActivity) {
    WarpLink.continue(userActivity)
}

7. Migrate Deferred Deep Links

WarpLink runs the deferred deep link check automatically from configure(). The match arrives in the same onLink callback, flagged with isDeferred. There is no separate deferred call to port.

Adjust's deferred delivery runs through the AdjustDelegate protocol's adjustDeferredDeeplinkReceived(_ deeplink: URL?) -> Bool method on iOS, registered via adjustConfig.delegate before Adjust.initSdk(...), through setDeferredDeeplinkCallback on AdjustConfig in React Native, and through deferredDeeplinkCallback on AdjustConfig in Flutter. Delete those; WarpLink's onLink replaces all of them. On Android, remove whatever deferred handling code you added alongside the SDK itself in step 3.

options: WarpLinkOptions(onLink: { result in
    guard case .success(let deepLink) = result, let deepLink else { return }
    if deepLink.isDeferred {
        print("Match confidence: \(deepLink.matchConfidence ?? 0)")
    }
    navigate(to: deepLink)
})

To run the check manually instead, set the deferred opt-out flag and call checkDeferredDeepLink() yourself (see the deferred deep links guides).

8. Attribution and Reporting

WarpLink attributes installs to the link that drove them through a match cascade: an exact referrer signal (Play Install Referrer) on Android, an enriched probabilistic match on both platforms, and a device ID (IDFV) check on iOS that recognizes an install asking again, with a confidence score on every result. See the iOS attribution guide (or the Android, React Native, and Flutter equivalents) for match types, confidence bands, and privacy details.

Beyond that, running both SDKs for a period is a normal part of a migration: it lets you compare install counts and deep link behavior before retiring Adjust. See Run the Cutover in the general guide for the rollout sequencing.

Testing Checklist

After migration, verify on each platform:

• SDK initializes: enable debug logging and check console output
• Deep links open the app: tap a WarpLink URL on a physical device
• Deep link data resolves: destination and custom parameters are correct
• Deferred deep links work: click link, install, verify match. An uninstall is enough to retest on either platform, because the completion marker goes with the app. That second install is reported as a reinstall and still counts as an install
• AASA/assetlinks verified: curl https://yourapp.aplnk.to/.well-known/apple-app-site-association
• Error handling: test invalid URLs, expired links, no connectivity
• All Adjust code removed: no remaining imports or dependencies
• Clean build: no compilation errors

Next Steps

• General migration guide: the provider-agnostic playbook for planning, domains, cutover, and decommissioning.
• Quickstart: create your first link and get an SDK key.
• iOS SDK, Android SDK, React Native SDK, and Flutter SDK: full setup and API reference.
• Adjust alternative for small teams: cost comparison and positioning for teams evaluating the move.