Skip to main content

Installation

Requirements

  • Flutter 3.19.0 or higher
  • Dart 3.3.0 or higher
  • iOS 15.0+ / Android 5.0 (API level 21) and above

Step 1: Add the Package

Run the following command to add the latest version of the Linkrunner package to your project:
This command will automatically:
  • Add the latest version of linkrunner to your pubspec.yaml
  • Download and install the package and its dependencies

Step 2: Platform Specific Setup

Android Configuration

  1. Ensure your project’s minSdkVersion is at least 21 in your android/app/build.gradle file:
  1. Add the following permissions to your AndroidManifest.xml file:
Note: The AD_ID permission (<uses-permission android:name="com.google.android.gms.permission.AD_ID" />) is already included in the SDK and is required for collecting device identifiers (GAID). If your app participates in Designed for Families, you should revoke AAID and disable AAID collection. See the Disabling AAID Collection section for more details.

Revoking the AD_ID Permission

According to Google’s Policy, apps that target children must not transmit the Advertising ID. To revoke the AD_ID permission, use Flutter SDK version 3.5.0 and above. Children apps targeting Android 13 (API 33) and above must prevent the permission from getting merged into their app by adding a revoke declaration to their Manifest. Use the setDisableAaidCollection() and isAaidCollectionDisabled() functions to disable AAID collection programmatically: android/app/src/main/AndroidManifest.xml
Make sure to add xmlns:tools="http://schemas.android.com/tools" to your manifest tag to use the tools:node="remove" attribute. If you disable AAID collection, you should also remove the AD_ID permission from your manifest to fully comply with Google Play’s Family Policy requirements.
For more information, see Google Play Services documentation.

Backup Configuration

For Android apps, the SDK provides backup rules to exclude Shared Preferences data from backup. This prevents the retention of the Linkrunner install ID during reinstallation, ensuring accurate detection of new installs and re-installs. For detailed backup configuration instructions, please refer to the Android SDK Backup Configuration.

Encrypted SharedPreferences

SDK Version Requirement: Starting from linkrunner v3.9.1, the SDK automatically encrypts the credentials it stores in Android SharedPreferences (such as the install ID and other persisted SDK state). No additional configuration is required — upgrade to v3.9.1 or above to get this behavior by default.
On Android, values written by the SDK are encrypted at rest, with a hardware-protected key generated on the device and stored in the Android Keystore. The key never leaves the device and is not bundled with the SDK. If you are upgrading from an earlier version, the SDK will transparently migrate any existing plaintext entries to the encrypted store on the next read after the upgrade — no code changes are needed on your side.

iOS Configuration

  1. Update your iOS deployment target to iOS 15.0 or higher in your ios/Podfile:
  1. Add the following to your Info.plist file for App Tracking Transparency:

Initialization (Required)

You’ll need your project token to get started! Note: The initialization method doesn’t return any value. To get attribution data and deeplink information, use the getAttributionData method.

SDK Signing Parameters (Optional)

For enhanced security, the LinkRunner SDK requires the following signing parameters during initialization:
  • secretKey: A unique secret key used for request signing and authentication
  • keyId: A unique identifier for the key pair used in the signing process
You can find your project token, secret key, and key ID here.

Platform-Specific SDK Signing

For applications requiring different signing keys per platform:

Setting the Customer User ID

Use setCustomerUserId to attach your own user identifier to the device right after init. Once set, the identifier is stored securely on-device and automatically included in every event you track, so you never have to pass it on each trackEvent call. Call it as early as the user’s ID is available. This guarantees every event carries a user_id from the very first event, and is especially useful for existing users who were already onboarded before this feature shipped.
Available from Flutter SDK v3.10.0.
Best practice: set the Customer User ID as early as possible. The user_id is only attached to events tracked after it’s set, and is not applied retroactively. Use a stable, unique identifier from your own system (for example your internal user ID or a UUID) rather than an email address or other PII.
The identifier is stored securely on-device and persists across app restarts. Calling setCustomerUserId again with a different identifier updates the stored value; passing the same identifier is a no-op. signup() / setUserData() also update it.

User Identification (Required)

Call the signup method as soon as the user is identified — whether through signup or login. This is the moment Linkrunner ties the install (and any future events) to a user identifier. It is strongly recommended to use the integrated platform’s identify function to set a persistent user_id once it becomes available (typically after signup or login). If the platform’s identifier function is not called, you must provide a user identifier for Mixpanel, PostHog, and Amplitude integration.
  • mixpanelDistinctId for Mixpanel
  • amplitudeDeviceId for Amplitude
  • posthogDistinctId for PostHog
To enable remarketing and reattribution, you need to capture deep links and pass them to the Linkrunner SDK. This allows Linkrunner to detect returning users who open the app via a deep link.
Linkrunner sends the updated deeplink back after processing. For Linkrunner campaign links, use the returned deeplink as the resolved destination instead of the original tracking URL.

Getting Attribution Data

To get attribution data and deeplink information for the current installation, use the getAttributionData function:
The getAttributionData function returns an AttributionData object with the following structure:
Example response:

Setting User Data

Call setUserData each time the app opens and the user is logged in:
setUserData is optional and is not a replacement for signup. Always call signup first as soon as the user is identified (signup or login). Use setUserData afterwards only when additional user details become available later — for example, when the user adds a phone number, email, or completes their profile after identification.

Setting CleverTap ID

Use the setAdditionalData method to set CleverTap ID:

Parameters for LinkRunner.setAdditionalData

  • clevertap_id: String (optional) - CleverTap user identifier
This method allows you to connect user identities across different analytics and marketing platforms.

Revenue Tracking

Revenue data is only stored and displayed for attributed users. Make sure you have implemented the .signup function before capturing payments. To attribute a test user, follow the Integration Testing guide. You can verify your events are being captured on the Events Settings page.

Capturing Payments

Track payment information:

Parameters for LRCapturePayment

  • amount: double (required) - The payment amount
  • userId: String (required) - Identifier for the user making the payment
  • paymentId: String (required) - Unique identifier for the payment, used to deduplicate transactions
  • type: PaymentType (optional) - Type of payment. Available options:
    • PaymentType.FIRST_PAYMENT - First payment made by the user
    • PaymentType.SECOND_PAYMENT - Second payment made by the user
    • PaymentType.WALLET_TOPUP - Adding funds to a wallet
    • PaymentType.FUNDS_WITHDRAWAL - Withdrawing funds
    • PaymentType.SUBSCRIPTION_CREATED - New subscription created
    • PaymentType.SUBSCRIPTION_RENEWED - Subscription renewal
    • PaymentType.ONE_TIME - One-time payment
    • PaymentType.RECURRING - Recurring payment
    • PaymentType.DEFAULT_PAYMENT - Default type (used if not specified)
  • status: PaymentStatus (optional) - Status of the payment. Available options:
    • PaymentStatus.PAYMENT_INITIATED - Payment has been initiated
    • PaymentStatus.PAYMENT_COMPLETED - Payment completed successfully (default if not specified)
    • PaymentStatus.PAYMENT_FAILED - Payment attempt failed
    • PaymentStatus.PAYMENT_CANCELLED - Payment was cancelled
  • eventData: Map<String, dynamic> (optional) - Key-value pairs for additional event data, including Meta ecommerce properties.

Removing Payments

Remove payment records (for refunds or cancellations):

Parameters for LRRemovePayment

  • userId: String (required) - Identifier for the user whose payment is being removed
  • paymentId: String (optional) - Unique identifier for the payment to be removed
Note: Either paymentId or userId must be provided when calling removePayment. If only userId is provided, all payments for that user will be removed.

Ecommerce Events

Minimum SDK Version: Ecommerce Event Manager requires linkrunner-flutter v3.7.0 or above. Please ensure your SDK is updated before using this feature.
If you are tracking Ecommerce events to sync with Meta Catalog Sales, you must format your eventData to include Meta’s required fields. You also need to map your custom event to the standard commerce event in the Linkrunner Dashboard. For detailed explanations of the required fields like content_ids, contents, and value, refer to our Meta Commerce Manager documentation.

Add To Cart Example

Use the trackEvent method to send an AddToCart event:

View Content Example

Use the trackEvent method to send a ViewContent event:

Payment / Purchase Example

Use the capturePayment method to send a Purchase event containing the ecommerce payload:
Note: For more information on testing and verifying your ecommerce events, please see our Testing Ecommerce Events guide.

Tracking Custom Events

From Flutter SDK v3.10.0, custom events automatically include the user_id you set during signup() / setUserData(). The SDK stores this identifier securely on-device and attaches it to every trackEvent call, so you no longer need to pass it manually. Events tracked before signup are sent without a user_id.
Events are only stored and displayed for attributed users. Make sure you have implemented the .signup function before tracking events. To attribute a test user, follow the Integration Testing guide. You can verify your events are being captured on the Events Settings page. For capturing revenue, it is recommended to use the .capturePayment method instead of .trackEvent.
Track custom events in your app:

Parameters for LinkRunner().trackEvent

  • eventName: String (required) - Name of the event to track
  • eventData: Map<String, dynamic> (optional) - Key-value pairs for additional event data, including Meta ecommerce properties
  • eventId: Object (optional) - Your own unique identifier for the event (String or num), useful for deduplication and correlating with your backend

Revenue Sharing with Ad Networks

To enable revenue sharing with ad networks like Google Ads and Meta, include an amount parameter as a number in your custom event data. This allows the ad networks to optimize campaigns based on the revenue value of conversions:
For revenue sharing with ad networks to work properly, ensure the amount parameter is passed as a number (double or int), not as a string.

Enhanced Privacy Controls

The SDK offers options to enhance user privacy:
When PII hashing is enabled, sensitive user data like name, email, and phone number are hashed using SHA-256 before being sent to Linkrunner servers.

Disabling AAID Collection

SDK Version Requirement: The AAID collection disable functionality requires Flutter SDK version 3.5.0 or higher.
The SDK provides options to disable AAID (Google Advertising ID) collection. This is useful for apps targeting children or families to comply with Google Play’s Family Policy.
Disabling AAID collection is not recommended unless absolutely necessary. The GAID is a primary signal for Google Ads attribution and install matching, so disabling it reduces attribution accuracy. Only disable it if your app is built for children or families and must comply with Google Play’s Family Policy.

Disable AAID Collection

To disable AAID collection, call setDisableAaidCollection before SDK initialization:
When AAID collection is disabled, the SDK will not collect or send the Google Advertising ID (GAID) to Linkrunner servers.

Removing AD_ID Permission

If you want to completely remove the AD_ID permission from your app’s manifest (for example, for apps targeting children), you can override the SDK’s permission declaration in your android/app/src/main/AndroidManifest.xml. For detailed instructions on revoking the AD_ID permission, including Google’s policy requirements for apps targeting children and Android 13+ (API 33+), see the Revoking the AD_ID Permission section above.

Uninstall Tracking

Before you begin

Here’s what you need to know before getting started: Requirements:

Android

Connect Firebase Cloud Messaging (FCM) with Linkrunner
To configure FCM HTTP V1 for uninstalls:Enable the FCM API:
  1. Go to the FCM console.
  2. Select a project.
  3. Go to Project Overview > Project settings.
  4. Copy the Project ID. This will be required in a later step. Project ID
  5. Go to the Cloud Messaging tab.
  6. Make sure that Firebase Cloud Messaging API (V1) is set to Enabled.
Create a custom role for Linkrunner Uninstall:
  1. Go to the Service accounts tab.
  2. Click Manage service account permissions.
  3. A new browser tab opens in Google Cloud Platform.
  4. In the side menu, select Roles.
  5. Click + Create role.
  6. Enter the following details:
    • Title: Linkrunner Uninstalls
    • ID: lr_uninstalls
    • Role launch stage: General availability
  7. Click + Add permissions.
  8. In Enter property name or value field, enter cloudmessaging.messages.create and select it from the search results. Google Cloud Permission
  9. Check the cloudmessaging.messages.create option and click Add.
  10. Click Create.
Assign Linkrunner the FCM uninstall role:
  1. In the side menu, select IAM.
  2. Open the View by Principals tab.
  3. Click Grant Access.
  4. In Add Principals -> New principals field, enter lr-uninstalls-tracking@lr-uninstalls-tracking.iam.gserviceaccount.com
  5. In Assign Roles -> Select a role field, enter Linkrunner Uninstalls and select it from the search results.
  6. Click Save.
The Linkrunner service account has been assigned the role of Linkrunner Uninstalls.
  1. In Linkrunner, go to Settings > Uninstall Tracking.
  2. Under the Android tab, enter the Firebase Project ID that you copied initially and click Save. Uninstall Tracking
Follow these instructions to integrate FCM with the Linkrunner SDK:
  1. Set up Firebase Cloud Messaging:
Set up Firebase Cloud Messaging in your flutter app. See the Firebase Cloud Messaging documentation for detailed instructions.
  1. Configure your app to provide the device’s push token to the Linkrunner SDK.
Custom implementations of FCM’s onMessageReceived method can unintentionally make uninstall push notifications visible to users, disrupting the intended silent experience. To avoid this, ensure your logic checks if the message contains lr-uninstall-tracking and handles it accordingly, as shown in the code example above.

iOS

Connect APNs with Linkrunner
Get the required credentials from the Apple Developer Portal:APNs Authentication Key (p8) and Key ID:
  • Go to the Apple Developer Portal.
  • Select Identifiers under Certificates, IDs & Profiles.
  • Click on the app you want to track uninstalls for. Then, under Capabilities, search for Push Notifications and enable it.
  • Under Certificates, IDs & Profiles, select Keys and click on plus (+) icon to create a key. Enable APNs when creating the key and download the key file (p8).
  • The Key ID can be found in the Keys tab.
Bundle ID and Team ID:
  • Under Identifiers, click on your app and you will see the Bundle ID and Team ID (App ID Prefix).
  1. In Linkrunner, go to Settings > Uninstall Tracking.
  2. Under the iOS tab, upload the APNs Authentication Key (p8) file and enter the Key ID, Bundle ID and Team ID (App ID Prefix) that you copied from the Apple Developer Portal. Uninstall Tracking
Follow these instructions to integrate FCM with the Linkrunner SDK:
  1. Set up Firebase Cloud Messaging:
Set up Firebase Cloud Messaging in your flutter app if you haven’t already. See the Firebase Cloud Messaging documentation for detailed instructions.
  1. Configure your app to provide the device’s APNs token to the Linkrunner SDK.

Function Placement Guide

FunctionWhere to PlaceWhen to Call
LinkRunner().initApp initializationOnce when app starts
LinkRunner().getAttributionDataAttribution data handling flowWhenever the attribution data is needed
LinkRunner().setAdditionalDataIntegration codeWhen third-party integration IDs are available
LinkRunner().signupIdentification flow (signup or login)Once when the user is identified
LinkRunner().setUserDataAuthentication logicEvery time app opens with logged-in user
LinkRunner().trackEventThroughout appWhen specific user actions occur
LinkRunner().capturePaymentPayment processingWhen user makes a payment
LinkRunner().removePaymentRefund flowWhen payment needs to be removed
LinkRunner().handleDeeplinkDeep link entry pointsWhen app is opened via a deep link
LinkRunner().setDisableAaidCollectionApp initialization or privacy settingsWhen you need to disable AAID collection
LinkRunner().isAaidCollectionDisabledPrivacy settings or compliance checksWhen you need to check AAID collection status

Complete Example

Here’s a simplified example showing how to integrate Linkrunner in a Flutter app: You can find your project token here.

Next Steps

Test Your Integration

Validate your setup end-to-end

Set Up Deep Linking

Configure deep links for your app

Support

If you encounter issues during integration, contact us at support@linkrunner.io.