A channel produces a feed at a stable URL. This article covers the other side: telling an ad network to read that URL as its product catalog source. This is a one-time setup per network — after that, updates flow through automatically.
Before you paste the URL anywhere, check the channel's Used for setting (Settings tab). That's where you tell Renable which network reads this feed and how it's used there — whether it's the network's Main feed or a Supplementary feed, plus any add-ons the feed carries (video, extra images, or Google's AI discovery fields). It doesn't connect anything by itself; it's what makes Renable check your fields against that network's requirements, so it's worth setting before you hand the URL over. See Working with channels.
One destination works differently: OpenAI's merchant program doesn't fetch a URL — the feed is pushed to it, and listing requires OpenAI's approval first. See The ChatGPT shopping feed.
Microsoft does fetch a URL, and the steps follow the same pattern as the networks below — add a feed in Microsoft Merchant Center using its automatically download file from URL option, which is the only method Microsoft schedules for you. Two things are Microsoft-specific and worth reading first: your store has to be verified and approved before a feed can be added at all, and a feed Microsoft hasn't re-fetched for 30 days expires. Also check whether you need a Renable channel at all — if you already run Google Shopping, Microsoft can import your Google Merchant Center store directly. Both are covered in The Microsoft shopping feed.
Snapchat also fetches a URL — you add the channel's feed URL as a data feed on your Snapchat catalog, and Snapchat refreshes it hourly or daily. The part that isn't about the feed is the part that catches people: Snapchat Dynamic Ads need the Snap Pixel installed and passing back the same product IDs, and Snapchat only opens the format once your pixel events match 1,000 Snapchatters. See The Snapchat feed.
Pinterest fetches a URL too, but on the slowest schedule of any destination here — once every 24 hours, at a time of day you choose, with no on-demand option. What catches people out with Pinterest is everything that has to be true before a catalog will attach: a business account, your website claimed, the Pinterest tag installed, and a site meeting Pinterest's merchant guidelines. See The Pinterest feed.
Reddit fetches a URL too, on a sync schedule you set in Reddit Ads Manager. Two Reddit-specific things: never put a username or password in the feed URL (Reddit has separate fields for those), and the catalog on its own runs nothing — Reddit requires the Reddit Pixel or the Conversions API on your store before Dynamic Product Ads will deliver. See The Reddit feed.
Perplexity takes either route: a hosted feed URL it fetches, or an SFTP push using credentials issued during merchant onboarding. Both come after approval — Perplexity's merchant program is an application you make, and it is US-focused as of mid-2026, so for many merchants there is nothing to connect the feed to yet. Perplexity publishes no fetch schedule, so don't assume one. See The Perplexity shopping feed.
Prisjakt fetches a URL too, but there's an approval step before there's anywhere to connect it to: Prisjakt approves each shop before it's listed, you apply per market, and the application form asks for the feed URL — so publish the channel first and apply with the URL in hand. Renable can't push to Prisjakt (its push routes are a manual upload in Business Center or its own feed API), and how often Prisjakt re-reads the URL is set by your Prisjakt package rather than by Renable, so don't assume an interval. See The Prisjakt feed.
PriceRunner fetches a URL too, and there's a sales step before there's anywhere to connect it to: PriceRunner has no signup form — you email its retail team, they set your shop up, and becoming a paying customer means a cost-per-click agreement with a monthly budget you set. Renable can't push to PriceRunner (it takes a hosted HTTPS address or a plain FTP server, both of which mean PriceRunner fetching from you). Once it is reading the URL, keep it stable — PriceRunner warns that a changing feed address makes products disappear, and in Renable the URL only changes if you change the file format or the compression switch. It imports one to four times a day, and a brand-new product can take up to 24 hours to appear. See The PriceRunner feed.
Criteo fetches a URL as well, and adding it is self-serve inside Criteo's Management Center — you paste the feed URL under Product Catalog, pick the delimiter and price format, and Criteo shows you how it parsed the file before you save. Criteo can also read a file pushed to its own SFTP server, so the channel's SFTP delivery section is a real option here if that is how your account was set up. Two Criteo-specific things: it reads the file up to four times a day at times you schedule in UTC, so an edit lands at the next import rather than immediately; and the feed alone runs nothing — Criteo's OneTag script has to be live on your store, sending the same product IDs this feed sends. Whether you can open a Criteo account yourself depends on your market: the self-serve signup covers the US and the UK, and everywhere else Criteo's team sets the account up under a contract. See The Criteo feed.
A new channel gets its first URL automatically, a few minutes after you create it — no Publish click needed for that first deployment. From then on, any settings, fields, or automations changes you make land on a draft, and you do need to publish before the ad network sees them. Start by copying the channel's URL from the channel page.
Meta (Facebook / Instagram)#
- In Meta Commerce Manager, create (or open) a catalog for the products you're advertising.
- Add a data source and choose the scheduled-feed / feed-URL option, rather than a manual upload.
- Paste in your Renable channel URL and set a fetch schedule — hourly is a reasonable default, matching how often Renable itself refreshes.
- Save, and trigger an initial fetch if Meta doesn't run one automatically.
[VERIFY: exact current menu path and terminology in Meta Commerce Manager — "Data Sources," "Feeds," and scheduling options are renamed periodically by Meta.]
See Meta's own docs: Meta Commerce Manager catalog fields.
Connecting your Meta ad account#
Once your channel feeds a Meta catalog, you can also connect the Meta ad account that runs ads from it. This gives Renable read access to those ads, so it can understand how your designs are used on Meta.
That connection belongs to your organization, not to one channel — you connect an ad account once and it covers every Renable channel feeding a catalog that account advertises. So it isn't set up here: open the settings menu (the cogwheel in the top right), choose Integrations, and follow Integrations.
Connecting an ad account never changes any feed, and your catalog connection keeps working whether or not you connect one.
Google (Merchant Center)#
- In Google Merchant Center, go to Products → Feeds and add a new feed.
- Choose the scheduled-fetch option and enter your Renable channel URL.
- Set the fetch frequency and time.
Once the feed is flowing, you can also add the fields Google's AI shopping surfaces read — see AI discovery on Google.
See also Finding your feed in the Google Merchant Center and Google Merchant Center fields. If you're connecting Google Merchant Center as a live API integration instead of a feed URL, see Connecting Google Merchant Center — that's a different setup from pasting a channel URL.
TikTok#
- In TikTok's Catalog Manager (Business Center), create or open a catalog.
- Add a data feed and choose the scheduled feed / feed-URL option.
- Paste in your Renable channel URL and set the fetch schedule.
[VERIFY: exact current menu path and terminology in TikTok Catalog Manager.]
See TikTok Catalog product parameters.
Verifying the ad network picked up the feed#
- Check the network's own catalog/feed dashboard for a "last fetched" timestamp and item count. That count should roughly match the latest render's entry count on the channel's Activity tab.
- Compare a product or two side by side — the exact field values in the network's catalog view against the channel Preview tab's Source view.
- Most networks flag individual items that fail validation (bad price format, missing required field, disapproved image). Those errors point back to a field or automation that needs adjusting on the Renable side.
Troubleshooting "my feed isn't updating"#
Work through these in order:
- Did you publish? Renable only deploys the published version of a channel — a draft with unpublished changes doesn't affect the live feed at all. See Publishing a channel.
- Has enough time passed? Background changes (price, stock, new products) can take a few minutes to reach the published feed; the ad network then fetches on its own schedule (often hourly) on top of that.
- Is the channel archived, or over a plan limit? Both of these cause Renable to intentionally deploy an empty feed — this isn't a bug, it's how Renable stops advertising a catalog it shouldn't be serving. Unarchive the channel, or check plans and limits, and republish.
- Check the Activity tab on the channel for warnings or errors from the last render.
- Check the ad network's own feed status page — the fetch may be failing on their side (auth, format validation) even though your Renable feed is current.