EventSend Client Workspace Setup (Onboarding)

EventSend Client Workspace Setup (Onboarding)

1. 01

   Create the client workspace and confirm the plan ceiling before wiring anything

   The Free tier caps at 2,500 events/month, 2 seats, 3 team destinations, and 1 source with 7-day retention. Starter at $12/mo raises this to 50,000 events/month, unlimited seats, unlimited destinations, unlimited sources, and 30-day retention. Growth at $29/mo covers 150,000 events/month. Pick the tier from the client's expected monthly event volume, not from the seat count, because seats stop being the constraint from Starter upward.

2. 02

   Generate a route token and hand the client's developer the single es_ endpoint

   Every route issues an es_ token. The client POSTs a small JSON payload to that one endpoint instead of maintaining separate integrations per destination. Keep the token in the agency's password manager and issue a separate route per client so a revoked token never touches another account.

3. 03

   Attach an optional unique key to every event that must not duplicate

   Idempotent ingestion depends on the unique key. Set it on checkout, failed payment, and form-submit events so a retried client request does not fire a second Slack alert or a second downstream webhook. Events without a key are logged but not deduplicated.

4. 04

   Fan out to the client's destinations and confirm each one receives

   Route to Slack, Discord, Telegram, Pushover, web push, or a custom webhook. Send one test event per destination and have the client confirm receipt in their own channel before you call the route live. The Free tier allows 3 team destinations and 1 source, so a multi-channel client needs Starter.

5. 05

   Connect inbound third-party webhooks through the same pipeline

   Stripe, GitHub, and Vercel webhooks can be received without backend code. Point the vendor's webhook settings at the EventSend route so third-party events land in the same log, retry queue, and alerting path as first-party product events.

6. 06

   Configure retry logic, rate limiting, and alerting thresholds

   Set the retry behavior for failed deliveries and the rate limit that protects downstream destinations. Turn on alerting so the agency is notified when a destination starts failing, rather than hearing about it from the client.

7. 07

   Document the routing map and hand the client a written runbook

   Record every source, route token, destination, and unique-key rule in one page. Note the retention window the client is on (7 days on Free, 30 days on Starter) so they know how far back they can query. Flag that EventSend does not publish white-label branding, so client-facing alerts and dashboards will show the EventSend brand.