Won't this be far too noisy?

Filter to the handful of features that actually predict expansion; everything else streams to the warehouse without an alert.

Can I spot free users hitting paid features?

The plan field rides along — branch on it to flag free-plan users leaning on paid surfaces, a clean upsell trigger.

How do I roll this up per account?

enrich.entity attaches the account id so usage aggregates cleanly in Postgres by company, not just by user.

ingestlayer/recipes/v0.4

Track feature usage in Webhook

Watch the features that signal expansion — exports, API calls, integrations — and route the moments that hint a customer is ready for more.

01source

sourcesdk.eventTypeScript SDK

matchfeature.used

02pipeline · 2 steps

01CTLfilter.matchfeature in {export, api, webhook}
02ENRenrich.entityuser → account · plan · owner

03destinations · 1

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

the event

You emit feature.used 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_idstring
featurestringfeature key
countnumberuses in window
planstring

emit it

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

emit feature.used

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

await ingest("feature.used", {
  user_id: ctx.user.id,
  feature: "csv.export",
  count:   1,
  plan:    ctx.user.plan,
});

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

Won't this be far too noisy?: Filter to the handful of features that actually predict expansion; everything else streams to the warehouse without an alert.
Can I spot free users hitting paid features?: The plan field rides along — branch on it to flag free-plan users leaning on paid surfaces, a clean upsell trigger.
How do I roll this up per account?: enrich.entity attaches the account id so usage aggregates cleanly in Postgres by company, not just by user.

build this pipeline or read the quickstart →