{"templateId":"markdown","sharedDataIds":{"sidebar":"sidebar-sidebars.yaml"},"props":{"metadata":{"markdoc":{"tagList":["admonition"]},"redocly_category":"Products","product_name":"Journey Orchestration","type":"markdown"},"seo":{"title":"Re-randomize on Re-entry in Journey Orchestration","description":"Configure Treasure Data CDP Journey Orchestration to assign profiles to new A/B Test variants when they re-enter batch Journeys and refresh treatment cohorts.","siteUrl":"https://docs.treasure.ai","lang":"en-US","jsonLd":{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://www.treasure.ai/","name":"Treasure AI","url":"https://www.treasure.ai/","logo":"https://www.treasure.ai/hubfs/assets/images/logos/primary-logo.svg"},{"@type":"WebSite","@id":"https://docs.treasure.ai/#website","name":"Treasure AI Documentation","url":"https://docs.treasure.ai/","inLanguage":["en","ja"],"publisher":{"@id":"https://www.treasure.ai/"}}]}},"dynamicMarkdocComponents":[],"compilationErrors":[],"ast":{"$$mdtype":"Tag","name":"article","attributes":{},"children":[{"$$mdtype":"Tag","name":"Heading","attributes":{"level":1,"id":"re-randomize-on-re-entry","__idx":0},"children":["Re-randomize on Re-entry"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Treasure Data CDP's ",{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration"},"children":["Journey Orchestration"]}," re-randomization assigns a profile to a new variant when the profile re-enters a batch Journey and reaches a configured A/B Test step. This capability helps recurring Journeys refresh Control and Treatment cohorts instead of keeping a profile in the same variant indefinitely. Re-randomization is configured separately for each A/B Test step, so other A/B Test steps in the Journey can continue to use Sticky assignments."]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"info"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Re-randomization applies only when re-entry is permitted and the profile reaches the configured A/B Test step again. It does not move profiles that are already progressing through the Journey."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"when-to-use-re-randomization","__idx":1},"children":["When to Use Re-randomization"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Re-randomization is best suited for recurring batch Journeys where refreshing cohort composition matters more than keeping individual profiles in the same variant across cycles."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Use re-randomization when you want to:"]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Refresh the composition of Control and Treatment groups in a recurring Journey."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Give profiles another opportunity to receive a Treatment on a later Journey cycle."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Prevent a profile from remaining in the same variant indefinitely."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Reassign profiles across all variants at each eligible re-entry."]}]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Use Sticky assignment instead when profiles must remain in the same variant for the life of the Journey or when you need stable cohorts for winner selection or capped traffic."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"how-it-works","__idx":2},"children":["How It Works"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Treasure Data CDP Journey Orchestration performs a new variant draw only when a profile is eligible to re-enter and reaches the configured A/B Test step again."]},{"$$mdtype":"Tag","name":"ol","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["A profile meets the Journey’s entry criteria."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The profile reaches the A/B Test step and is assigned to a configured variant."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The profile exits or completes the Journey according to the Journey’s configured logic."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The profile becomes eligible to re-enter."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The profile reaches the same A/B Test step again."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Journey Orchestration performs a new assignment across all variants when ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Re-randomize on re-entry"]}," is enabled."]}]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A new assignment is not guaranteed to be different from the previous assignment. For example, a profile assigned to Control in one cycle may receive Treatment in the next cycle, or may receive Control again by chance."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"prerequisites","__idx":3},"children":["Prerequisites"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Before enabling re-randomization, verify the following:"]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The Journey is a ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Batch"]}," Journey."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The Journey’s re-entry setting allows profiles to return for the intended number of cycles."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The Journey has exit, goal, suppression, or completion logic that releases profiles for re-entry as intended."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["A stable and unique profile identifier is available, such as ",{"$$mdtype":"Tag","name":"code","attributes":{},"children":["cdp_customer_id"]},"."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Cooldown, suppression, and frequency rules prevent excessive or conflicting communications."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["The A/B Test step does not use ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Profile Cap"]}," or ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Declare Winner"]},"."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"configure-re-randomization","__idx":4},"children":["Configure Re-randomization"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Use the following steps to configure re-randomization for an A/B Test step in Treasure Data CDP Journey Orchestration."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"open-the-ab-test","__idx":5},"children":["Open the A/B Test"]},{"$$mdtype":"Tag","name":"ol","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Open Treasure Console."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Navigate to ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Audience Studio"]},"."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Select the parent segment and open a batch Journey, or ",{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey"},"children":["create a batch Journey"]},"."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Open the Journey in draft mode."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Select the A/B Test step, or ",{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration/batch/ab-test/creating-an-a-b-test"},"children":["create an A/B Test"]},"."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"set-the-assignment-behavior","__idx":6},"children":["Set the Assignment Behavior"]},{"$$mdtype":"Tag","name":"ol","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Specify a stable ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Unique ID Field"]}," for the assignment, if one is not already configured."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Define the variants and their allocation percentages."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Select ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Re-randomize on re-entry"]}," as the assignment behavior."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Connect each variant to the appropriate downstream action or activation."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Save the A/B Test."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Verify that the selected assignment behavior is displayed."]}]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":[{"$$mdtype":"Tag","name":"img","attributes":{"src":"/assets/re-randomize-on-re-entry-a-b-test-settings.c83557d2cf76d7ef6f1a77edf39ac3701abc93eb9edeb5677a49b17813675540.9e7171ae.webp","alt":"A/B Test configuration showing Re-randomize on re-entry selected, with a 20% / 20% / 60% variant split"},"children":[]}]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Variant percentages define assignment probabilities rather than fixed quotas. For example, a 20% / 20% / 60% split can produce different observed counts in each Journey cycle, especially with a smaller audience."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"assignment-behavior","__idx":7},"children":["Assignment Behavior"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Treasure Data CDP Journey Orchestration supports two assignment behaviors for A/B Test steps: Sticky and Re-randomize on re-entry. Sticky preserves a profile's existing variant, while re-randomization performs a new draw across all configured variants on each eligible re-entry."]},{"$$mdtype":"Tag","name":"div","attributes":{"className":"md-table-wrapper"},"children":[{"$$mdtype":"Tag","name":"table","attributes":{"className":"md"},"children":[{"$$mdtype":"Tag","name":"thead","attributes":{},"children":[{"$$mdtype":"Tag","name":"tr","attributes":{},"children":[{"$$mdtype":"Tag","name":"th","attributes":{"data-label":"Assignment behavior"},"children":["Assignment behavior"]},{"$$mdtype":"Tag","name":"th","attributes":{"data-label":"First entry"},"children":["First entry"]},{"$$mdtype":"Tag","name":"th","attributes":{"data-label":"Later eligible re-entry"},"children":["Later eligible re-entry"]}]}]},{"$$mdtype":"Tag","name":"tbody","attributes":{},"children":[{"$$mdtype":"Tag","name":"tr","attributes":{},"children":[{"$$mdtype":"Tag","name":"td","attributes":{},"children":["Sticky"]},{"$$mdtype":"Tag","name":"td","attributes":{},"children":["Assigns the profile to a variant"]},{"$$mdtype":"Tag","name":"td","attributes":{},"children":["Keeps the profile in the previously assigned variant"]}]},{"$$mdtype":"Tag","name":"tr","attributes":{},"children":[{"$$mdtype":"Tag","name":"td","attributes":{},"children":["Re-randomize on re-entry"]},{"$$mdtype":"Tag","name":"td","attributes":{},"children":["Assigns the profile to a variant"]},{"$$mdtype":"Tag","name":"td","attributes":{},"children":["Performs a new draw across all configured variants"]}]}]}]}]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Re-randomization is full re-randomization. Control participates in the new draw; the capability is not limited to refreshing the Control group."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"limitations","__idx":8},"children":["Limitations"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Treasure Data CDP Journey Orchestration supports re-randomization only for batch Journeys. Profiles already progressing through a Journey are not reassigned mid-Journey."]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Profile Cap is not supported on a re-randomized A/B Test step."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Declare Winner is not supported on a re-randomized A/B Test step."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Re-randomization does not provide a calendar-based reset policy; use the Journey’s re-entry cadence or a separate scheduling design when calendar boundaries are required."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Existing Sticky A/B Test steps remain Sticky unless they are configured separately."]}]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"warning"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A profile can receive a different Treatment or offer on a later cycle. Add appropriate suppression, cooldown, and frequency controls before using re-randomization with customer-facing activations."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"validate-before-launch","__idx":9},"children":["Validate Before Launch"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Validate re-randomization with a non-customer-facing observation activation before enabling customer-facing activations."]},{"$$mdtype":"Tag","name":"ol","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Test with a non-customer-facing observation activation."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Run at least two eligible Journey cycles."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Confirm that the profile reaches the A/B Test step again after re-entry."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Compare assignments using the stable profile identifier."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Confirm that profiles already in the Journey are not moved mid-Journey."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Review variant counts by cycle; do not expect exact percentages in every cycle."]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Confirm suppression and cooldown behavior before enabling customer-facing activations."]}]},{"$$mdtype":"Tag","name":"Admonition","attributes":{"type":"info"},"children":[{"$$mdtype":"Tag","name":"p","attributes":{},"children":["If ",{"$$mdtype":"Tag","name":"strong","attributes":{},"children":["Re-randomize on re-entry"]}," is not available in the A/B Test configuration, contact Treasure AI to request enablement for the relevant account and environment."]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"related-pages","__idx":10},"children":["Related Pages"]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration/batch/ab-test/about-a-b-testing"},"children":["About A/B Testing"]}]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration/batch/ab-test/creating-an-a-b-test"},"children":["Creating an A/B Test"]}]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration/batch/defining-profile-re-entry-criteria"},"children":["Defining Profile Re-entry Criteria"]}]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey"},"children":["Creating a Batch Journey"]}]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":[{"$$mdtype":"Tag","name":"MarkdownLink","attributes":{"href":"/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey-activation"},"children":["Creating a Batch Journey Activation"]}]}]}]},"headings":[{"value":"Re-randomize on Re-entry","id":"re-randomize-on-re-entry","depth":1},{"value":"When to Use Re-randomization","id":"when-to-use-re-randomization","depth":2},{"value":"How It Works","id":"how-it-works","depth":2},{"value":"Prerequisites","id":"prerequisites","depth":2},{"value":"Configure Re-randomization","id":"configure-re-randomization","depth":2},{"value":"Open the A/B Test","id":"open-the-ab-test","depth":3},{"value":"Set the Assignment Behavior","id":"set-the-assignment-behavior","depth":3},{"value":"Assignment Behavior","id":"assignment-behavior","depth":2},{"value":"Limitations","id":"limitations","depth":2},{"value":"Validate Before Launch","id":"validate-before-launch","depth":2},{"value":"Related Pages","id":"related-pages","depth":2}],"frontmatter":{"seo":{"title":"Re-randomize on Re-entry in Journey Orchestration","description":"Configure Treasure Data CDP Journey Orchestration to assign profiles to new A/B Test variants when they re-enter batch Journeys and refresh treatment cohorts."}},"lastModified":"2026-08-27T08:16:22.000Z","pagePropGetterError":{"message":"","name":""}},"slug":"/products/customer-data-platform/journey-orchestration/batch/ab-test/re-randomize-on-re-entry","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}