Stream link events into your analytics and backend with webhooks
LinkMe webhooks send click, token, claim, app-open, and deferred-claim-attempt events to your own endpoint so you can power attribution pipelines, internal alerts, and downstream analytics without polling APIs.
What you get
- Event subscriptions per webhook so each endpoint gets only what it needs.
- Delivery history per webhook with response status, attempt count, and timing.
- Automatic retry/backoff for retriable failures, with stop conditions.
- Auto-disable when endpoints keep failing to protect your event pipeline.
- Optional HMAC signing secret for endpoint-side verification.
- Choose app-target scope or environment scope; environment webhooks receive events from every app target in that environment.
Event model you can subscribe to
| Event | Why teams subscribe |
|---|---|
| link.click | Track raw click throughput, channel quality, and destination behavior. |
| link.token_created | Observe new token creation for deferred/deep-link lifecycle tracing. |
| link.claim | Monitor successful claims for install/open attribution flows. |
| link.app_open | Record app-open events tied to routing outcomes. |
| link.deferred_claim_attempt | Audit deferred claim attempts and troubleshoot attribution misses. |
Environment scope and product surfaces
Configure an environment webhook when one endpoint should receive events from all app targets in that environment. Surface routing stays in the event data, so the receiver can distinguish paths such as /customer and /staffwithout creating a separate webhook for every surface.
{
"event": "link.click",
"app_id": "target_123",
"data": {
"link_id": "link_456",
"surface": {
"id": "surface_customer",
"name": "Customer",
"path_prefix": "/customer"
}
}
}Common webhook patterns
Analytics forwarding
Receive link events once, then forward them to PostHog, GA4, Segment, or your warehouse with your own mapping rules.
Operational alerts
Trigger internal workflows when claim/open events happen, for example CRM updates or campaign health notifications.
Data enrichment pipeline
Join LinkMe events with your user/account data before storing in BI systems.
Reliable event delivery
Use built-in retries, delivery history, and auto-disable safeguards to keep integrations stable.
Quick implementation flow
- Create a webhook in Developer settings and choose the event types you need.
- Point URL to your ingestion endpoint or automation gateway.
- Enable signing secret and verify signature in your receiver.
- Return `2xx` quickly and process downstream asynchronously.
- Monitor delivery history and fix endpoint issues before retries trigger auto-disable.
Full step-by-step setup, payload reference, and verification code samples are in the Webhooks Guide.
Receiver design that holds up in production
Do this
- Verify signature on the raw body when signing is enabled.
- Return `2xx` quickly and enqueue async processing.
- Make downstream consumers idempotent by `id` and `event`.
- Alert on delivery failure streaks before auto-disable impacts workflows.
Avoid this
- Doing heavy synchronous work before responding.
- Parsing/mutating request body before signature validation.
- Assuming retries always arrive in strict chronological order.
- Ignoring delivery history until campaigns are already affected.
Connect webhooks with attribution QA
For reliable campaign reporting, pair webhook streams with LinkMe attribution checks. Validate campaign URLs in the UTM Debugger before launch, then consume click/claim/open webhook events for server-side analytics and audit trails.