Your feed is the product data Renable builds and delivers — titles, prices, availability, and the images and videos Renable renders — published at a stable URL. The creative is the actual ad the network assembles from that feed, and the campaign that runs it: budget, targeting, and delivery. Renable controls the feed; the ad network controls the creative and campaign.
The two sides: feed and creative#
Getting your products advertised takes two systems doing two different jobs. Renable owns one side, and the ad network — Meta, Google, or TikTok — owns the other. Almost every "why is this happening" question gets easier once you know which side you're on.
The feed is Renable's side#
The feed is a live, structured list of your products: each product's ID, title, description, link, price, availability, and main image, plus any extra fields a network wants. Renable builds it from your catalog, renders the product images and videos, keeps it accurate as your prices and stock change, and hosts it at a stable URL the network reads. In Renable, a feed is produced by a channel. Everything in this layer you can see and fix inside Renable.
The creative and campaign are the ad network's side#
The creative is the finished ad a shopper actually sees — the network assembles it from your feed, choosing which products to show which person and laying them out for the placement. The campaign is everything that decides whether that ad runs at all: budget, targeting, bidding, schedule, and the network's review of each product against its policies. All of this lives in the ad network's own tools, not in Renable.
The word "creative" can be confusing, because Renable uses it too — you design ad layouts in Renable's Studio, and each project has a Creative tab listing the templates its channels render, alongside your AI ad copy (prompts) and brand assets. Here's the honest line: the image or video a template renders travels inside the feed as a product field, and the copy and assets on the Creative tab are feed-side inputs that shape the product data Renable delivers — so all of that is on Renable's side. The network still assembles that feed into the final, personalized ad unit and decides who sees it — and that assembly plus the campaign around it is the side Renable doesn't control.
Why the line matters#
When an ad isn't behaving, the single most useful question is which side is this on — because the answer tells you where the fix lives. A missing field, an excluded product, or an out-of-date price is a feed problem, and you fix it in Renable. A disapproved product, an exhausted budget, or targeting that's too narrow is a campaign problem, and you fix it in the ad network.
The boundary is firm in one direction that surprises people: Renable can make a product eligible to show, but it can't make the network show it. A perfect feed doesn't guarantee delivery — it just removes every feed-side reason not to deliver. Once the feed side is clean, whatever's left is on the network.
Where each side lives#
The feed side (in Renable). You shape and deliver the feed here:
- The channel that produces and hosts the feed, and its fields, rules, and product sets.
- The catalog the channel pulls product data from.
- Publishing — your edits sit in a draft until you publish, and the live feed the network reads doesn't change until then.
The creative and campaign side (in the ad network). You build the campaign and resolve product approvals in the network's own tools — Meta Ads Manager, Google Ads, or TikTok Ads Manager, and the matching catalog view (Meta Commerce Manager, Google Merchant Center, or the TikTok catalog) — [VERIFY: exact product names and menu paths per network]. None of that lives in Renable.
What Renable does — and doesn't — do#
Renable's job stops at the feed. That's a deliberate boundary, not a gap:
- Renable does build your product feed, render your product images and videos, keep the feed accurate as your data changes, and host it at a stable URL — see Get your products into Meta Advantage+ for how that feed reaches a network.
- Renable does not run your campaigns, set budget or targeting, approve products, or decide who sees your ads. Those are the ad network's, and you manage them there.
A quick way to tell which side a problem is on#
If a product is missing, a field is wrong, or a price is stale, start on the feed side — that's fixable in Renable. Work through Check your ads are eligible to deliver, which walks the feed-side checks in order. If every feed-side check is clean and an ad still isn't showing, the answer is on the campaign side, in the network — see My ads aren't showing.
FAQ#
Does Renable make my ads?
Renable builds the product feed and renders the product images and videos that go into it. The ad network takes that feed and assembles the final, personalized ad a shopper sees, then runs it as a campaign. Renable supplies the ingredients; the network builds and delivers the ad.
I designed an ad template in Studio — isn't that the creative?
That template renders the product image or video, and that rendered media travels inside your feed as a product field — so it's on Renable's side. The ad network still assembles it into the finished ad unit and decides who sees it. Designing the template shapes what the network has to work with; it doesn't run the ad.
Renable says my feed is fine but my ads still aren't showing — whose problem is it?
The ad network's. Once a product is in your published feed with its required fields filled and in stock, Renable's part is done. Check the network for a disapproved product or a campaign that's paused, unfunded, or too narrowly targeted. See My ads aren't showing.
Or ask Aimée#
Aimée works the feed side with you — she can explain which side a problem sits on, trace a single product end to end to find where it dropped out, and fix and publish feed data once you approve. What she can't do is reach into the ad network: she can't approve products there or change your campaign's budget or targeting, because those live outside Renable entirely.