Skip to content

Quickstart

Get Linkrunner attributing your installs in under 10 minutes

This guide walks you through the six steps every Linkrunner integration follows. Each step links out to platform-specific instructions when you need them.

For mobile SDK testing, Open SDK Console in the dashboard. It is in beta and helps you register a test device and verify SDK events.

1. Create a Project & Get Your Token

  1. Sign in to the Linkrunner Dashboard.
  2. Create a new project (or open an existing one).
  3. Copy your Project Token from Dashboard → Documentation.
  4. (Optional, recommended for production) Grab your Secret Key and Key ID from Dashboard → Settings → SDK Signing to enable request signing.

2. Install the SDK

Pick your platform and follow the install steps in the corresponding SDK guide.

bash
npm install rn-linkrunner
# or
yarn add rn-linkrunner

Full React Native guide →

3. Initialize the SDK (Required)

Call init as early as possible in your app's startup — typically in your root component, Application class, or AppDelegate. Pass the optional secretKey and keyId if you set them up in step 1.

javascript
import linkrunner from "rn-linkrunner";

await linkrunner.init(
    "YOUR_PROJECT_TOKEN",
    "YOUR_SECRET_KEY", // Optional
    "YOUR_KEY_ID",     // Optional
);

4. Identify the User (Required)

Call signup once, as soon as the user is identified — whether through signup or login. This is what ties the install (and any future events) to a user identifier and powers revenue and lifecycle attribution.

javascript
await linkrunner.signup({
    user_data: {
        id: "user_123",        // Required
        name: "Jane Doe",      // Optional
        email: "jane@example.com",
        phone: "9876543210",
        is_first_time_user: true,
    },
});

signup is required. setUserData is optional and is not a replacement for signup — call it later only when additional user details become available (e.g., the user adds a phone or completes their profile after the initial signup).

To unlock remarketing and deferred deep linking, forward incoming deep link URLs to Linkrunner. Each SDK exposes a handleDeeplink (or equivalent) method — see the SDK guide for the cold-start and warm-start hooks specific to your platform.

6. Verify Your Setup

For mobile SDKs, use SDK Console to register a test device, verify SDK initialization, check attribution data, and test signup, custom events, and revenue events.

For normal testing, registering the device in SDK Console is enough. Set debug = true in SDK init only if GAID collection is disabled on Android, or the ATT prompt is disabled on iOS so IDFA is unavailable. Remove debug = true before production.

What to Build Next

Need Help?

Email support@linkrunner.io — we typically respond within a few hours during business hours.

Need help? Contact support@linkrunner.io