Jurisdictional routing

Description

The pattern that varies decisions by the customer's jurisdiction: which consent regime applies, which retention windows govern, which channel rules dominate, which regulatory carve-outs allow or block specific recipes. Distinct from consent state propagation because jurisdiction is the structural context that determines which consent state is meaningful in the first place. Increasingly required as US state law, EU member state variation, and sectoral regulation create non-uniform compliance terrain.

Common failure modes

• 01Jurisdiction inferred from IP address only, which is unreliable for residents abroad, VPN users, and customers in transit
• 02Jurisdiction captured at signup but never refreshed, so the customer who moves continues to be served under the rules of their old residence
• 03Routing rules encoded across many systems, each implementing the jurisdictional split differently, so the union of rules diverges from any one's intent
• 04Jurisdictional rules represented as if-then logic at the activation layer rather than as a structural attribute on the customer, leaving every downstream system to re-derive jurisdiction

Tools for this pattern

The capability a stack needs to run this pattern, and the vendors that provide it, on Martech Stack Builder.

• NeedsPrivacy Compliance (GDPR/CCPA)
• RelatedData Access Control

Recipes composing this pattern