Integration · CDP
Segment
Segment (CDP) is the canonical event router for many consumer subscription apps. Metapolicy ships as a Segment destination so the events you already track — identify, track, screen — flow through as reward signal without your engineering team writing a new instrumentation layer.
The contract
What flows in
- Segment track events: any event you label as a reward (e.g. "Trial Started", "Subscription Purchased") flows into Metapolicy as reward signal
- Segment identify calls: user_id mapping ingested for cross-surface attribution
- Custom mappings: per-event reward_spec keys configured in the Metapolicy dashboard
What flows out
- Lift readouts available as a Segment source — downstream warehouses (Snowflake, BigQuery) ingest LiftReadout rows as a first-class table
- Optional: write decision assignments back as Segment events for downstream personalisation tools
Setup
- 01In Segment Dashboard → Destinations, add Metapolicy (under Analytics)
- 02Provide your environment-scoped Metapolicy API key in the destination settings
- 03Map the events you treat as rewards to reward_spec keys (typically Trial Started, Subscription Purchased, Plan Upgraded)
- 04Optionally enable the reverse direction: LiftReadout → Segment source
- 05Validate by replaying a Segment debugger event and confirming it appears in Metapolicy's decision-log dashboard
Why this is the cheapest possible integration path
If your team already runs Segment, you have a typed event taxonomy. Metapolicy reuses it. No new SDK, no new instrumentation, no new property names — just a destination toggle.
The DR readout is computed against the same events Segment routes to your warehouse, so the numbers reconcile by construction.
Wire Segment in a 30-minute call.
We pair with your engineer, ship the integration live, and run the first decision on your stack.