GrowthRailDocs

Webhook events

EventWhat it signalsGrowth Rail action
user.createdUser signup confirmed by provider.Record signup proof; join to pending SDK attribution claim.

How attribution works

A verified provider event proves the signup happened — but not that the user was referred. Growth Rail completes a referral only when that event joins to the opaque attribution claim previously captured by the SDK on the referring user's device.

Identity rule: Growth Rail joins events to claims using stable IDs and opaque tokens. It never correlates users by email, name, phone number, or billing address.
1

Create the Growth Rail connection

Open Dashboard → Integrations → Auth, choose Kinde, and create a Sandbox or Production connection. Copy the generated webhook endpoint URL — you will paste it into Kinde in the next step.

2

Register the webhook in Kinde

In Kinde → Settings → Webhooks, add the copied endpoint and subscribe to user.created.

Return to Growth Rail and save the Kinde tenant JWKS URL. Growth Rail encrypts and stores it — the raw value is never returned by the API after saving.

Verification tip: Use https://your-subdomain.kinde.com/.well-known/jwks. Growth Rail only fetches HTTPS JWKS URLs hosted under kinde.com and caches public keys briefly.
Security: Never commit webhook secrets to source control or log them. If a secret is compromised, rotate it in both Kinde and Growth Rail immediately.
3

Pass attribution data from your app

Pass the Kinde user ID delivered as data.user.id. The webhook body is a signed JWT rather than JSON.

ts
// Run after Kinde resolves the authenticated user.
await GrowthRail.initAppUser(kindeUser.id);
4

Verify end-to-end in test mode

Create a user in the matching Kinde environment and confirm its signed user.created JWT is accepted by Growth Rail.

OutcomeMeaning
CompletedSignup proof and SDK attribution token matched. The referral reward has been triggered.
Awaiting attributionThe webhook signature was valid, but the SDK claim has not arrived yet — or the stable user ID did not match a pending claim. The event is held; Growth Rail completes the referral when the claim arrives.
IgnoredThe event was verified but no matching attribution claim exists and the hold window has expired, or the event type is out of scope.
Provider-specific notes
  • Kinde user imports do not emit user.created.
  • Kinde webhooks are environment-scoped, so create separate Sandbox and Production connections.