ingestlayer/recipes

Track trial conversions in Slack

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

  • toslackSlack
    channel#alerts

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 Slack

Post to any channel in your workspace. Connect once with OAuth, pick the channel per pipeline.

  1. 01

    connect your workspace

    Authorize the ingestlayer Slack app over OAuth from the destinations page. We hold only a channel-scoped bot token, in-region, in the same KMS as your other credentials.

  2. 02

    pick a channel

    Choose any public channel, or invite the bot to a private one. The channel is set per pipeline, so different events can land in different places.

  3. 03

    map the message

    Reference event fields with $event.* in the message template. The default renders a titled block with the event name and its key fields.

in slackdelivered
┌─ #alerts ──────────────────────────────┐
│  ingestlayer  APP                       │
│  user.signed_up                         │
│  email   ada@acme.com                   │
│  plan    pro                            │
│  source  marketing-site                 │
└─────────────────────────────────────────┘

notes

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 pipelineor read the quickstart →

trial conversions, routed elsewhere

more, into Slack