Retarget your store visitors: Meta catalog and Google Merchant Center feeds for a small store.

Why retargeting is the cheapest ad rupee

A cold ad — shown to someone who has never heard of you — has to do three jobs at once: get attention, explain what you sell, and earn enough trust for a click. A retargeting ad has one job: remind. The person already did the hard part by visiting. That is why, on the same product with the same creative, retargeting audiences convert at several times the rate of cold ones, and why the cost of an order from a returning visitor is usually a fraction of a cold order's.

There is a second reason it suits a small store. Cold campaigns need volume to learn — Meta wants dozens of conversions a week before it optimises well, and a store doing ten orders a day cannot feed it. Retargeting audiences are small and specific, so a small budget covers them fully. You are not competing on scale; you are just showing up again.

The three audiences (and the one exclusion)

You do not need twelve audiences. Three, built from your Pixel events, cover a small store, and they are layered by intent — the deeper the visitor went, the shorter the window and the harder the ad can push.

Windows are a judgement, not a rule. A ₹400 phone cover is decided in a day; a ₹6,000 saree might be thought about for two weeks. Start with the numbers above and shorten them if you see the same people being hit too often (Meta reports frequency — above 3–4 a week on a small audience means shrink the window or the budget).

What a product feed is, and why catalog ads and Shopping need one

A product feed is a plain file — one row per product — that lists what you sell in a format an ad platform can read: an ID, a title, a description, a price, whether it is in stock, a link to the product page and a link to its image. Meta reads it into a Catalog; Google reads it into Merchant Center. Once they have your catalogue, they can build ads out of it without you designing anything.

That is the whole point of retargeting with a feed. When someone views the *Blue Jaipur Kurta* on your store, the Pixel tells Meta the product ID. Meta looks that ID up in your catalog and shows that visitor an ad with *that* kurta, its price and its photo — not a generic banner. This is what Advantage+ catalog ads (Meta's name for dynamic product ads) do, and it is the format that does the heavy lifting for every serious Instagram seller. Google's side is the same idea: Shopping results with your product photo and price, both the free listings and paid Shopping ads, are built from your Merchant Center feed.

Without a feed, you can still retarget — but only with a static image you made, shown to everyone in the audience regardless of what they looked at. With a feed, the ad is personal and the platform keeps it current: sold out drops out, a price change shows the new price.

How SitesPlaced generates your feeds

On the SitesPlaced AI Co-founder plan every published store serves two feeds, built from the live catalogue and refreshed on their own. You do not export anything or maintain a spreadsheet.

• Meta Catalog (CSV): yourstore/feed.csv — for example https://meeraweaves.sitesplaced.site/feed.csv, or the same path on your custom domain.
• Google Merchant Center (XML): yourstore/feed.xml — an RSS 2.0 feed with Google's g: fields, the format Merchant Center reads directly.

Both feeds carry the same columns, which are the ones Meta lists as required or recommended for a catalog and which Merchant Center accepts as-is:

A few rules baked into the feed so the catalog stays clean: archived products are excluded, products with no image or no name are skipped (both platforms reject them anyway), and the feed refreshes about every 15 minutes, so a price change or a sold-out product reaches the platforms on their next scheduled fetch. You will find both URLs, with a copy button, under AI Co-founder → Retargeting kit in your store dashboard.

Adding the feed to Meta Commerce Manager

Meta's screens move around, so these are the steps by name rather than by screenshot. You need a Facebook Business account and the Pixel already connected (below).

1. Open Commerce Manager and create a catalog. Choose the E-commerce catalog type. Give it your store's name.
2. Add items with a scheduled feed. Under Catalog → Data sources, choose Add items → Data feed → Scheduled feed. Paste your feed.csv URL. No login or password is needed; the feed is public.
3. Set the schedule. Hourly is ideal; daily is fine for a small store. Meta will fetch the file on that schedule and update prices and stock.
4. Check the first upload. Commerce Manager reports how many items it read and flags any it rejected. The common rejections are a missing image and a description that is too short — fix them on the product and they clear on the next fetch.
5. Connect the Pixel to the catalog. Under Catalog → Events, connect the Pixel from your store. Meta then matches the id in the feed to the product IDs your Pixel sends on ViewContent and AddToCart, and the Viewed a product and Added to cart audiences light up.

Adding the feed to Google Merchant Center

1. Create a Merchant Center account and claim your website. Use the store's live URL — your custom domain if you have one. Verification is by a small HTML tag or through Search Console if the domain is already verified there.
2. Add a product source. Under Products → Add products, choose Add products from a file and then the option to fetch from a URL on a schedule. Paste your feed.xml URL.
3. Set country and language. India and English for most stores. If you ship abroad, add those countries later; start with one.
4. Set a fetch schedule. Daily is the usual choice. Merchant Center reads the XML, and each product goes through a review that typically takes a few days on a new account.
5. Fix what Merchant Center flags. New accounts get disapprovals for missing policy pages (returns, shipping, contact), mismatched prices between feed and page, and images with text on them. Publish your policy pages on the store, keep the compare-at price consistent, and use clean product photos.
6. Turn on free listings, then decide about Shopping ads. Free listings cost nothing and are worth having for every store. Paid Shopping campaigns are run from Google Ads and are a separate decision — they are cold traffic, not retargeting.

The Pixel + Conversions API checklist

Audiences are built from Pixel events, and catalog ads match on the product IDs those events carry. If the Pixel is not firing correctly, the feed is a spreadsheet nobody reads. On SitesPlaced the Meta Pixel and the Conversions API are built in on the Growth plan and above — you paste your Pixel ID and a Conversions API token once, and the store fires PageView, ViewContent, AddToCart, InitiateCheckout and Purchase, with the Purchase also sent from the server off the order record and deduplicated.

1. Pixel ID and Conversions API token pasted under Settings → Tracking & code → Meta Pixel & Conversions API, and the card shows connected.
2. In Events Manager, open your store, view a product and add it to the cart: ViewContent and AddToCart appear within a minute, each with a content_ids value that matches a product ID in your feed.
3. Place a test order (COD is fine, cancel it after): Purchase appears twice — browser and server — and Events Manager shows them deduplicated to one.
4. No Pixel base code pasted anywhere else (custom head code, a Meta plugin). A second copy double-counts every event and inflates your audiences.
5. Catalog connected to this Pixel under Catalog → Events, with the match rate shown as a healthy percentage after a day of traffic.

The longer version, with why the server-side Purchase matters on iPhones, is in Meta Conversions API for small online stores and on the Meta Pixel + Conversions API integration page.

A ₹200/day retargeting plan

₹200 a day is ₹6,000 a month — a real amount for a small store, and enough to cover retargeting audiences fully if the store sees a few hundred visits a week. Here is how to split it. Everything below is one campaign with three ad sets, all using Advantage+ catalog ads against your feed.

Run it for two weeks before judging. In Ads Manager look at two numbers per ad set: cost per purchase and frequency. If the Cart set converts at a cost well under your margin, move budget to it from Visitors. If frequency on any set climbs past 4 a week, the audience is too small for its budget — cut the budget, not the window. And if the whole campaign shows no purchases in two weeks with the Pixel verified, the problem is usually the product page, the price or the shipping cost, not the ad.

If you would rather not build this by hand, the Campaign planner in the AI Co-founder tab does the arithmetic for you: give it a goal and a daily budget (and your margin, if you know it), and it picks products from your real best-sellers, works out the break-even return on ad spend, writes five hook angles, lays out the broad → interest → retargeting audience plan and a 7-day schedule with kill and scale rules. It costs 5 credits per plan. The walkthrough is in plan a Meta ads campaign with AI.

Mistakes that waste the budget

• Retargeting before the Pixel is verified. Meta will happily spend on an audience of nobody. Do the checklist first.
• Not excluding buyers. The person who ordered yesterday gets an ad for the same product with a discount they did not get. They notice.
• Using a static image for the Viewed audience. The whole value of that audience is showing the exact product. Use the catalog.
• A discount in every retargeting ad. Buyers learn to abandon the cart to trigger the code. Keep discounts for the Cart set, and not always.
• Windows too long for a small store. A 180-day window on a store with 300 visits a week is a tiny audience shown the same ad for six months. Shorter windows, fresher people.
• Judging after three days. Retargeting audiences are small, so purchases are lumpy. Two weeks is the minimum before changing anything.
• Letting the feed rot. A manually uploaded CSV from March advertises sold-out products in September. A scheduled feed that refreshes itself is the fix — which is why SitesPlaced serves one rather than an export button.

FAQs