Do I need a separate call for every plan?

No. Emit one user.signed_up event with a plan field, then branch on it in the pipeline if you want different destinations per plan.

What if the same signup fires twice?

Pass the user id as idempotencyKey. The gate enforces (project, key) uniqueness, so a retry or double-submit counts once.

Can I enrich the signup before it lands?

Yes — the enrich.person action resolves the email to company, role, and country in flight, so the alert arrives already annotated.

ingestlayer/recipes/v0.4

Track user signups in Webhook

Know the moment someone signs up — who they are, which plan they picked, and where they came from — without waiting for a daily export or tailing logs.

01source

sourcesdk.eventTypeScript SDK

matchuser.signed_up

02pipeline · 2 steps

01ENRenrich.personemail → company · role · country
02MUTredact.piiemail + ip masked per destination

03destinations · 1

towebhook.outWebhook
urlhttps://api.acme.com/hooks

the event

You emit user.signed_up with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

user_idstringyour internal id
emailstring
planstringfree | pro | scale
sourcestringwhere they came from
created_atstringISO 8601

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit user.signed_up

import { ingest } from "@ingestlayer/sdk";

await ingest("user.signed_up", {
  user_id: user.id,
  email:   user.email,
  plan:    user.plan,
  source:  "marketing-site",
}, {
  idempotencyKey: user.id,   // one signup per user, ever
});

route it to Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

questions

Do I need a separate call for every plan?: No. Emit one user.signed_up event with a plan field, then branch on it in the pipeline if you want different destinations per plan.
What if the same signup fires twice?: Pass the user id as idempotencyKey. The gate enforces (project, key) uniqueness, so a retry or double-submit counts once.
Can I enrich the signup before it lands?: Yes — the enrich.person action resolves the email to company, role, and country in flight, so the alert arrives already annotated.

build this pipeline or read the quickstart →