Product segments that update themselves: best sellers, zombies and price drops

Every shopping account eventually wants the same thing: spend more on the products that sell, less on the ones that don't, and react when something changes — a price drop, a restock, the last few units. All of that starts with knowing which products are which. That is segmentation, and the hard part is not defining the segments. It is keeping them true.

A list of "best sellers" someone exported in March is wrong by May. A segment that updates itself is a different kind of tool: it becomes part of the feed, and the campaigns built on it stay right without anyone touching them.

Static and rule-based segments

There are two kinds, and you need both.

Static segments hold decisions only people make: the products in a Black Friday campaign, homepage picks, a new collection the buyer is proud of. Nothing in the data says which products those are, so someone chooses them — one by one, or in bulk from a filtered list — and they stay put until someone changes them.

Rule-based (dynamic) segments hold facts: what sells, what is running out, what just got cheaper. A rule describes the segment, and products enter and leave it as the data changes. Nobody maintains the list; the rule does.

The mistake is to maintain facts by hand. It works for a week.

Seven segments that pay off

These are the segments that most often change what you do in an ad account. The thresholds are good defaults — adjust them to your catalog, but keep a minimum in every rule.

Best sellers

The top 10% of products by purchases over the last 30 days, with at least one purchase. A percentage adapts as the catalog grows; a fixed "20 sales" does not. Keep ties: if the cut falls between products with the same number of purchases, include all of them, or the segment changes for no reason.

Use: a higher target or bid, their own campaign, the first products in a catalog ad.

Zombie products

In stock for more than 30 days, at most 5 views and no purchases. The "30 days" matters: without it, every new product looks like a zombie in its first week.

Use: a low-bid campaign, or leave them out of paid feeds entirely and look at the listings — the title, images or price is usually the problem.

Viewed, not selling

Products with as many views as your busiest quarter of products — and at least 20 — but no purchases. People find them and decide not to buy. This segment is rarely an ads problem and often a price or product-page problem, which is exactly why it is worth seeing.

Use: a review list for the merchandising team; lower bids until something changes.

Price drop

In stock, and the price shoppers pay fell by 5% or more in the last 7 days. "The price shoppers pay" means the sale price when there is one — a sale that starts is a price drop.

Use: a retargeting product set for people who viewed the product before, or a promotion label.

Back in stock

Out of stock before, in stock again in the last 7 days. The people who wanted it the first time are the best audience you have.

Use: retargeting, and a nudge to lift bids that were cut while the product was unavailable.

Low stock

In stock with 1 to 5 units left. There is little point in paying for clicks on the last unit.

Use: lower bids, or leave the products out of price comparison sites until they are restocked. The mirror segment, restocked — stock up by at least 5 units and 25% in the last 7 days — tells you when to bring them back.

New arrivals

First seen in the last 30 days and in stock — but not the products that came with your very first import, or the whole catalog counts as "new" for a month.

Use: a separate campaign with its own budget, since new products have no history for smart bidding to learn from.

Getting segments into the channels

Channels don't know your segments; they know your feed. Two mechanisms carry segments into it.

Custom labels. Google Shopping and Performance Max campaigns can split listing groups by custom_label_0 to custom_label_4. Write a segment into a label — custom_label_0 = best_seller — and the campaign can bid on it. Meta's product sets can filter on custom labels too, so the same label becomes a product set for a catalog ad; other catalog channels offer similar filters, so check which fields yours accepts. Our guide to custom labels covers label schemes in detail.

Feed filters. Some segments shouldn't be advertised at all. Rather than excluding them in every campaign, leave them out of the feed: "not in Zombie products", "not in Low stock" for a price comparison feed. A product that leaves the segment comes back with the next build.

Pitfalls

• Too little data. Three views and no purchase isn't a zombie; it's a product nobody has seen yet. Give every performance rule a minimum number of views or purchases.
• Segments that flap. A product that enters and leaves "best sellers" every other day unsettles bidding. Recalculate daily rather than hourly, use a 30-day window, and keep ties.
• A label that changes meaning. Members of a segment should change; what the label means should not. If custom_label_0 meant margin last month and best sellers this month, every campaign built on it is now wrong.
• Analytics that don't match the feed. Performance segments only work if the item ids in Google Analytics match your products — by id, SKU, item group or GTIN. Check the match rate before trusting a zombie list.
• No history, no change. "Price drop" needs the price before. A tool can only see changes from the moment it starts comparing; it can't know what happened earlier.

How FeedManager does it

FeedManager calls segments product tags. A static tag is set on a product page, in bulk on selected products or on every product matching the list's filters, through the Product API, or copied once from your Shopify or WooCommerce tags. A dynamic tag has a rule — the same conditions as feed filters, plus an optional ranking such as "top 10% by purchases", with ties kept — and runs every hour, six hours, day or week, and optionally two minutes after a sync. It never runs more often than your plan syncs its sources. A live preview shows what the rule would tag before you save it.

Twenty-five suggested tags — the seven above and eighteen more, such as top revenue, trending up, high stock, big discounts, top rated, low margin, below market price and search winners — are offered on the Tags page when your data supports them, each with how many products it would tag now. Nothing is created until you add it, and every rule can be edited afterwards. The performance ones need Google Analytics numbers (best sellers and top revenue also work with Shopify Analytics sales), the market-price ones Google Merchant Center and the search ones Google Search Console, which come with Pro and above; the rest work on every plan.

For price, stock and availability changes, each sync records the last change it saw on each product. That starts with your first syncs — there is no history from before — and the time of a change is as precise as your sync interval.

In feeds, "has the tag" and "doesn't have the tag" work in filters and in rule conditions, so a rule can set custom_label_0 to best_seller for every product tagged Best sellers, and {tags} writes a product's tag names into a field. Feeds that use tags and rebuild after syncs are rebuilt two minutes after tags change. How many tags each plan includes is on the pricing page.

Segments are the cheapest structure you can add to a catalog: no new creative, no new budget. The work is in keeping them true — and that is work a rule does better than a spreadsheet.

Frequently asked questions