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 Webhook

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

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

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

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 →