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 Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 Postgres

Insert each event as a row into a table in your own Postgres.

01
add the connection
Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.
02
point at a table
Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.
03
map columns
Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

in postgresdelivered

INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

The target table must already exist with compatible column types; ingestlayer never runs DDL on your database.
Connections come from fixed EU egress IPs — add them to your firewall, or inserts will time out.
Use a jsonb column for the full payload when your event shape changes often, so a new field never breaks the insert.

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 →