Make a feed available
Host your Tweakwise feed at a public URL, usually on the same server as your e-commerce platform, so Tweakwise can import it over HTTP or FTP.
Tweakwise imports your product feed by downloading it from a URL. Once your feed generator produces a valid feed, you need to publish it at a location Tweakwise can reach over the internet.
In most setups the feed is generated and served by the same server that runs your e-commerce platform. For example, a scheduled job writes feed.xml to a public folder of your webshop, and your web server exposes it at https://www.yourstore.com/feeds/feed.xml.
Any publicly reachable HTTP or FTP location works, as long as it ends in a stable URL.
The URL you end up with is what you enter in the feed import task. See Import a feed.
Choose a protocol
Tweakwise can retrieve your feed over:
- HTTP/HTTPS (recommended). Works with the web server you already run for your shop.
- FTP. Useful if your feed is delivered to an FTP server by an existing process.
Which one fits depends on how the feed is generated and on your infrastructure. Agree on the approach with your implementation partner.
FTP does not support encryption. Tweakwise does not support the secure variants SFTP and FTPS. Anyone who can intercept the traffic can read the feed. This is acceptable only if the feed contains no sensitive data.
Make the feed available
- Generate the feed to a location your web server (or FTP server) can serve, for example a public folder on your webshop server.
- Expose the file at a stable URL, for example
https://www.example.com/feeds/feed.xml. - Open the URL from outside your network and confirm the full feed downloads.
- Use this URL in the HTTP URL field of your feed import task.
If the feed should not be readable by everyone, see Secure a feed.
Web server requirements (HTTP)
This section is for the person configuring the web server. Setting up a web server is out of scope for this guide. There are no equivalent notes for FTP.
TLS
Your web server must support a TLS version that the Tweakwise HTTP client supports.
- The client technically supports TLS 1.0, 1.1 and 1.2. Versions below 1.2 are insecure and should not be used.
- TLS 1.3 is not supported, and this will not change in the foreseeable future.
- Configure your web server to support TLS 1.2.
To check which versions your server supports, run a test with Qualys SSL Labs.
If the TLS versions do not match, the import fails with an error like
Could not create SSL/TLS secure channel. Check the TLS configuration of your web server first.
Caching
Disable caching entirely on the URL that serves the feed. This prevents Tweakwise from importing a stale feed.
If you cannot disable caching, make sure your web server honors the headers Tweakwise sends with every request:
Pragma: no-cache
Cache-Control: no-store, no-cache, max-age=0Do not assume the default configuration honors these headers. Verify it, for example by requesting the feed twice after changing it and checking that the second response contains the new content.
Compression (optional)
The Tweakwise HTTP client supports gzip. It reduces bandwidth and speeds up the download. It is not required.
Tweakwise sends this request header:
Accept-Encoding: gzipTo support it, respond with the header below and a gzip-compressed body:
Content-Encoding: gzipNotes
- The feed URL must be reachable from the internet, not only from your internal network.
- Keep the URL stable. Changing it requires updating the feed import task.
- If you restrict access by IP address, allow the Tweakwise ranges listed in Secure a feed.
FAQ
Can I host the feed on the same server as my webshop?
Yes. This is the most common setup. Write the generated feed to a public folder of the webshop and serve it through the existing web server, then use the resulting URL in the feed import task.
Does Tweakwise support SFTP or FTPS?
No. Only plain FTP and HTTP/HTTPS are supported. Prefer HTTPS when the feed contains sensitive data.
The import fails with "Could not create SSL/TLS secure channel". What should I check?
Check that your web server supports TLS 1.2. Tweakwise does not support TLS 1.3, and versions below 1.2 are insecure.
Next step
Updated 15 days ago