Skip to content
pipeo
Menu

Use cases

Use cases

Examples of how sources, destinations and connections fit together. Names and events are illustrative.

Product analytics fan-out

A web app and a mobile app send to one source each; both connect to GA4 and Mixpanel.

Example setup

  • Source: Web app
  • Source: Mobile app
  • Destination: Google Analytics 4
  • Destination: Mixpanel

Warehouse feed

Every event lands as hourly files in your bucket for the warehouse to load.

Example setup

  • Source: Backend
  • Destination: Amazon S3 file sink
  • Connection: all event types
  • Loader dedupes on messageId

Internal services by webhook

Billing and support tools get only the events they care about, signed.

Example setup

  • Destination: Webhook to billing
  • Filter: track events Order Completed and Subscription Started
  • Dropped field: context.ip
  • Signing secret set

Backfill a new destination

A destination added today gets last month’s events from the archive.

Example setup

  • Add the destination and connect it
  • Run a connection test
  • pipeo replay with a 30-day window
  • Cap the rate with --max-per-second

Send once, deliver everywhere

Sign in, create a source, connect your destinations and change one host setting in your SDK.