Group assignment

Overview

This guide explains how to configure experiment groups for AI Decisioning (AID).

Experiment group assignment determines whether a user receives:

• treatment — AI-optimized messaging
• holdout — No campaign messaging for this use case
• customer_managed — Your existing business-as-usual messaging

To measure incremental lift accurately, every eligible user must be consistently assigned to one of these groups.

In most cases, Hightouch recommends using built-in group assignment within AI Decisioning. However, you can also assign groups in your warehouse or another testing platform if needed.

Choose the approach that best fits your implementation:

• Hightouch-assigned groups
• Externally-assigned groups

Why experiment group assignment is required

AI Decisioning uses incrementality-based measurement to determine whether personalized messaging drives additional conversions beyond what would have happened otherwise.

To measure lift accurately, users must be consistently assigned to:

• treatment
• holdout
• customer_managed

Stable and unbiased assignment ensures:

• Valid experiment reporting
• Accurate performance comparisons
• No contamination between messaging strategies

Hightouch-assigned groups

In most cases, Hightouch recommends using native AI Decisioning functionality to assign experiment groups. This is configured directly in the Hightouch UI when you set up an agent →.

When users qualify for an agent’s audience, Hightouch assigns each user to a group by:

• Computing a deterministic, uniform hash of a stable user identifier plus a static experiment key ("salt")
• Taking the result modulo 100
• Mapping contiguous bucket ranges to configured percentages
  (for example, 0–9 = 10% holdout, 10–29 = 20% customer_managed, 30–99 = 70% treatment)

Although group assignment is evaluated daily when the AID job runs, deterministic hashing ensures users retain the same group once assigned.

This approach is randomized and independent of demographic or attribute bias. Assignments depend only on (user_id, salt) and do not rebalance over time. If percentage allocations change later, existing assignments remain stable and only marginal bucket ranges expand or contract.

Advantages

• Guaranteed group stability using proven randomization logic
• Simplified configuration for most implementations

Considerations

• Group assignments are evaluated daily when the AID job runs. If many new users enter the audience each day, users may briefly be eligible for customer-managed campaigns before suppression occurs.
• Group assignments must be synced to downstream tools. Suppression must be configured to ensure holdout and treatment users do not receive customer-managed campaigns.

Hightouch-assigned groups setup steps

Prerequisites

• Initial schema configuration
  Learn more about defining your schema →
  • Parent model with a unique primary key
  • Related models configured
• Audience defined in Hightouch
  Learn more about building audiences →
• Destinations configured for syncing group assignments to your ESP
  See setup instructions for Braze →, Iterable →, or SFMC →

1. Set the holdout percentage

When you create a new agent, you set a holdout percentage. The standard holdout is 10%.

For live agents, you can view or modify the holdout percentage in the agent’s Configuration tab.

If you chose to manage group assignment yourself in the data warehouse or via another tool, the source field can be referenced here instead of a raw percentage assignment.

2. Define the customer_managed percentage

During onboarding, you will work with your Hightouch account team to determine what percentage of users remain in your existing business-as-usual messaging strategy (customer_managed).

Your account team configures this in the agent.

3. Generate experiment groups and sync downstream

Prior to launch, your Hightouch account team will:

1. Generate initial group assignments
2. Join assignments back to your schema
3. Sync groups to your ESP as Cohorts, Segments, or Lists (terminology varies)

4. Configure suppression

Suppress the holdout group and Hightouch treatment group from your existing sends to ensure a valid experiment.

For example:

• Sync holdout and treatment users to a Braze cohort
• Use that cohort as suppression for all customer_managed campaigns

Where to access group assignments

Group assignments are stored in a table in your data warehouse and are:

• Used by the Hightouch UI to populate reporting
• Available as list memberships or user attributes in your ESP

Performance overview reporting supports breakdowns for:

• treatment
• customer_managed
• holdout

Experiment groups table in the warehouse

This table tracks which experiment bucket each user belongs to over time for a given agent (e.g., AID treatment vs customer_managed vs holdout).

Example table name
hightouch_planner.de_user_experiment_groups_<agent_id>

Key columns

This table is typically used to:

• Build customer_managed and holdout audiences
• Slice reporting by experiment group membership over time

The group assignment table is pulled into the Schema:

Externally-assigned groups

The following setup applies only if you manage group assignment outside of Hightouch.

SQL-based group assignment

You create a column in your parent model using SQL to denote split group assignments.

Advantages:

• Enables you to use your existing experiment assignment infrastructure
• Allows for more frequent experiment group updates if your users enter your parent model at high frequency and customer_managed suppression groups need to be updated more frequently than AID run frequency

Considerations:

• Requires careful SQL logic to ensure proper randomization and group stability
• Must preserve assignment stability when users re-enter audiences

Other tool-managed assignment

If you have a dedicated testing platform or leverage split capabilities within another tool, we can use the split assignments as long as they are populated into the data warehouse. Timing considerations must be taken into account here to ensure users are not eligible for an audience without having a split assignment.

Externally-assigned groups setup steps

Prerequisites

Before configuring group assignment, ensure the following are in place:

• Initial schema configuration
  See Define data schema →
• A parent model with a unique primary key
• Related models configured
• An audience defined in Hightouch
  See Audiences →
• Destinations configured for syncing group assignments to your ESP
  See destination setup docs →
• Confirmation of your split group assignment, typically one of the following:
  • 2-way split: 90% Hightouch AID treatment, 10% holdout
  • 3-way split: 45% Hightouch AID treatment, 45% customer_managed, 10% holdout

1. Create a related model for group assignment

Create a dedicated related model in your schema that deterministically assigns each user to a group.

The following example shows a Snowflake SQL query that can be used directly in a related model to assign a 45 / 45 / 10 split.

-- Snowflake example
WITH bucketed_users AS (
    SELECT
        user_id,
        -- Modulo 100 converts the hash into a uniform integer bucket from 0–99
        -- Rotate the salt '1' to redistribute users in future experiments
        ABS(HASH(CONCAT(user_id, '1'))) % 100 AS bucket
    FROM parent_model_table
)

SELECT
    user_id,
    CASE
        WHEN bucket < 45 THEN 'treatment'
        WHEN bucket < 90 THEN 'customer_managed'
        ELSE 'holdout'
    END AS aid_agent1_assignment
FROM bucketed_users;

In your related model setup:

• Use user_id as the join key
• Set the relationship to 1:1
• Merge fields from the related model onto the parent model

This makes the group assignment available as a user-level attribute throughout Hightouch.

Example related model configuration

2. Create a Hightouch sync for the customer_managed audience

Create an audience that includes all users where aid_agent1_assignment = customer_managed (using the field name defined in the group assignment SQL).

Set up a recurring sync to your ESP to populate an audience that will be used as a filter for customer_managed campaigns.

• Choose a sync frequency that fits your send schedule (for example, hourly)
• Ensure the audience stays up to date as users enter and exit eligibility

Where are group assignments used in AID?

Your Hightouch account team will add the group assignment variant into your agent configuration.

Group assignments are used in the Hightouch UI to automatically populate reporting.

Performance overview reporting supports breakdowns for:

• treatment
• customer_managed
• holdout

Frequently asked questions

Will Hightouch reporting match my other attribution?

While raw event counts will match when using the same source data, Hightouch reporting is incrementality-based and will not always align with attribution-based reporting in your ESP or other tools.

When you look at Hightouch incrementality reporting, we are not claiming full responsibility for every conversion. We are simply reporting the conversion rate for the group of users who received any treatment versus the conversion for users who did not. The result is a clear overview of whether the marketing efforts are effective and how much lift they drive.

What do treatment and holdout users actually receive?

• treatment
  AI-optimized messages (content and timing) from the agent.

• holdout
  No campaign messaging for that use case, but users are still tracked to observe organic behavior.

• customer_managed
  Users in this group continue to receive your existing marketing messaging.

How does Hightouch assign users to treatment, holdout, and customer_managed?

When a user qualifies for an audience, Hightouch:

1. Computes a deterministic hash of the user’s stable ID and an experiment key
2. Applies modulo 100 to create a bucket from 0–99
3. Maps bucket ranges to groups (for example, 0–9 = holdout, 10–29 = customer_managed, 30–99 = treatment)

This produces random, unbiased, and stable group assignments that never change for a given agent.

What happens if we change percentages later?

Changing split assignments only affects new users entering the audiences. Existing users remain in their original group. There is no re-randomization of users once a group is assigned.

What if users fall out of the audience and later re-enter?

Group assignment is deterministic. Users re-enter the same group they were originally assigned to.

What happens if I want to put all users in my treatment group?

Once you have established a high-performing agent, you can merge customer_managed users into the Hightouch treatment audience.

Contact your Hightouch account team to request this change. We do not recommend merging the holdout group and suggest maintaining at least a small holdout for ongoing measurement.