Update a personalization slot
Update a personalization slot variant in place — send only the fields you want to change; at least one is required. Omitted fields keep their stored values, so editing the copy never silently re-ranks a variant or brings a paused one back. Set active to false to stop serving a variant without deleting it. Updated content is re-checked against the same markup rules as create. Owner or admin only; returns 404 when no variant with that id exists in this tenant.
Authorizations
Dashboard JWT token from Clerk
Headers
Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
Slot-variant id (perso_ + 32 hex characters), as returned by create or list.
Body
Move the variant to a different slot key.
1 - 100^[a-z0-9-_]+$Retarget the variant at another segment, or null for the default content.
champion, high_value_engaged, engaged, new, passive, at_risk, dormant, lost, null Replacement markup or text for the slot.
1 - 5000New call-to-action destination (http or https), or null to clear.
500New call-to-action label, or null to clear.
200New variant name, or null to clear.
50New tie-breaker rank (0–100) — highest wins.
0 <= x <= 100Set false to stop serving the variant, true to resume.
Replacement free-form key/value data.