Track trial conversions in Email
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
02pipeline · 1 steps
- 01ENRenrich.entitycustomer → company · seats · source
03destinations · 1
- toemail.outEmailtoalerts@acme.com
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.
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 Email
Send a transactional email to one or more recipients, addressable from event fields.
- 01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
- 02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
- 03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.
From: mail@notify.ingestlayer.com To: alerts@acme.com Subject: Payment failed — acme-inc (€240.00) A charge failed for acme-inc. amount €240.00 reason insufficient_funds attempt 2
notes
- Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
- Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
- Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that 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.
trial conversions, routed elsewhere
- Track trial conversions in SlackSlack
- Track trial conversions in DiscordDiscord
- Track trial conversions in TelegramTelegram
- Track trial conversions in WebhookWebhook
- Track trial conversions in PostgresPostgres
- Track trial conversions in NotionNotion
more, into Email
- Track user signups in Emailtrack
- Monitor failed payments in Emailmonitor
- Route support escalations in Emailalert
- Track waitlist signups in Emailtrack
- Track new subscriptions in Emailtrack
- Track canceled subscriptions in Emailtrack
- Track successful payments in Emailtrack
- Track form submissions in Emailtrack
- Track feature usage in Emailtrack
- Track file uploads in Emailtrack
- Monitor failed logins in Emailmonitor
- Monitor usage-limit hits in Emailmonitor
- Monitor error spikes in Emailmonitor
- Monitor cron-job health in Emailmonitor
- Monitor CI/CD build status in Emailmonitor
- Flag high-value leads in Emailalert
- Catch churn-risk signals in Emailalert
- everything you can pipe to Emailhub