Google Play Merchandising and Optimization Page: What Changes and What to Do First
Google Play does not only sell inside your app. It also surfaces your products on store pages, in notifications, and in browsing flows that many teams never actively manage. Google is now replacing three separate Console tools for that work with one machine-learning-driven Merchandising and optimization page, and existing configurations freeze on March 16. This guide explains what each legacy tool did, what survives the migration, and which Console actions must happen before the cutoff.
The three tools being replaced
Out-of-app promotion currently lives in three Console areas, and each one asks you for a different kind of decision. The useful way to read them is by how much control you hand over versus how much you keep.
- Purchase flow recommendations is the hands-off option. You nominate SKUs and can narrow them by country; after that, Google's signals about a shopper's history and browsing context decide the placement. Think of it as a supply list, not a campaign.
- Featured products is the hands-on option. You name the products, give them a window with start and end dates, attach offers or events, aim at audiences and countries, and can keep everything to licensed testers while you build. It behaves like a scheduled promotion.
- Cart abandonment reminders is not product-level at all. Google notices a checkout that stalled and nudges the shopper to return. Your only lever is the Console opt-out form, and today that form is split between one-time products and subscriptions.
All three reach people who have not opened your app, which is why they behave as a second acquisition channel rather than an extension of your paywall.
What the unified page changes
The new page inverts the workflow. Instead of describing a campaign, you describe a catalog: mark the SKUs that may be promoted, and Google Play's models choose the surfaces, the moment, and the audience. Because the system can use every out-of-app purchase flow Google Play supports, the ceiling on reach is higher than a hand-built promotion could realistically hit.
What you give up is the levers that lived at the merchandising layer. Audience targeting, country targeting, and offer or event associations no longer exist there. Geography becomes a SKU-level concern, so any regional strategy has to be expressed in the product catalog itself rather than in a promotion.
A practical way to judge the trade: if your out-of-app strategy was mostly "promote these good products broadly," the new page is a net gain. If it depended on showing different products to different regions or tying promotions to specific events, that logic needs a new home before the cutoff. Teams that skipped these tools entirely because three separate surfaces felt like overhead now have a single, lower-friction place to opt in.
Timeline and cutoff
The migration runs in phases around one hard date. The schedule below reproduces the published timeline exactly; treat it as a dated reference and confirm current Console behavior before you act on it.
Featured products: what happens to each configuration
Featured products carry the most settings, so they also carry the most migration rules. The table below reproduces each per-aspect outcome exactly. Work through it product by product: for every active featured product, find its row and decide whether the post-cutoff behavior is acceptable or needs a change before the freeze.
Purchase recommendations: simpler path
Recommendations need less attention because there is less to lose. SKUs you already nominated stay eligible after March 16, so the products keep being suggested. The country filter attached to recommendations goes away, and if geography still matters it has to be expressed at the SKU level. Products reserved for licensed testers drop out of merchandising. Reporting stays on the old page until that page is retired with the new launch. In practice, the only capability most teams lose is choosing which countries see a recommendation.
Cart abandonment reminders: one detail that matters
This is the lightest migration, but one scope detail is easy to miss: the new page starts with one-time products only. Subscriptions sit outside the initial launch scope. A subscription blocklist you already have stays in force and is untouched by the move.
On opt-out timing, the sequence matters. The existing form for one-time products works until March 16; after that, opting out means waiting for the new page. Opt-outs already on file continue to apply, and if you are content to stay opted in, there is nothing to do.
Pre-cutoff checklist
Sequence the work by what becomes impossible after the freeze. Anything that can only happen before March 16 goes first.
- File any one-time-product cart abandonment opt-out using the existing form. This is the only window; afterwards you wait for the new page.
- Audit featured products with end dates after March 16. For each one, either drop the end date so it keeps running indefinitely, or delete it if you do not want it promoted past the cutoff.
- Move country restrictions to the SKU level wherever country targeting is currently set on featured products or purchase recommendations.
- Revisit licensed-tester-only products. They will be excluded from merchandising; retarget them before the cutoff if real users should see them.
- Plan replacements for offer and event associations on featured products, since those links stop being supported.
- Export performance data from the featured products and purchase recommendations pages while the metrics are still visible.
- Brief anyone on your team who touches Play Console about the deadline and the changes.
Why your billing code does not change
A common worry is whether purchases that begin on a Play Store surface need new billing plumbing. They do not. A purchase started from a Play Store surface arrives through the same Play Billing Library path as an in-app purchase: your app receives it through the same PurchasesUpdatedListener or queryPurchasesAsync calls, with the same purchase token, product ID, and acknowledgment requirements. If your backend consumes Real Time Developer Notifications (RTDN), the notification types match those for in-app purchases. In short, the store surface changes where the shopper starts, not what your integration receives afterward, so existing verification and fulfillment logic should apply without modification. If you are evaluating a billing vendor, ask specifically whether store-originated Play transactions are handled as ordinary Play purchases, including verification, entitlement granting, and acknowledgment, and confirm the answer against that vendor's current documentation before relying on it. The distinction to keep clear: the Merchandising and optimization page changes how Google Play promotes products, not how purchases are processed once they happen. Console configuration is the work item; billing code and entitlement logic stay as they are.
| Date | What happens |
|---|---|
| Before March 16 | Last chance to modify existing purchase flow recommendations and featured products configurations. Last chance to use the cart abandonment reminder opt out form for one time products. |
| March 16 | Existing purchase flow recommendations and featured products pages become frozen. The cart abandonment reminder opt out form is disabled for one time products. No further changes can be made on these pages. |
| After March 16 | Existing selections remain active according to the migration rules described below. Your configurations continue to function but cannot be modified. |
| New page launches | Google Play automatically migrates your existing selections to the new Merchandizing and optimization page. You can then modify your selections on the new page. The old pages for purchase flow recommendations and featured products are deprecated. The cart abandonment reminders opt out form for one time products is also deprecated. |
Dated reference as published; confirm current Console behavior before acting.
| Configuration aspect | What happens after March 16 |
|---|---|
| No end date set | The featured product remains in place and continues to be merchandized. No action needed. |
| End date after March 16 | You have two options before March 16: make the product available indefinitely by removing the end date, or delete it if you do not want it merchandized past March 16. |
| Offers and events | Offers and events associated with featured products will no longer be supported. If you rely on these associations, plan accordingly before the cutoff. |
| Audience and country targeting | Audience and country targeting associated with existing featured products will not be supported. If you need to restrict country selection, you must configure that at the SKU level. |
| Licensed testers | Products that only target licensed testers will no longer be available for merchandizing. If you have products in a testing only configuration, they will be excluded from out of app promotion. |
| Performance reporting | Performance reporting and associated metrics remain visible on the featured products page until it is deprecated when the new Merchandizing and optimization page launches. |
Dated reference as published; confirm current Console behavior before acting.
Frequently asked questions
Do out-of-app purchases need a different billing integration?
No. Purchases started from Google Play surfaces go through the same Play Billing Library flow as in-app purchases. Your app receives them through the same PurchasesUpdatedListener or queryPurchasesAsync calls, with the same purchase token, product ID, and acknowledgment requirements. RTDN notification types are also the same. If you use a billing vendor, check that vendor's current documentation for how it handles store-originated purchases, and confirm that verification, entitlement granting, and acknowledgment follow the same path as in-app transactions.
Will my existing featured products keep running after the cutoff?
It depends on the configuration. Featured products with no end date keep being merchandised. Those with an end date after March 16 must either have the end date removed (to run indefinitely) or be deleted before the cutoff. Offer/event associations, audience targeting, and country targeting are dropped; country restrictions must move to the SKU level. Licensed-tester-only products are excluded from merchandising.
What happens to my cart abandonment reminder opt-out?
If you already opted out, the opt-out stays in effect. If you want to opt out of one-time-product reminders, submit the existing form before March 16; after that you must wait for the new page to launch. Subscription blocklists are unchanged. The new page initially covers one-time products only, not subscriptions.
Can I still target specific countries after the migration?
Not at the merchandising level. Audience and country targeting on featured products and country targeting on purchase recommendations are dropped. If you need geographic restrictions, configure them at the SKU level.