Snapchat Dynamic AdsThe catalog is the easy half of Snapchat Dynamic Ads

Renable writes your products to Snapchat’s own spec — RSS/XML, CSV or TSV at a feed URL Snapchat fetches as often as every hour — and checks every field per product before you publish. The two things that actually gate Dynamic Ads live on your store, not in Renable, and we tell you what they are up front.

Dynamic Ads, straight from your feedHourly refresh at both endsChecked against Snapchat’s spec
Channel
Ready to publish842 in · 842 out
Required fieldsall present
One of brand, GTIN or MPN842 covered
Image formats18 GIFs converted
Feed refreshhourly

Output

feeds.renable.com/sportgear/snapchat.xml

Simplified view of a channel’s pre-publish checks, for illustration.

Early access

The Snapchat channel is rolling out now. Start free and we’ll get you set up as it lands — talk to us if you want it sooner.

Start here

The feed is the part we can fix. Here’s the part that’s on you.

Snapchat Dynamic Ads run off a product catalog, and a catalog is a feed at a URL. Renable can have that feed written to Snapchat’s spec, checked per product and hosted, in an afternoon. That part is genuinely easy, and any tool that tells you otherwise is selling the wrong thing.

What no feed tool can do for you is the other half — two prerequisites that live on your own site and inside your Snapchat account. You’ll meet them either way. Better now than after you’ve built the feed.

What Renable handles

The feed itselfRSS/XML, CSV or TSV
Required fieldschecked per product
One of brand, GTIN or MPNvalidated as written
Hosting and refreshhourly, at a stable URL

All of it checked per product before the feed goes out — you see the count, and which products, before Snapchat ever fetches.

What has to be true on your side

The Snap Pixel is installedyour store
Its item ids match your catalog idsyour store
Pixel events match 1,000 SnapchattersSnapchat’s gate
Organization Admin on a business and ad accountyour account

Snapchat’s own words: “To access Dynamic Ads, your pixel events must match 1,000 Snapchatters.” That gate is Snapchat’s, and no feed clears it for you.

One of those four we can actually help with: if your pixel already sends a product id, Renable can make the feed’s id the same id — that’s a mapping rule, and it takes a minute. The rest is work on your own site, and it’s worth doing before you build anything.

The spec

Familiar fields, different rules

If you already run a shopping feed, most of Snapchat’s field names will look familiar. The spec underneath them is Snapchat’s own, though, and the differences are the quiet kind — the ones that cost you products instead of throwing an error. Renable writes to Snapchat’s spec, not to a generic one.

Only one of brand, GTIN or MPN

Snapchat puts it plainly: only one of brand, gtin or mpn is required. A product with a barcode and no brand is fine here, where other destinations would flag it. Renable validates the rule as written — one identifier present per product, not three.

Availability has values you don’t have

Snapchat adds Discontinued and Available for order, and it has no backorder value at all. An availability value Snapchat doesn’t list isn’t a safe default — Renable maps yours onto Snapchat’s list for this channel only, leaving your other feeds untouched.

WebP is fine here. GIF is not.

That’s the reverse of some destinations, which is exactly why it gets missed. Renable converts what Snapchat won’t take, and you can send up to 20 extra images per product on top of the main one.

Limits that truncate quietly

The product id caps at 128 characters and the title at 375 — long enough until a variant export starts composing ids. Snapchat also writes size_system as MEX where Google writes MX. Renable checks the lengths and the spelling before the feed goes out.

Channel
ActivityPreviewFieldsRulesSettings
FieldValueFill
idsku100%
titleproduct_name100%
priceprice100%
availabilitystock_status100%
brand / gtin / mpnmanufacturer93%· 63 empty
additional_image_linkgallery88%

63 products carry none of the three identifiers, so the one-of rule flags them by name — before the feed goes out, not after.

Simplified view of a channel’s field mapping, for illustration.

Scale isn’t the constraint here: Snapchat takes up to 10 million items in a catalog, a feed up to 14 GB, and 200 catalogs per organization. A gzipped .gz file is fine if you want it smaller — Snapchat states it doesn’t read .zip archives, and Renable never writes one.

Under the ad

What Renable feeds Snapchat

Dynamic Ads are built from your catalog, so the catalog is the creative. One set of products, cleaned once, written the way each destination expects.

A clean, mapped feed

Your data mapped to Snapchat’s catalog fields, corrected by rules and lookups, and re-imported roughly every hour so prices and stock stay current.

Fix the feed IT won’t touch

Copy written from your own data

AI writes titles and descriptions from each product’s own data and fact-checks every claim against it — in each market’s language, inside the lengths Snapchat allows.

See how the copy is written

Your customers’ words in the creative

Connect Trustpilot, Bazaarvoice, TestFreaks, Yotpo or a Google review feed, and the best quote for each product renders into that product’s image — which is what the feed points Snapchat at.

Put your customers’ words on screen

FreshnessAn hourly loop, end to end

Renable re-imports your data roughly every hour and rewrites the feed at a stable URL. Snapchat fetches that URL on a schedule you set — hourly or daily — and hourly is the fastest refresh contract of the destinations we’ve added.

Run both ends hourly and the catalog Snapchat reads is at most an hour behind your store. A price change or a sold-out size stops being a thing you find out about tomorrow.

Feed freshness

Renable

re-imports hourly

Hosted URL

always current

Snapchat

fetches hourly

Hourly is Snapchat’s own setting
Snapchat will fetch a scheduled feed hourly or daily. Hourly is the fastest cadence of the destinations we’ve added — take it.
A file you upload by hand is not
A manual upload is only as fresh as the moment you made it. A hosted URL removes the step and the drift with it.

Simplified view of the feed schedule, for illustration.

Add-ons

A product video in the feed — and 20 images beside it

Renable includes your product video in the Snapchat feed so it can be used for Product Level Video Ads — you configure the automatic template layout and preferred video tags in Snapchat Ads Manager. Design one video template in Studio and every product gets its own render, bound to its own data.

In Renable

A video rendered per productone template
Carried in the feed’s video fieldper product
Extra product imagesup to 20
Copy and voiceover per marketper language

Extra images ride additional_image_link — up to 20 per product. What Snapchat does with them is Snapchat’s call.

In Snapchat Ads Manager

The catalog on the commerce verticalyour setup
A Dynamic Template on the automatic layoutyour setup
Preferred video tags on that templateyour setup
An ad type that supports product videoyour setup

A Dynamic Template on any other layout will not surface a product video. That’s Snapchat’s rule, and it’s the one people trip over — so we say it here rather than let you find it later.

No rip-and-replace

Keep the catalog you’re running. Put ours beside it.

Other destinations let you layer a supplementary feed over an existing catalog. We won’t promise that on Snapchat — Snapchat’s own documentation contradicts itself on whether it exists, so we treat it as unsupported rather than sell you something that might not be there.

What does work is a parallel run. Connect the feed behind your current catalog as a source, reshape it in Renable, and stand a second Snapchat catalog up on the Renable feed. Compare the two — product counts, fields, the products each one drops — and move your ad sets across in Ads Manager when the output agrees. Nothing has to change on day one.

The catalog you run today

untouched

A Renable catalog beside it

same products, written to spec

Compare, then cut over

on your timeline

Diagnostics

“Why aren’t my products showing in my Snapchat catalog?”

Snapchat runs automated checks on your feed and won’t walk you through which product broke or why. Renable catches it first, names the exact products, and tells you what to change. Here’s what it usually is:

No identifier at all on the product
Snapchat needs one of brand, gtin or mpn. Not all three — but not none either, and a catalog built from a bare export often has none.
63 products
An availability value Snapchat doesn’t use
Snapchat has Discontinued and Available for order, and no backorder at all. Map your values onto Snapchat’s list rather than hoping an unknown one is ignored.
41 products
An image format Snapchat won’t take
WebP is accepted here and GIF is not — the opposite of what people assume. Renable converts them before the feed goes out.
18 products
A product id past 128 characters
Composite ids from a variant export run long fast. Snapchat caps the id at 128 characters and the title at 375 — both checked before publish, and both fixable with a rule.
The catalog is fine — the pixel isn’t
If the products are in the catalog and Dynamic Ads still won’t run, look at the Snap Pixel: its item ids have to match your catalog ids, and your pixel events must match 1,000 Snapchatters before Dynamic Ads open up.
Excluded by a rule (working as intended)
An exclude rule dropped it on purpose — sold out, clearance, a brand you don’t advertise. The trace says so, so it never looks like a fault.
Channel
ActivityPreviewFieldsRulesSettings
Traced Ridge Daypack842 in · 779 out

What the trace found

In the channel’s product setapplied

scope: included

Exclude rulesapplied

no match — kept

Required · one of brand, gtin, mpndidn’t apply

all three empty

Snapchat needs one of the three, and this product has none. Your manufacturer column fills brand for 61 of the 63 — on this channel only.

flagged by required-field check

Simplified view of a channel trace, for illustration.

Aimée

Why is the Ridge Daypack missing from my Snapchat catalog?

It’s in the product set and no rule excluded it. Snapchat wants one of brand, gtin or mpn and this product has none of the three — 63 products are in the same state. Your manufacturer column covers 61 of them.

Traced Ridge Daypack · found the gap

Draft fix ready — map brand from manufacturer on the Snapchat channel only. Nothing goes live until you publish.
Scope · includedRules · keptIdentifier · missing
Publish fixNot yet

Or just ask Aimée

Skip the digging. Ask why a product is missing and Aimée reads the same checks and logs, names the step that dropped it, and drafts the fix — for you to publish.

SetupFrom a store URL to a Snapchat feed, in one conversation

Give Aimée your store URL and she imports the catalog, maps the feed to Snapchat’s fields, applies the spec checks, and tells you exactly which products needed changing. Configuration is human-gated: everything she builds is a draft until you publish it.

Renable hosts the feed at a stable URL. You create the catalog on Snapchat’s side — that needs Organization Admin on a Snapchat business account and an ad account — paste the URL once, set the fetch schedule, and updates flow through on their own.

Aimée

Set up a Snapchat channel for sportgear.com.

On it. I’ll import the store, write the feed to Snapchat’s spec, and check the one-of-three identifier rule per product. Everything lands as a draft first.

Checked 842 products against Snapchat’s spec

Built a Snapchat channel · 842 products

Saved as a draft — nothing reaches Snapchat until you publish it.
Feed mappedAvailability mapped18 images convertedVideo field on

Publish, and I’ll hand you the feed URL to paste into your Snapchat catalog. Set the fetch to hourly while you’re in there.

Publish channelReview first

Renable builds the feed and the creative. Snapchat runs the campaigns.

What Renable controls is that Snapchat gets the best possible version of every product — a clean feed in a shape Snapchat reads, checked against its spec before it goes out, with the images and video rendered from your own data.

Budgets, targeting, bidding and delivery stay in Snapchat Ads Manager. Renable doesn’t manage your campaigns, and it never learns whether Snapchat accepted an individual product — that lives on Snapchat’s side.

Dynamic Ads themselves are configured over there too: the template layout, the video tags, the ad type, and the pixel gate. We make the catalog the strongest candidate we can. What Snapchat shows is Snapchat’s decision, and no feed tool can promise otherwise.

Everything above, on the free tier

Channels aren’t a paid add-on, and neither is video. Add Snapchat alongside the channels you already run and pay only for the feed items your rules keep.

Free for your first 100 items — no cardNo % of ad spend, everUnlimited seats

Trusted by retailers like Webhallen.

Running your product feed on a feed tool today?

Snapchat Dynamic Ads, answered

How do I set up a Snapchat product catalog for Dynamic Ads?
Renable publishes your products as RSS/XML, CSV or TSV at a stable feed URL. You create the catalog on Snapchat’s side — that needs Organization Admin on a Snapchat business account and an ad account — paste the URL in, and set the fetch schedule to hourly or daily. Renable itself re-imports your data roughly every hour, so hourly on both ends keeps the catalog at most an hour behind your store. Aimée can build the whole channel from your store URL.
Why aren’t my products showing in my Snapchat catalog?
Usually one of five things: no identifier at all (Snapchat needs one of brand, gtin or mpn), an availability value Snapchat doesn’t use, a GIF image, a product id past 128 characters or a title past 375, or an exclude rule that dropped it on purpose. Renable checks all of them per product before the feed goes out and names the products. If the catalog itself looks right and Dynamic Ads still won’t run, the cause is almost always the pixel — see below.
Can I run video ads on Snapchat from my catalog?
Renable includes your product video in the Snapchat feed so it can be used for Product Level Video Ads — you configure the automatic template layout and preferred video tags in Snapchat Ads Manager. There’s more to it than the feed: the catalog has to be on the commerce vertical, the Dynamic Template has to use the automatic layout (any other layout will not surface a product video), and the ad type has to be one that supports it. All of that is set on Snapchat’s side. Catalog-driven Collection ads use images, not video.
Do I need the Snap Pixel?
Yes. The Snap Pixel has to be installed on your store and pass back item ids that match the ids in your catalog, and Snapchat gates the format itself: “To access Dynamic Ads, your pixel events must match 1,000 Snapchatters.” Renable can’t clear that for you. What it can do is make the feed’s id the same id your pixel already sends, which is the half of the problem that usually breaks.
Can I keep my existing Snapchat catalog?
Yes — run them in parallel. Connect the feed behind your current catalog as a source, reshape it in Renable, and stand a second catalog up on the Renable feed. Compare the two until the output agrees, then move your ad sets across in Ads Manager on your own timeline. We deliberately don’t offer a supplementary feed on Snapchat: Snapchat’s own docs contradict themselves on whether it exists, so we treat it as unsupported rather than promise it.
Does Renable manage my Snapchat campaigns or budget?
No. Renable builds the feed and the creative; Snapchat runs the campaigns. Budgets, targeting, bidding and delivery all stay in Snapchat Ads Manager, along with the Dynamic Ads setup itself. What Renable controls is that Snapchat gets the best possible version of every product.
What does it cost?
Free for your first 100 items — no credit card. Paid plans are a flat price per feed item your rules keep, with no percentage of ad spend and unlimited seats, and channels are never a paid add-on. See pricing for the full ladder.

Put your catalog on Snapchat properly

Start free, and see what Snapchat would have quietly dropped — and what your store still needs — before you publish.