SyncHTTP / HTTPS
Fetch a catalog file from any reachable URL, with optional basic auth.
What we read. Where we publish.
Sync sits between one source catalog and every destination that consumes it. The source side is deliberately boring — if a system can expose a file, Sync can read it. The channel side is where the per-destination logic lives.
01Channels
Destinations we generate and serve feeds for.
Each channel gets its own live endpoint, its own field mapping, and its own product set. A custom destination is a supported case, not an exception.
- Google Shopping
- Meta
- TikTok
- Snapchat
- MoEngage
- Live Shopping
- Custom XML
- CSV
- TSV
02Sources
Where the catalog comes from.
Credentials are stored per shop. Sync pulls on schedule, skips files that have not changed, and records the result of every import.
SFTP
Pull from a protected drop with stored credentials on a schedule.
Shopify
Connect the store catalog directly as a managed source.
XML
Parse structured catalog exports, including nested product nodes.
CSV / TXT
Delimited exports with auto-detected separators and encodings.
TSV
Tab-separated exports handled as a first-class source format.
03Output formats
What the channel actually receives.
Feeds are regenerated on a schedule, during campaign windows, or on demand. If a refresh fails, the last valid feed stays online rather than serving a partial file.
XML
Served live per channel, the format most ad platforms expect.
CSV
Delimited output for marketplaces and internal consumers.
TSV
Tab-separated output where a channel requires it.
Not on the list?
Most custom destinations are a mapping, not a rebuild.
If your channel takes a structured file, it is usually a new field mapping rather than new infrastructure. Send us the spec and we will tell you honestly whether it fits.