Event guide

Connect account outcomes to a Customer.

Use the Web SDK for pricing views, feature views and signup intent. Send actual account, verification, workspace, trial and plan outcomes only from your server after your system records them.

  1. Create or resolve a Customer Profile with audience:write. Profile creation alone does not mean signup or marketing consent.
  2. Create a Site-bound or organization-wide key with saas:write. Keep it on your server. Include the active siteId and the Profile ID with every fact.
  3. Call POST /v1/saas/events after your account or billing transaction commits. Reuse the same idempotency key for retries.
  4. Read the receipt through the Analytics API. Accepted ingestion and downstream Journey execution are separate states.
curl https://api.fendsy.com/v1/saas/events   -H "Authorization: Bearer $FENDSY_SAAS_API_KEY"   -H "Content-Type: application/json"   -H "Idempotency-Key: account-created-42"   -d '{"kind":"account_created","siteId":"SITE_ID","customerProfileId":"PROFILE_ID","accountId":"account-42"}'

Supported server outcomes are account_created,email_verified, workspace_created,trial_started, trial_ended,plan_activated, plan_renewed andplan_cancelled. Trial and plan events require their typed plan or subscription IDs. Unknown and private fields are rejected.

Browser actions stay intent signals. Governed custom.saas.*events can be inspected before activation; a browser report cannot claim a verified account or billing outcome. These events never grant email marketing consent. Use Audience for consent and eligibility.

A SaaS account needs no Catalog Item. If you sell a product or service, use the separate confirmed order contract.