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 Telegram

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

totelegramTelegram
chat@oncall

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 Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

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 →