Playbook

e_g Playbook For SaaS

A canonical event model for trials, registration, pricing intent, demo requests, and paid plan conversion.

Strategy

How this playbook should be modeled.

SaaS tracking should separate acquisition signals from product milestones.EVENTS Gatewaylets the marketing site and the product emit a shared canonical event language.

Core Events

Recommended canonical events.

These are the main e_g events this funnel should emit consistently.

PageViewViewContentLeadCompleteRegistrationStartTrialSubscribeContact

Implementation

Example e_g calls.

Use this as a starting point, then enrich payloads with your own business identifiers.

window.e_g("CompleteRegistration", {
  properties: {
    registration_type: "workspace_signup",
    plan_context: "starter"
  }
});

window.e_g("StartTrial", {
  properties: {
    plan_id: "pro-monthly",
    trial_days: 14
  },
  ecommerce: {
    value: 0,
    currency: "USD"
  }
});

window.e_g("Subscribe", {
  properties: {
    plan_id: "pro-monthly",
    billing_period: "monthly"
  },
  ecommerce: {
    value: 49,
    currency: "USD",
    order_id: "SUB-1001"
  }
});

Recommendations

What to keep consistent.

These habits reduce platform mismatch and make downstream routing simpler.

Recommendation

Separate trial start from paid subscription clearly.

Recommendation

Use CompleteRegistration for actual account creation, not just email capture.

Recommendation

Send plan_id and billing_period to make downstream reporting easier.