Express<\/a>:<\/p>\n\n\n\nimport express from "express";\nimport crypto from "crypto";\n\nconst app = express();\napp.use("\/webhooks", express.raw({ type: "application\/json" }));\n\nconst WEBHOOK_SECRET = process.env.TOLINKU_WEBHOOK_SECRET; \/\/ whsec_...\n\nfunction verifySignature(payload, signature) {\n const expected = crypto\n .createHmac("sha256", WEBHOOK_SECRET)\n .update(payload)\n .digest("hex");\n const sig = Buffer.from(signature, "hex");\n const exp = Buffer.from(expected, "hex");\n if (sig.length !== exp.length) return false;\n return crypto.timingSafeEqual(sig, exp);\n}\n\n\/\/ Event handlers mapped by type\nconst handlers = {\n "link.clicked": handleClick,\n "deferred_link.claimed": handleDeferredClaim,\n "install.tracked": handleInstall,\n "referral.created": handleReferralCreated,\n "referral.completed": handleReferralCompleted,\n};\n\napp.post("\/webhooks\/tolinku", async (req, res) => {\n const signature = req.headers["x-webhook-signature"];\n\n if (!signature || !verifySignature(req.body, signature)) {\n return res.status(401).json({ error: "Invalid signature" });\n }\n\n const event = JSON.parse(req.body.toString());\n\n \/\/ Respond immediately, process async\n const handler = handlers[event.event];\n if (handler) {\n res.status(200).json({ status: "accepted" });\n handler(event).catch(console.error);\n } else {\n res.status(200).json({ status: "unhandled" });\n }\n});\n<\/code><\/pre>\n\n\n\nThe handler responds with 200<\/code> before processing the event. Tolinku retries failed deliveries on a schedule of 1 minute, 5 minutes, and 30 minutes, so you may receive duplicates if your endpoint is temporarily unavailable. Build your handlers to be idempotent: processing the same event twice should produce the same result as processing it once.<\/p>\n\n\n\nFor idempotency, you can hash the event payload (since the envelope does not include a unique event ID) and store processed hashes in Redis or your database:<\/p>\n\n\n\n
async function isDuplicate(event) {\n const hash = crypto\n .createHash("sha256")\n .update(JSON.stringify(event))\n .digest("hex");\n const exists = await redis.get(`webhook:${hash}`);\n if (exists) return true;\n await redis.set(`webhook:${hash}`, "1", "EX", 86400); \/\/ 24h TTL\n return false;\n}\n<\/code><\/pre>\n\n\n\nIntegration Patterns<\/h2>\n\n\n\nAnalytics Sync<\/h3>\n\n\n\n
Push click and install data to your analytics warehouse:<\/p>\n\n\n\n
async function handleClick(event) {\n await analyticsDB.insert("deep_link_clicks", {\n prefix: event.data.prefix,\n token: event.data.token,\n campaign: event.data.campaign,\n platform: event.data.platform,\n device_type: event.data.device_type,\n timestamp: event.timestamp,\n });\n}\n<\/code><\/pre>\n\n\n\nCRM Updates<\/h3>\n\n\n\n
Update user profiles when installs arrive:<\/p>\n\n\n\n
async function handleInstall(event) {\n await crm.createOrUpdate({\n source: "deep_link",\n campaign: event.data.campaign,\n platform: event.data.platform,\n first_seen: event.timestamp,\n });\n}\n<\/code><\/pre>\n\n\n\nReferral Reward Fulfillment<\/h3>\n\n\n\n
Trigger rewards when referrals complete:<\/p>\n\n\n\n
async function handleReferralCompleted(event) {\n await rewardService.issueReward(event.data.referrer_id, {\n type: "referral_bonus",\n referred_user: event.data.referred_user_id,\n milestone: event.data.milestone,\n });\n\n await slack.send("#referrals", {\n text: `Referral ${event.data.referral_code} completed. ` +\n `${event.data.referrer_id} referred ${event.data.referred_user_id}.`,\n });\n}\n<\/code><\/pre>\n\n\n\nChoosing Which Events to Subscribe To<\/h2>\n\n\n\n
When creating a webhook in Tolinku, you select exactly which event types your endpoint should receive. The webhook creation form lets you check or uncheck individual event types.<\/p>\n\n\n\n
Here is a decision framework:<\/p>\n\n\n\n
Subscribe to link.clicked<\/code> if<\/strong> you need real-time click analytics, want to detect click fraud, or need to trigger actions immediately on link interaction.<\/p>\n\n\n\nSubscribe to deferred_link.claimed<\/code> if<\/strong> you are building onboarding flows that depend on the original deep link context, or need to track deferred deep link attribution quality.<\/p>\n\n\n\nSubscribe to install.tracked<\/code> if<\/strong> you are tracking user acquisition, attributing installs to campaigns, or triggering welcome sequences for users who arrived via deep links.<\/p>\n\n\n\nSubscribe to referral.created<\/code> if<\/strong> you are monitoring referral program participation, tracking how many users generate referral links, or syncing referral data to external CRM systems.<\/p>\n\n\n\nSubscribe to referral.completed<\/code> if<\/strong> you are fulfilling referral rewards, tracking referral conversion rates, or notifying teams when referrals convert.<\/p>\n\n\n\nIf you are just getting started, begin with link.clicked<\/code> and install.tracked<\/code>. These two events give you the most actionable data with the least handler complexity. Add referral events as your integration matures.<\/p>\n\n\n\nError Handling and Retry Logic<\/h2>\n\n\n\n
Webhook deliveries can fail. Your server might be down, or a transient database error might cause a 500 response. Tolinku retries failed deliveries up to three times with increasing delays: 1 minute, 5 minutes, and 30 minutes after the initial failure. Your handler needs to be resilient to duplicates and graceful with errors.<\/p>\n\n\n\n
A defensive handler wraps processing in a try\/catch and logs failures without crashing:<\/p>\n\n\n\n
app.post("\/webhooks\/tolinku", async (req, res) => {\n \/\/ ... signature verification ...\n\n const event = JSON.parse(req.body.toString());\n res.status(200).json({ status: "accepted" });\n\n try {\n const handler = handlers[event.event];\n if (handler) await handler(event);\n } catch (err) {\n console.error(`Failed to process ${event.event}:`, err);\n \/\/ Queue for retry via your own job system\n await retryQueue.add({ event, attempts: 0 });\n }\n});\n<\/code><\/pre>\n\n\n\nAlways respond with 200<\/code> before processing. If you respond with a non-2xx status, the platform will retry, and you could end up processing the event multiple times once your system recovers.<\/p>\n\n\n\nNext Steps<\/h2>\n\n\n\n
Webhook event types are the building blocks of a connected deep linking system. Each event type represents a specific moment in the user journey, and each carries the data you need to act on that moment. Start with the events that map to your most important business metrics, build handlers that are idempotent and fast, and expand your subscriptions as your integration needs grow.<\/p>\n\n\n\n
To configure webhooks<\/a> in your Tolinku Appspace, visit the webhook settings page and select the event types you need. The event types documentation<\/a> has the full payload reference for each type.<\/p>\n","protected":false},"excerpt":{"rendered":"Understand webhook event types for deep linking. Learn which events to subscribe to and how to handle click, install, and referral payloads.<\/p>\n","protected":false},"author":2,"featured_media":1118,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Webhook Event Types for Deep Linking Platforms","rank_math_description":"Understand webhook event types for deep linking. Learn which events to subscribe to and how to handle click, install, and referral payloads.","rank_math_focus_keyword":"webhook event types","rank_math_canonical_url":"","rank_math_facebook_title":"","rank_math_facebook_description":"","rank_math_facebook_image":"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/og-webhook-event-types.png","rank_math_facebook_image_id":"","rank_math_twitter_title":"","rank_math_twitter_description":"","rank_math_twitter_image":"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/og-webhook-event-types.png","footnotes":""},"categories":[15],"tags":[37,62,20,264,265,263,69,61],"class_list":["post-1119","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-engineering","tag-analytics","tag-api","tag-deep-linking","tag-engineering","tag-events","tag-integrations","tag-mobile-development","tag-webhooks"],"_links":{"self":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/1119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/comments?post=1119"}],"version-history":[{"count":2,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/1119\/revisions"}],"predecessor-version":[{"id":2250,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/1119\/revisions\/2250"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/media\/1118"}],"wp:attachment":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/media?parent=1119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/categories?post=1119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/tags?post=1119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Tolinku](\"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/platform-webhooks.png\")
\nThe webhooks page with create form, webhook list, and delivery log.<\/em><\/p>\n\n\n\n