Use cases

Show me top features used by paid users vs free users

Feature events, account data, and billing status live in different systems. Enspect joins them on demand so product teams can see which features paid users actually value.

Join logic

  • Join usage events to accounts using user_id or account_id
  • Attach plan tier from Postgres (or your app database)
  • Classify paid vs free using Stripe subscription state or entitlements

Output

  • X-axis: time period
  • Y-axis: feature adoption
  • Bars: Free (grouped) · Paid (grouped)

GoalPrioritize roadmap and packaging around what paying customers actually use.

Show conversion funnel from website visits to paid plans

Traffic, leads, onboarding, and billing live in separate tools. Enspect connects Google Analytics, forms, Enspect app events, and Stripe so teams can see exactly where users drop off.

Join logic

  • Map CTA clicks -> leads using session id, campaign, or email
  • Map leads -> Enspect users using email or account id
  • Map onboarded accounts -> paid plans using Stripe customer id

Output

  • X-axis: funnel stage
  • Y-axis: users or accounts
  • Stages: Visits · Clicks · Leads · Onboarded · Paid

GoalFind the biggest conversion leak and fix the step that blocks paid growth.

Show hiring source effectiveness by combining candidate pipeline, hiring outcomes, and cost per source

ATS, HRIS, and finance data rarely agree in one place. Enspect connects candidates, joined employees, and spend so HR can see which channels deliver hires at the lowest cost.

Join logic

  • Map candidates → hires using candidate_id or email
  • Map hires → hiring source (LinkedIn, referral, agency, etc.)
  • Aggregate per source: total_candidates, total_hires, and total_cost

Output

  • X-axis: hiring source
  • Y-axis: count / cost (same chart, grouped bars)
  • Bars: Hires · Cost

GoalIdentify which hiring channels bring the most hires for the lowest cost—the best ROI for HR.

Show ROI by marketing campaign by combining ad spend, user activity, and revenue

Spend, traffic, and revenue are usually split across ads, analytics, and CRM. Enspect links campaign visits to purchases so teams can stop guessing which campaigns actually pay back.

Join logic

  • Map users to campaigns using utm_campaign
  • Link purchases to users via user_id or email
  • Aggregate per campaign: total_spend and total_revenue

Output

  • X-axis: campaign
  • Y-axis: amount
  • Bars: Spend (grouped) · Revenue (grouped)

GoalIdentify which campaigns are profitable and which are wasting money.