Can I see which trials convert fastest?

The trial_days field travels with the event; land it in Postgres and the cohort math is a query away.

How do I credit the right channel?

enrich.entity restores the original acquisition source, so the conversion alert names where the customer first came from.

Should I also track trials that don't convert?

Yes — pair this with a trial.expired event and a churn-risk pipeline to catch the ones slipping away.

ingestlayer/recipes/v0.4

Track trial conversions in Postgres

Know the moment a trial turns into a paying plan — the clearest signal your activation is working — and route it to the people who made it happen.

01source

sourcesdk.eventTypeScript SDK

matchtrial.converted

02pipeline · 1 steps

01ENRenrich.entitycustomer → company · seats · source

03destinations · 1

towarehouse.pgPostgres
tableevents.signups

the event

You emit trial.converted 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.

customer_idstring
planstring
trial_daysnumberlength of trial
mrrnumberminor units

emit it

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

emit trial.converted

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

await ingest("trial.converted", {
  customer_id: sub.customer,
  plan:        sub.plan.nickname,
  trial_days:  daysBetween(sub.trial_start, sub.trial_end),
  mrr:         sub.plan.amount,
}, {
  idempotencyKey: sub.id,
});

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

Can I see which trials convert fastest?: The trial_days field travels with the event; land it in Postgres and the cohort math is a query away.
How do I credit the right channel?: enrich.entity restores the original acquisition source, so the conversion alert names where the customer first came from.
Should I also track trials that don't convert?: Yes — pair this with a trial.expired event and a churn-risk pipeline to catch the ones slipping away.

build this pipeline or read the quickstart →