Skip to main content
query

A rollout on a shop.

•ID!
required

The ID of the rollout.


Was this section helpful?

•Rollout

A rollout on a shop. Merchants use rollouts to run sales events, permanent launches, and A/B tests by serving treatments to a configured share of buyers.

Show fields
•DateTime

The date and time at which the rollout was archived.

•DateTime

The actual conclusion date and time of the rollout for public API requests. Use schedule.concludeAt for the planned conclusion date.

•DateTime!
non-null

The date and time at which the rollout was created.

Anchor to effectiveTrafficAllocationeffectiveTrafficAllocation
•Float!
non-null

The effective percentage of total traffic this rollout receives for new buyer assignments, accounting for mutex group constraints with other active rollouts.

•ID!
non-null

The ID of the rollout.

•String!
non-null

The name of the rollout.

•RolloutSchedule

The rollout's planned activation and conclusion dates. Returns null when neither date is set.

Show fields
•DateTime

The actual start date and time of the rollout for public API requests. Use schedule.activateAt for the planned activation date.

•RolloutStatus!
non-null

The status of the rollout.

Show enum values
•Int!
non-null

The percentage of buyer traffic that the rollout is configured to receive, as an integer from 0 to 100. This is the configured allocation before other active rollouts on the same resources are taken into account, so it isn't the share of buyers that a treatment reaches.

•[RolloutTreatment!]!
non-null

The treatments of the rollout. Control treatments are included even when they have no changes.

Show fields
•DateTime!
non-null

The date and time at which the rollout was last edited. This timestamp doesn't necessarily change when another rollout changes this rollout's effective traffic allocation.


Was this section helpful?