For the complete documentation index, see llms.txt. This page is also available as Markdown.

Adding a feed

Set up a CSV, XML, or JSON feed with the setup wizard.

Content Egg includes a dedicated module for working with product feeds in CSV, XML, or JSON format. This page covers adding one with the setup wizard, the feeds and URLs it supports, and how the feed keeps itself in sync afterward.

The setup wizard

Go to Content Egg > Modules and click Add a Feed to open the setup wizard.

  1. Paste the feed URL. That's the only thing you need to enter on this step. The wizard downloads a sample and automatically detects the format, encoding, currency, merchant domain, and CSV/decimal settings — you don't need to know any of this in advance.

  1. Map the fields. The plugin already fills in some of the mapping deterministically, based on common feed field names. Real sample rows from your feed are shown next to the mapping panel, along with a live preview of the first product, so you can confirm everything looks right. Click Map with AI to have the AI assign the remaining fields, or finish mapping any field manually.

  1. Confirm and import. Give the feed a name, choose how often it should sync, then click Save & import products. The import runs in the background with a live progress view, so you can leave the page and come back once it's done.

If the wizard can't detect your feed's parameters correctly, click Set up manually in the top-right corner of the page. This takes you straight to the classic module settings page, where you can enter every setting by hand.

Once the import finishes, your products live in a local library, ready to use. See where your products go for what to do next.

Supported feeds & URLs

  • Direct access: The feed must be reachable at a direct, live URL — no login page or authorization step in front of it.

  • Formats: CSV, XML, and JSON are supported. CSV is recommended when available, for better performance and simpler configuration.

  • Archives: ZIP and GZ (GZIP) are supported. The wizard detects compression automatically; when setting up manually, select the matching Archive format option.

  • Protocols: http://, https://, ftp://, and ftps:// URLs are all supported.

Type
Example

HTTP / HTTPS

http://www.example.com/data.csv

https://www.example.com/data.zip

FTP (anonymous)

ftp://ftp.example.com/path/to/feed.xml

FTP (with login & password)

ftp://user:pass@ftp.example.com/path/to/feed.xml

ftp://user:pass@aftp.linksynergy.com/12345_123456_mp.xml.gz

FTP (encoded credentials)

ftp://user:pass%40123@ftp.example.com/path/to/feed.xml.gz

(%40 = @, %3A = :, %2F = /)

FTPS (secure FTP)

ftps://user:pass@secureftp.example.com/path/to/feed.xml

How syncing works

  1. Loading the feed file: The feed file is downloaded to your server and cached. An unchanged feed is not re-downloaded or reprocessed on the next sync.

  2. Importing offers: The plugin imports offers into the local database. Imports always run in the background, so saving settings or reloading a feed never blocks the page.

  3. Product search: You can search feed products as you would in any other Content Egg module. If an import is still running, search shows a "please wait" message until it completes.

  4. Regular syncs: By default, feed data is considered stale after 12 hours. The plugin re-syncs it in the background the next time that data is actually requested (e.g. someone views a page or admin screen using it) — not on a fixed clock. On a very low-traffic site, a refresh may take longer than 12 hours if nothing requests the feed in the meantime. You can change this interval (from every hour up to once a week) in the wizard's last step or in the module settings — both control the same Feed sync interval option.

  5. Adding more feeds: Each feed is a separate module — repeat the steps above from Content Egg > Modules.

Video walkthrough

This walkthrough predates the current setup wizard, so the interface looks different — it's still a useful overview of the overall workflow.

Last updated