Shared deployment keys
One key. Every matching component placement.
Reuse one organization-scoped deployment key anywhere the same React, Vue, Svelte, or other interactive component should appear—even across pages or multiple times on one page.
One deploy atomically sends identical component HTML to every matching section and row. Use different keys only when placements should release independently.
Deployment fan-out
Deploy once instead of updating placements one by one
The shared key defines an atomic deployment group inside your organization.
Across multiple pages
Put the same key on matching sections or rows throughout a campaign, product family, or content collection.
More than once on one page
Reuse the key in multiple page positions when the same component belongs in more than one part of the experience.
All-or-nothing updates
Every matching target receives identical stored HTML. If one target cannot update, the whole deployment rolls back.
Give every rendered placement its own stable mount ID
Shared source does not mean duplicate DOM identifiers.
Use {{ deployment_instance_id }} in the component mount ID and every instance-specific DOM lookup. StaticPagesApi replaces it at render time with a stable value such as section-5914 or row-18203, so each placement initializes independently.
From one artifact to every matching target
StaticPagesApi deployment fan-out and destination publishing are related, but distinct, steps.
Place the shared key
Assign one key to every section or row that should receive the same component source.
Build one artifact
Compile the interactive component with tokenized mount IDs and instance-specific initialization.
Deploy atomically
PATCH the key once. StaticPagesApi updates every matching section and row with identical HTML in one transaction.
Publish affected pages
After fan-out succeeds, deduplicated webhooks publish affected pages to WordPress, Shopify, Rails, or another destination.
One release group, many rendered instances
Use the key boundary to match how your components ship.
Reuse a key when placements should always receive the same artifact. Choose different keys when components need independent release timing or different HTML. Each section or row remains a separate deployment target and counts separately toward your plan quota.
FAQ
Shared deployment-key questions
How placement fan-out, instance IDs, quotas, and destination publishing work together.
Yes. Put one organization-scoped deployment key on every matching target, whether those placements span multiple pages or repeat on the same page. One deploy atomically updates them all.
Use {{ deployment_instance_id }} in mount IDs and DOM lookups. Each section or row receives a stable unique value and must initialize independently.
No. Every placement counts separately toward the deployment-target quota, even when several placements share a key.
The deployment first fans out within StaticPagesApi. After it succeeds, publishing webhooks send each affected rendered page to WordPress, Shopify, Rails, or another configured destination.