Zero-downtime migration: how to switch to Sply in one day

The primary concern when upgrading tracking infrastructure is operational risk: breaking active campaigns, corrupting conversion data through duplicate events, or facing gateway latency during peak traffic.

Sply follows a Zero-Downtime Migration Protocol to ensure continuous tracking and parallel validation throughout the transition.

---

1. 4-phase migration roadmap#

┌──────────────────────────────────────────────────────────────────────────┐
│ PHASE 1: TAG INVENTORY & AUDIT (1 Hour)                                  │
│ • Catalog existing conversion triggers, pixel IDs, and custom schemas     │
├──────────────────────────────────────────────────────────────────────────┤
│ PHASE 2: SHADOW MODE VALIDATION (2–4 Hours)                              │
│ • Stream parallel server events via Sply without disabling legacy tags   │
│ • Validate deduplication using shared event_id keys                      │
├──────────────────────────────────────────────────────────────────────────┤
│ PHASE 3: SEAMLESS DNS TRANSITION (15 Minutes)                            │
│ • Activate Sply Edge fleet via DNS record update with zero traffic loss  │
├──────────────────────────────────────────────────────────────────────────┤
│ PHASE 4: FINAL TELEMETRY ACCEPTANCE (1 Hour)                             │
│ • Verify Event Match Quality (EMQ) and sub-50ms edge response latency   │
└──────────────────────────────────────────────────────────────────────────┘

---

2. Execution protocol#

Phase 1: Event schema mapping#

Document key events across the conversion funnel:

• PageView
• ViewContent
• AddToCart
• Purchase (checking currency, value, order_id)

Phase 2: Parallel shadow validation#

1. Client-side tags and the Sply gateway send identical events stamped with a shared event_id.
2. Meta Events Manager and GA4 detect the dual stream and deduplicate incoming hits into a single verified conversion with full match parameters.

Phase 3: Edge DNS delegation#

Add a CNAME or A-record to your DNS. Incoming requests transition smoothly to Sply edge nodes with no interruption to traffic.

Phase 4: Production verification#

Verify telemetry metrics in the Sply dashboard:

• Meta CAPI Delivery Status: 100% Success.
• Edge Latency: < 35 ms.
• Click-to-Session Discrepancy: < 1%.

---

Next steps#

• Implementation support: Book an Assisted Migration with a Sply Engineer.
• Next in series: Infrastructure reliability, data security, and privacy compliance in Sply.