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 Notion

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

tonotion.dbNotion
databaseSignups

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 Notion

Append events as rows to a Notion database, or content to a page. Connect once with OAuth, pick the target per pipeline.

01
connect your workspace
Authorize the ingestlayer Notion integration over OAuth from the destinations page, then choose which databases and pages it may touch. We hold only that workspace's access token, in-region, in the same KMS as your other credentials.
02
pick a target
Per pipeline, choose a database to append a typed row to, or a page to append content to. The picker lists exactly what you shared with the integration during authorization — nothing else.
03
map the columns
For a database, match event fields to Notion properties — automatically by column name, or per-column with $event.* templates. The title column falls back to the event name, so a row is never blank. For a page, the rendered body is appended as blocks.

in notiondelivered

┌─ Signups · database ───────────────────┐
│  Name        ada@acme.com               │
│  Plan        ● pro                       │
│  Source      marketing-site             │
│  Signed up   2026-06-03                  │
└─────────────────────────────────────────┘

notes

Notion grants access page by page: the integration only sees databases and pages you explicitly share during authorization. Add the target there, or the delivery dead-letters as object_not_found.
Each column is coerced to its Notion type — number, date, select, checkbox, URL, and so on. Properties an integration can't write (people, relations, files, formulas, rollups) are skipped rather than guessed.
Title and rich-text values cap at 2000 characters per block and are chunked beyond that; a single page append tops out at 100 blocks.
Tokens don't expire, but revoking the integration inside Notion flips the destination to an error state — reconnect from the destinations page to resume delivery.

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 →