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 Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 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

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 →