RevTurbineCheckoutMetadataBag
The Stripe Checkout revturbine_* metadata bag for a rendered output
(plan 282 REQ-5; research §6.2). String-valued and Stripe-shaped: spread it
into a Checkout Session’s metadata and subscription_data.metadata as-is.
A key the SDK does not hold is ABSENT, never empty or a placeholder — Stripe reads an empty metadata value as an unset, and an invented id would be worse than a gap on the attribution side.
Properties
Section titled “Properties”revturbine_account_id?
Section titled “revturbine_account_id?”
optionalrevturbine_account_id?:string
The identified account, redacted like the wire lanes. Absent when none was identified — never the user-derived fallback the interaction lane labels.
revturbine_decision_id?
Section titled “revturbine_decision_id?”
optionalrevturbine_decision_id?:string
PlacementOutput.decision_id.
revturbine_output_id
Section titled “revturbine_output_id”revturbine_output_id:
string
PlacementOutput.output_id — the rendered payload / treatment.
revturbine_placement_id
Section titled “revturbine_placement_id”revturbine_placement_id:
string
The placement whose CTA led to checkout — what confirms credit to it.
revturbine_plan_handle?
Section titled “revturbine_plan_handle?”
optionalrevturbine_plan_handle?:string
The plan the CTA converts onto (cta_path.plan_handle), when it names one.
revturbine_rule_id?
Section titled “revturbine_rule_id?”
optionalrevturbine_rule_id?:string
PlacementOutput.rule_id — the rule handle the interaction lanes stamp as rule_handle.
revturbine_user_id?
Section titled “revturbine_user_id?”
optionalrevturbine_user_id?:string
The id identify() set, as this SDK’s own telemetry carries it: an
email-shaped id is hashed the same way on every lane, so the purchase
joins the presentation and click rows. Absent for an unidentified user.