Cross-Channel Orchestration Comprehensive Playbook — Sequencing, Frequency, Suppression, Identity Stitching

Cross-channel orchestration is the practice of coordinating customer experience across paid media, email, SMS, push, in-app, web, and direct mail — so each touchpoint reinforces rather than duplicates the others. The four operating disciplines: sequencing (which channel fires when), frequency (how often across all channels combined), suppression (when to stop touching a customer), and identity stitching (recognizing the customer across surfaces).

Most marketing organizations run channels in parallel rather than orchestrated. Email team sends a campaign. Paid social team runs retargeting against the same segment. SMS team triggers a flow. The customer receives the email, sees the ad, gets the text, all within an hour — without any coordination. Cross-channel orchestration is the discipline of moving from parallel to sequential, where each touchpoint advances the customer rather than competing for their attention.

The four orchestration disciplines

  • Sequencing — decide which channel fires first for a given trigger, then which channels follow if the first fails
  • Frequency capping — total touches per customer per day across all channels, not per-channel
  • Suppression — when a customer converts, all open campaigns must stop targeting them within minutes
  • Identity stitching — recognize the customer across email, mobile, web, paid media so suppression and frequency work

Sequencing patterns

  • Email first → SMS escalation → Push fallback — typical for time-sensitive triggers (abandonment, restock)
  • Paid retargeting first → email reminder → direct mail at 30 days — for long-consideration purchases
  • In-app message → push → email if uninstalled — for mobile app lifecycle
  • Push if app open → SMS if not → email fallback — engagement-rank ordering
  • Tier-based sequencing — VIPs get high-touch channels, casuals get email-only
  • Time-of-day sequencing — push during day, email overnight, SMS only during business hours

Frequency capping across channels

The honest implementation requires a single source of truth for touches across channels. CDP-mediated frequency is the standard pattern:

  • CDP tracks every touch — paid impression, email send, SMS send, push delivery, direct mail drop
  • Frequency policy — e.g., 'no more than 3 marketing touches per customer per day across all channels'
  • Each channel queries CDP before firing — if cap exceeded, skip
  • Priority order — when capped, which channels deprioritize first
  • Channel-specific caps within global cap — e.g., 'global cap of 3, of which max 1 SMS, max 5 paid impressions'

Suppression — the underrated discipline

  • Post-purchase suppression — when customer purchases, all open acquisition campaigns suppress within 15 minutes
  • Post-conversion paid suppression — custom audience exclusion lists synced hourly to ad platforms
  • Post-engagement email suppression — clicked through email; suppress the rest of the campaign sequence
  • Subscription state changes — paused, cancelled, unsubscribed; suppress immediately across all marketing channels
  • Active support ticket suppression — don't send promotional content to customers with open complaint tickets
  • Negative review suppression — pause marketing to customers who left 1-star review until customer success follows up
  • VIP suppression from discount campaigns — don't discount-spam your best customers

RGM Experts Say

The single most common gap in cross-channel orchestration: post-purchase suppression lag. Customer buys at 2pm. The Meta retargeting campaign targeting cart abandoners doesn't refresh until midnight. From 2pm to midnight, the customer keeps seeing 'come back!' ads after they already bought. Average loss: 0.5–2% of paid spend on every BFCM. Hourly suppression sync is the fix.

Identity stitching for orchestration

  • Customer ID as the universal key — every channel writes to the customer record using a single customer ID
  • Hashed email as the cross-channel bridge — email available in CRM, ESP, paid social custom audiences
  • Phone number as the SMS-to-paid bridge
  • Device ID / MAID where available — for mobile app to paid mobile
  • Login as the gold standard — authenticated users have all identifiers tied together
  • CDP as the stitching engine — Segment, mParticle, Tealium, Rudderstack, Hightouch (reverse-ETL)

Tool stack for orchestration

  • Customer Data Platform (CDP) — Segment, mParticle, Tealium, Rudderstack, Hightouch
  • Engagement platform — Braze, Iterable, Customer.io, Klaviyo for DTC, Salesforce Marketing Cloud for enterprise
  • Identity resolution — LiveRamp, Acxiom for offline-to-online, plus internal identity graph
  • Reverse ETL — Hightouch, Census for syncing warehouse-segmented data to ad platforms
  • Ad platform suppression APIs — Customer Match, Custom Audiences, customer lists
  • Decision engine — Adobe Journey Optimizer, Salesforce Journey Builder for branching logic

Operating cadence

  • Daily — suppression sync to ad platforms; frequency cap report
  • Weekly — channel sequence health review; over-touched customer reports
  • Monthly — orchestration audit; ensure new campaigns honor existing sequence and suppression rules
  • Quarterly — frequency policy review; update based on response rate data

Related guides

Sources

  1. [1]Braze, Iterable, Customer.io documentation; mParticle and Segment orchestration patterns