From 2a73a771f16448f7a8b2811d37eec8a5966d49cc Mon Sep 17 00:00:00 2001 From: Darshil Rathod <69842641+RathodDarshil@users.noreply.github.com> Date: Thu, 23 Jul 2026 20:06:56 +0530 Subject: [PATCH] LIN-2090: document organic signup webhooks --- features/webhooks.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/features/webhooks.mdx b/features/webhooks.mdx index 141307b..ab1108b 100644 --- a/features/webhooks.mdx +++ b/features/webhooks.mdx @@ -56,7 +56,7 @@ Linkrunner sends webhooks for the following events: 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, user identity fields such as `user_id`, `name`, `phone`, `email`, and `additional_data` are only included in signup webhooks. -By default, install webhooks fire only for attributed (paid) installs. To also receive webhooks for organic installs, enable **Send webhooks for organic installs** in [Settings → Webhooks](https://dashboard.linkrunner.io/settings?s=webhooks). Organic install webhooks are sent with `network_name` set to `ORGANIC`, `ad_channel` set to `null`, and no campaign details. +By default, install webhooks fire only for attributed (paid) installs. To also receive webhooks for organic users, enable **Send webhooks for organic users** in [Settings → Webhooks](https://dashboard.linkrunner.io/settings?s=webhooks). This covers both install and signup webhooks. Organic webhooks are sent with `network_name` set to `ORGANIC`, `ad_channel` set to `null`, and no campaign details. 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. @@ -72,6 +72,8 @@ The `signup` webhook is triggered when you call the `.signup()` method in your a 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. +Like install webhooks, signup webhooks fire only for attributed users by default. Enabling **Send webhooks for organic users** also delivers signup webhooks for organic users, with `network_name` set to `ORGANIC` and no campaign details. + Use the signup webhook for: - Linking attribution data to your user records - CRM integration and user onboarding flows @@ -237,7 +239,7 @@ Example: ### Install Event (Organic) -Sent only when **Send webhooks for organic installs** is enabled: +Sent only when **Send webhooks for organic users** is enabled: ```json {