Will the URL change when I rebuild the feed?

No. The URL is stable and tied to the channel feed, not to any single build. Rebuilding swaps what the URL serves; the address stays the same, so you never have to re-paste it into the channel.

Is it safe that the feed URL has no login?

Yes, by design. Channels pull it unauthenticated, so the long random token in the URL is the access control. It cannot be guessed or used to find other feeds. Just keep the URL private and share it only with your channel.

I rebuilt the feed but the channel still shows old data. Why?

The channel only sees changes the next time it fetches the URL, on its own schedule. Rebuilding updates what the URL serves instantly; increase the channel's fetch frequency if you need faster pickup.

Your public feed URL (how channels pull it)

Each channel feed has a stable, unguessable URL the channel pulls on its own schedule. How it works, why the token is your access control, and how to use it.

What the public feed URL is

Every channel feed you create gets one stable public URL. You paste that URL into your channel account once (Google Merchant Center, Meta Commerce Manager, TikTok, Snapchat), and from then on the channel pulls the feed from that address on its own schedule. You do not push files to the channel; the channel comes and gets the latest one.

Because the URL is stable, it never changes as you rebuild the feed. You set it up in the channel once and it keeps serving the freshest published build forever.

The token is the access control

The URL contains a high-entropy random token generated when you create the export. That token is the access control: anyone with the URL can read the feed, and nobody can guess or enumerate another tenant's feed. The channels pull it unauthenticated, so the secret in the URL is what protects it.

Treat the URL like a secret. Share it only with the channel you are setting up. There is no login on the feed URL by design, because the channels that fetch it cannot log in.

The token is random and unguessable (generated with a cryptographic random source).
Whoever holds the URL can read that one feed; it cannot be used to find others.
Channels fetch it without authentication, so keep the URL private.

What the URL serves

The URL always serves the current published build of that channel feed, with the right content type (CSV or XML). If a new build was held to protect you (see safe-publish), the URL keeps serving the last good build, so a channel never pulls a broken or empty feed.

Each time a channel pulls the URL, MartechFlow records the fetch. That is how the Diagnostics view can tell you when the channel last pulled the feed and how many times in the last 7 days, which is a quick way to confirm the channel is actually reading it.

Setting it up in a channel

Copy the URL from the channel feed card (there is a copy button next to it) and add it as a scheduled / fetched feed in your channel account.

1Open your feed and find the channel feed card for the channel and format you want.
2Click the copy button next to the feed URL.
3In your channel account, add a new feed and choose the "scheduled fetch" or "fetch from URL" option.
4Paste the URL and set the channel's pull frequency.
5Save; the channel will fetch on its schedule. Use Diagnostics to confirm it pulled.

Freshness and the channel's schedule

The URL serves the latest published build, but when the channel sees a change depends on the channel's own pull frequency, not yours. Rebuilding the feed updates what the URL serves immediately; the channel still only picks it up the next time it fetches.

If you need a faster pickup, increase the fetch frequency in the channel account. If a build is held, the channel keeps getting the last good version until you fix and rebuild, which is the safe behavior.