Cloudflare Queues: review where lead data lives
On October 12, 2026, Cloudflare announced jurisdiction selection for Queues: EU, US and FedRAMP.
On October 12, 2026, Cloudflare announced jurisdiction selection for Queues: EU, US and FedRAMP. Provider announcement. Its URL contains a September date, but the visible publication date is October 12. Checked October 13.
What advertisers should review
If leads or events pass through a queue, map the whole route: form, receiver, queue, consumer, CRM, logs and backups. This is our architectural review recommendation, not a claim that AffiliateCore uses this service.
The documentation says jurisdiction is fixed at creation; consumers may operate elsewhere. Selecting a queue region therefore does not establish compliance for the entire system.
Ask an engineer which fields the message actually needs. Avoid duplicating contact details throughout technical logs. Document access, retention and deletion separately. A country or contractual requirement needs assessment across the complete route, not just the region label in a dashboard.
Test a change safely
Using non-production data, reconcile accepted messages, processed events, duplicates and failures. Preserve an event identifier so a repeat does not create a second lead. This is a recommended consumer check, not a promise of automatic Cloudflare deduplication.
A production migration needs its own switch-over and rollback plan, owner and stop condition. Do not remove the old queue before reconciling its outstanding messages. The useful deliverable is a data-flow map and a decision on whether a change is necessary at all. This news does not introduce an AffiliateCore feature.