Blog

Who sees a Shopify rollout discount? Visitors, markets, ads

By Beacon Wave Studio · October 5, 2026 · 8 min read

In October 2026 Shopify added discounts to Rollouts. A rollout, the scheduling tool under Markets > Rollouts, could already switch a theme, a catalog or a checkout configuration on at a set time; now it can activate or deactivate a discount with them, for the whole store or for a share of visitors. The feature is genuinely useful. It also produces the most confusing support ticket a store can get: “my friend got 15% off and I did not”.

This post is about the audience side of that. Not how to build a rollout, which Shopify’s guide to creating a rollout covers, but who actually ends up seeing the discount once it runs: which visitors, in which markets, arriving from where. If you use GeoBeacon to send shoppers to the right market, the second half explains how the two fit together and why nothing in GeoBeacon changed with this release.

Three things decide who is in a rollout

Shopify’s page on rollout types defines eligible visitors as the ones covered by the rollout’s traffic allocation and by the markets its changes apply to. Add the channel the visitor is on and you have the three filters.

Traffic allocation. A Launch at 100% reaches every eligible visitor. A Launch or Event at a lower percentage reaches that share and leaves the rest on the current store. An Experiment, available on the Grow plan and above, splits its audience further into a control, which sees the store as it is, and a treatment, which sees the changes. For a discount change the control keeps the discount in whatever state its own dates put it, and the treatment sees it activated or deactivated by the rollout.

Markets. A rollout’s changes apply to the markets you select. A visitor browsing a market outside that list is not in the rollout at all, however much traffic you allocated. This is the filter most stores forget, because it is not a property of the visitor. It is a property of the storefront the visitor happens to be standing in.

Channel. According to Shopify’s requirements and considerations, Experiments and any rollout below 100% apply only to the online store. Point of sale, headless storefronts and other channels are outside them. Only a rollout that publishes to 100% of visitors reaches the other places a change would normally propagate to.

The discount’s own dates stop being the whole truth

A discount in a rollout keeps its own start and end dates, and Shopify applies both rules at once. The discount is active for a visitor when its own dates say so, or when an active rollout that activates it covers that visitor. A rollout that deactivates the discount wins for its audience even inside the discount’s own dates. So the row on the Discounts page can read Scheduled while thousands of visitors are checking out with the discount applied, and it can read Active while the treatment group pays full price. Whoever answers support messages needs to know that the Discounts page is now the second place to look, and Markets > Rollouts is the first.

Shopify also told app developers about this in October 2026. Apps that read discount data were asked to request a new read_rollouts permission and read the rollouts attached to each discount, because the discount’s status alone can now be misleading. That request is aimed at discount and sale apps. Apps that do not read discounts, GeoBeacon among them, have nothing to update.

Markets: the filter geolocation actually touches

Here is the case that catches international stores. You create a rollout that activates a 15% discount for the German market during a local holiday. A shopper in Munich searches for your brand, clicks the first result, and lands on your primary domain. Shopify resolves the market from the URL, so that shopper is in your primary market. The rollout does not apply to them. They see full prices, and if a colleague who bookmarked the German storefront sees the discount, you have your support ticket.

This is the same problem we described for market-specific promotions before discounts joined rollouts, and the answer has not changed. Something has to move the shopper into the market where you configured the promotion. GeoBeacon does that: a rule maps the shopper’s country to a Shopify market or an external store, and either offers a popup or redirects. It decides in the browser after the page has loaded, skips known crawlers so search engines keep indexing every market URL, and remembers a shopper’s choice so they are not asked twice. Once the shopper is on the German storefront, Shopify’s own rules decide whether the rollout includes them.

Two things follow from that. First, GeoBeacon does not make a rollout reach more people. A rollout at 50% traffic still reaches half the German storefront’s visitors; routing shoppers there only makes sure the right half is drawn from the right people. Second, GeoBeacon does not need to know that a rollout exists. It reads the store’s markets to help you generate rules and nothing else, which is why its only permission is reading markets.

Ads, feeds and the offer that does not match

Shopify’s page on audience reach and external channels is blunt about this: external channels do not receive rollout information. Google Shopping, Meta catalogs, product feeds, affiliate links and third-party apps all see your store as it is without the rollout. If a rollout gives 15% off to half your visitors, half the people clicking an ad that says 15% off will not get it. Shopify lists “a different discount” among the mismatches, and notes that channels that review landing pages can delist products or suspend accounts when the offer on the page does not match the listing.

The fixes Shopify suggests are the obvious ones. Run the rollout at 100% for anything that appears in ads or feeds, so every visitor gets the same offer. Or pause the ads for the affected products while the rollout runs. Or keep the rollout’s products out of the feed for its duration. Organic search is less sensitive, since there is no feed review, but the same visitor confusion applies to anyone arriving from a search result.

Geolocation adds one wrinkle. A redirect from your primary domain to a market subfolder is a URL change, and a feed that lists the primary URL will send shoppers through that redirect. GeoBeacon handles the redirect with the shopper’s country, not the campaign, so an ad for the German promotion will land a German shopper on the German storefront as intended. It will not stop a shopper from landing in the control group once they are there. Only the traffic allocation does that.

Before the rollout starts

A short list, in the order we would check it.

Markets. Open the rollout and confirm the markets its changes apply to are the ones you meant. Then confirm that shoppers from those countries actually land in those markets. If your analytics show German visitors mostly on the primary domain, a market-specific rollout will miss most of them until a geolocation rule or a very visible country selector moves them.

Allocation. If the discount is also in ads, feeds or an email you are sending to everyone, set the rollout to 100% or choose an Event instead of an Experiment. Save experiments for discounts you are not advertising externally.

Support. Write down for your team that discounts can be live from a rollout while the Discounts page says Scheduled, and that in an Experiment two shoppers can legitimately see different offers. A one-line note saves an afternoon.

Check it yourself. After the rollout starts, open the target market’s storefront in a few private browser windows. For an Experiment, reload until you have seen both the control and the treatment, and make sure each one is a store you would be happy for a customer to land on.

Rollouts gives merchants a scheduling and testing tool that used to need an app, and discounts were the obvious next thing to put in it. Reaching the right visitors, though, still starts with having them in the right market. That part is what GeoBeacon is for, and it keeps doing it the same way whether a rollout is running or not.