Webhooks

Overview

Webhooks allow you to receive real-time HTTP notifications when attribution events occur in your app. When a user installs your app or signs up, Linkrunner sends a POST request to your configured endpoint with detailed attribution data. Common use cases:

Server-side analytics and reporting
CRM integration for user onboarding
Real-time Slack notifications
Custom attribution pipelines

Configuration

Setting Up Your Webhook URL

Go to Linkrunner Settings → Webhooks
Enter your webhook endpoint URL
Save the configuration

Your endpoint must be publicly accessible and respond with a 2xx status code to acknowledge receipt.

Testing Your Endpoint

Before going live, verify your endpoint can:

Accept POST requests with JSON body
Respond within a reasonable time (recommended under 5 seconds)
Return a 2xx status code on success

Webhook Events

Linkrunner sends webhooks for the following events:

Event	Description
`install`	Triggered when an app install is attributed to a campaign or organic source
`signup`	Triggered when a user signup event is recorded via the SDK

Install Webhook

The install webhook is triggered immediately when Linkrunner attributes an app installation. At this point, your app has just been opened for the first time and the user hasn’t had a chance to sign up or log in yet. Because of this, the user_id field will be null in install webhooks. However, the install webhook does include device identifiers (gaid for Android, idfa for iOS) when available. You can use these to match the install with the user later when they sign up. Use the install webhook for:

Tracking install counts by campaign
Analyzing attribution data (network, ad creative, etc.)
Monitoring app store conversion rates
Storing device IDs to link with user accounts later

The signup webhook is triggered when you call the .signup() method in your app via the Linkrunner SDK. This happens after the user has signed up or logged in, so the user_id field will contain the ID you passed to the SDK. The signup webhook includes device identifiers (gaid/idfa) along with the user_id, giving you a complete picture of both the device and the user. It also includes user identity fields (name, phone, email) and any custom parameters you passed via additional_data, such as referral codes or other custom key-value pairs. Use the signup webhook for:

Linking attribution data to your user records
CRM integration and user onboarding flows
Calculating signup conversion rates from installs
Forwarding custom parameters (e.g., referral codes) to your backend

To receive signup webhooks, you must call .signup() in your app after the user signs up or logs in. See your SDK’s usage guide for implementation details.

Payload Structure

All webhooks are sent as POST requests with a JSON body.

Headers

Header	Description
`Content-Type`	`application/json`
`linkrunner-key`	Your project’s private key for authentication

Body Parameters

Field	Type	Description
`event_type`	`"install"` \| `"signup"`	The type of attribution event
`user_id`	`string` \| `null`	Customer user ID (if provided via SDK)
`campaign_id`	`string`	Unique identifier for the campaign
`campaign_name`	`string` \| `null`	Human-readable campaign name
`network_name`	`string` \| `null`	Attribution network: `ORGANIC`, `META`, `GOOGLE`, etc.
`ad_channel`	`string` \| `null`	Ad channel: `META`, `GOOGLE`, `TIKTOK`, `APPLE_SEARCH_ADS`, etc.
`attributed_on`	`ISO 8601 date`	Timestamp when attribution occurred
`installed_at`	`ISO 8601 date` \| `null`	Timestamp of app installation
`store_click_at`	`ISO 8601 date` \| `null`	Timestamp of store redirect click
`link`	`string`	The campaign link URL
`app_version`	`string` \| `null`	Installed app version
`gaid`	`string` \| `null`	Google Advertising ID (Android)
`idfa`	`string` \| `null`	Identifier for Advertisers (iOS)
`name`	`string` \| `null`	User’s name (from `user_data.name` passed to the SDK)
`phone`	`string` \| `null`	User’s phone number (from `user_data.phone` passed to the SDK)
`email`	`string` \| `null`	User’s email address (from `user_data.email` passed to the SDK)
`additional_data`	`object` \| `null`	Custom parameters and device data (from the `data` field passed to the SDK)
`meta_campaign_details`	`object` \| `null`	Meta Ads campaign details (see below)
`google_campaign_details`	`object` \| `null`	Google Ads campaign details (see below)

The name, phone, and email fields are populated from user_data passed to the SDK’s .signup() or .trigger() methods.
The additional_data field is populated from the SDK data object.
For install events, these fields are null since user-level signup data is not yet available.

Meta Campaign Details

When the attribution is from Meta Ads, meta_campaign_details contains:

Field	Type	Description
`ad_creative_id`	`string` \| `null`	Meta ad creative ID
`ad_creative_name`	`string` \| `null`	Ad creative name
`ad_set_id`	`string` \| `null`	Ad set ID
`ad_set_name`	`string` \| `null`	Ad set name
`campaign_group_id`	`string` \| `null`	Campaign group ID
`campaign_group_name`	`string` \| `null`	Campaign group name
`account_id`	`string` \| `null`	Meta Ads account ID
`ad_objective_name`	`string` \| `null`	Campaign objective (e.g., `APP_INSTALLS`)
`is_instagram`	`boolean` \| `null`	Whether the ad was on Instagram
`publisher_platform`	`string` \| `null`	Platform where ad was shown
`platform_position`	`string` \| `null`	Placement position

Google Campaign Details

When the attribution is from Google Ads, google_campaign_details contains:

Field	Type	Description
`gclid`	`string` \| `null`	Google Click ID
`gbraid`	`string` \| `null`	Google app campaign tracking parameter
`ga_source`	`string` \| `null`	Google Analytics source
`ad_group_id`	`string` \| `null`	Ad group ID
`ad_group_name`	`string` \| `null`	Ad group name

Additional Data

The additional_data object contains custom parameters and device data passed through the SDK. This is useful for forwarding arbitrary key-value pairs like referral codes or custom identifiers through the attribution flow. Example:

{
  "id": "user_123",
  "name": "Test User",
  "email": "test@example.com",
  "phone": "9876543210",
  "device_data": {},
  "referral_code": "ABC123",
  "custom_param_name": "custom_value"
}

Example Payloads

Install Event

{
  "event_type": "install",
  "user_id": null,
  "campaign_id": "camp_XYZ123",
  "ad_channel": "META",
  "network_name": "META",
  "app_version": "2.4.1",
  "campaign_name": "Summer Promotion 2023",
  "attributed_on": "2026-03-24T08:11:00.464Z",
  "installed_at": "2026-03-24T08:11:00.464Z",
  "store_click_at": "2026-03-24T08:11:00.464Z",
  "link": "https://dl.linkrunner.io/?c=camp_XYZ123",
  "meta_campaign_details": { ... },
  "google_campaign_details": null,
  "gaid": "bk9384xs-p449-96ds-r132",
  "idfa": null,
  "name": null,
  "phone": null,
  "email": null,
  "additional_data": null
}

{
  "event_type": "signup",
  "user_id": "test_user_webhook_002",
  "campaign_id": "OgWmhiSXhG",
  "ad_channel": "META",
  "network_name": "ORGANIC",
  "app_version": "1.0.0",
  "campaign_name": "TOF - Free trial - AAA - DSDT - 17/12",
  "attributed_on": "2026-03-25T15:52:00.007Z",
  "installed_at": "2025-12-30T12:34:29.742Z",
  "store_click_at": null,
  "link": "https://dl.linkrunner.io/?c=OgWmhiSXhG&utm_source=meta_ads",
  "meta_campaign_details": null,
  "google_campaign_details": null,
  "gaid": "5faa2433-d7e1-4a8e-9a1c-a5880c26ab5c",
  "idfa": null,
  "name": "Test User",
  "phone": "9876543210",
  "email": "test@example.com",
  "additional_data": {
    "id": "test_user_webhook_002",
    "name": "Test User",
    "email": "test@example.com",
    "phone": "9876543210",
    "device_data": {},
    "referral_code": "ABC123",
    "custom_param_name": "custom_value"
  }
}

Authentication

Every webhook request includes a linkrunner-key header containing your project’s private key. Use this to verify that requests are genuinely from Linkrunner.

// Example: Verifying the webhook signature
const PRIVATE_KEY = process.env.LINKRUNNER_PRIVATE_KEY;

app.post('/webhook', (req, res) => {
  const receivedKey = req.headers['linkrunner-key'];

  if (receivedKey !== PRIVATE_KEY) {
    return res.status(401).json({ error: 'Unauthorized' });
  }

  // Process the webhook...
  res.status(200).json({ received: true });
});

Never expose your private key in client-side code. Store it securely as an environment variable.

Slack Integration

Linkrunner automatically formats webhook payloads for Slack when your URL contains hooks.slack.com. Instead of raw JSON, Slack receives a rich Block Kit formatted message displaying:

Event type and user ID
App version and network
Campaign name
Attribution timestamps
Device identifiers (GAID/IDFA)
User identity (name, phone, email)
Meta campaign details (if applicable)

To set up Slack notifications:

Create an Incoming Webhook in your Slack workspace
Copy the webhook URL (format: https://hooks.slack.com/services/...)
Paste it as your webhook URL in Linkrunner settings

Retry Behavior

If your endpoint fails to respond with a 2xx status code, Linkrunner retries the webhook with exponential backoff:

Attempt	Delay
1st retry	1 second
2nd retry	2 seconds
3rd retry	4 seconds

After 3 failed attempts, the webhook is marked as failed. Ensure your endpoint is reliable to avoid missing events.

Best Practices

Respond quickly

Return a 2xx status code as fast as possible. Process the webhook data asynchronously to avoid timeouts.

Implement idempotency

Store processed campaign_id + user_id combinations to handle potential duplicate deliveries gracefully.

Validate authentication

Always verify the linkrunner-key header matches your private key before processing.

Handle failures gracefully

Log failed webhook processing for debugging and implement alerting for critical failures.

Troubleshooting

Webhooks not being received?

Verify your endpoint URL is correct and publicly accessible
Check that your server accepts POST requests with JSON body
Ensure your firewall allows incoming requests from Linkrunner

Getting 401 errors?

Verify the linkrunner-key header validation in your code
Check your private key matches the one in your dashboard settings

Missing data in payload?

name, phone, and email require you to pass user_data to the SDK’s .signup() or .trigger() methods
user_id requires SDK configuration to be passed
Device identifiers (gaid/idfa) depend on user consent and SDK implementation
additional_data requires passing a data object to the SDK and contains those custom parameters

Need help? Contact support@linkrunner.io

Getting Started

SDK Guides

Core Features

Ad Networks

Analytics Integrations

Ecommerce Manager

API Reference

Billing

FAQ

Overview

Configuration

Setting Up Your Webhook URL

Testing Your Endpoint

Webhook Events

Install Webhook

Payload Structure

Headers

Body Parameters

Meta Campaign Details

Google Campaign Details

Additional Data

Example Payloads

Install Event

Authentication

Slack Integration

Retry Behavior

Best Practices

Troubleshooting

Getting Started

SDK Guides

Core Features

Ad Networks

Analytics Integrations

Ecommerce Manager

API Reference

Billing

FAQ

Documentation Index

​Overview

​Configuration

​Setting Up Your Webhook URL

​Testing Your Endpoint

​Webhook Events

​Install Webhook

​Signup Webhook

​Payload Structure

​Headers

​Body Parameters

​Meta Campaign Details

​Google Campaign Details

​Additional Data

​Example Payloads

​Install Event

​Signup Event

​Authentication

​Slack Integration

​Retry Behavior

​Best Practices

​Troubleshooting

Overview

Configuration

Setting Up Your Webhook URL

Testing Your Endpoint

Webhook Events

Install Webhook

Signup Webhook

Payload Structure

Headers

Body Parameters

Meta Campaign Details

Google Campaign Details

Additional Data

Example Payloads

Install Event

Signup Event

Authentication

Slack Integration

Retry Behavior

Best Practices

Troubleshooting