Feed Destinations

Productsup provides a standard set of Feed Destinations that already cover a large number of cases. If a feed just needs to be provided as a link, pushed to an FTP, a Cloud Storage Bucket or a Google Sheet, this article provides the information needed.

In Setup you can determine the feed Destination, which is the place your final feed will be exported to. The setup is only accessible after the export is activated.

To add a destination click on the Add Destination button and choose between the following options in the dialog window that opens afterwards.

8d04d667b5fe52b77911a81529931819.png

Choosing the right destination

When adding a destination, you will be asked to provide a name.

Option 1: Upload the feed to the Productsup server

4c1b5425ee994af0f86ed9b5d52e97e4.png

This will upload the final feed to the Productsup Server where it is accessible without a username or password. A unique URL will be generated based on site and channel parameters.

Important: Our retention policy for the files on the Productsup server looks as follows:

  • We keep historic files back to 12 months even if they are not requested

  • We keep historic files for more than 12 months if they were requested within the last 12 months

This does apply to files the Productsup Server only, not to the ones exported to a user created FTP account on our platform. Files stored on these will stay for the entire duration of the partnership.

Option 2: Upload the feed to an FTP Server

f5ac2bb4ea530a0dfd4d7c9eda55d4af.png

Enter the FTP server information that is necessary, set it to "Active" and save.

This option is preferred if you want to upload your feed to a server that is protected with username and password. You can create your own FTP server if you follow the steps described in Create an FTP server hosted by Productsup. The FTP underlies the same retention policy as the Productsup Server.

Option 3: Upload the feed to an SFTP Server

17d9f363cce0c3dbffe784acddded8dd.gif

You can upload the feed to an SFTP server after filling in all necessary information in the input fields. For this destination you can also choose between entering a password or an SSH key. Don't forget to set the server to "Active" and save.

This destination gives you the possibility to write a ".fin" file to the server, once the upload is finished. This will notify the SFTP server that the upload is done entirely and the feed can be picked up. The old .fin file will be deleted once a new upload starts.

Set this option to "On" if you want this additional file to be created.

Option 3.1: Upload the feed to an SFTP Server via Proxy

6149d61266661.gif

If you need to whitelist our IPs, you can choose the destination SFTP Server (with proxy) and activate the proxy by clicking the Proxybutton.

Option 4: Upload the feed to the Google Merchant Center FTP/SFTP (for Google Merchant Center only)

eb4895ab7f147e298e7a6c2aa5d8f85f.png

Enter your Google FTP username and password, set the server to "Active" and Save.

If you created an SFTP in the Merchant Center, add the destination "Google Merchant Center SFTP Destination" instead and follow the same steps:

642bee5012245a6e1dd3b732bf8b85db.png

Keep in mind: This is not your Google Merchant Center login, but the credentials to access the server you created within the GMC.

To learn more about the upload to the Google Merchant center, read out article: Add Data Feed to Merchant Center.

Option 5: Upload the feed via Google Sheets API

First you need to choose the Google Spreadsheet export in the Exports A/B tab and add the needed columns in the Dataflow tab since this export template is completely blank. In the setup section for this export choose the Google Sheets API from the dropdown list.

7697ed109dab48142d63e093a77c6f3e.jpeg

Fill in the Authentication information, the Sheet Name and the Sheet Prefix if defined with a different name. To activate that export click on Save. If you want to deactivate it click on the button Off below the word Active.

ead05bb3dddf903e6507f26db236acc9.png

Option 6: Upload to Amazon S3

Before you can upload your feed to Amazon S3, make sure that one of the two conditions is met:

  • The Access Key ID you are using has been granted access to the bucket..

  • Your bucket has been created as a public bucket.

We strongly recommend the first option as it is more secure

Figure 1. TITLE
TITLE


Select your S3 region, enter your bucket name, and also a base path, if applicable.

Option 7: HTTP Post Request Destination

If your system has an API Endpoint that accepts feed files, you can upload the feed directly to your API, using the HTTP Post Request Destination.

Enter the URL to your endpoint and choose the Method from the dropdown, you can choose between HTTP POST and HTTP PUT. Choose the Transfer method, either binary data body or multipart/form-data (Form Based) and enter the File field name. If necessary, enter Username and Password.

Activating "Upload response contents" will upload the HTTP response into a file that can be found on the bottom of the export setup page.

Activating "Via Proxy" will upload the data using our proxy servers, this can be used incase a limited number of IPs is needed to whitelist.

Figure 2. TITLE
TITLE


Option 8: Upload to Microsoft Azure Blob Storage

To upload to Microsoft Azure Blob Storage, you need to prvode the name of the target Container, your Storage account name and your Access key.

Figure 3. BlobStorage
BlobStorage


Option 9: Upload to Google Cloud Storage

To upload to Google Cloud Storage, select or add your Google Cloud authentication first. Enter the name of the bucket and directory that the file should be send to. Both support the use of placeholders to dynamically populate bucket and directory names and paths. The following placeholders are supported: - {{Site.name}}: Uses the site name as bucket name/path - {{Site.id}}: Uses the site id as bucket name/path - {{Export.name}}: Uses the export name as bucket name/path - {{Export.id}}: Uses the export id as bucket name/path

In case the site or export name contains a /, it needs to be replaced, as this normally indicates a new folder. This can be done with a Replace filter.Example: {{Export.name| replace({ "/":"_" })}}This will replace the forward slash / with with an underscore.

Figure 4. GoogleCloud
GoogleCloud


Option 10: Upload to a WebDav Destination

To upload to a WebDav destination, you can utilize our HTTP Post Request destination.

Add the URL to your WebDav destination and activate "Append filename to the URL".Choose the Method "PUT" and "binary data body" for transfer.Set the file field name to "file" and add the header "Content_type: text/plain".Enter your username and password, if you need to authenticate.Click save.

Figure 5. webdav
webdav


Finding your feed URL

You need to copy the feed URL in order to send it to your export partner. They need to integrate it into their system and can import the feed on their side whenever it is updated.

When choosing the Productsup Server, the FTP or SFTP server as an export destination, you will find your feed URL in the "Files" section next to the Filename and the limit. Remember to send the password and username in case your feed is password protected.

You can also find the URL together with the time of the last export on the very bottom of the page.

407e744f126333cdff85e38ce5605ddc.png
70bc4bbaae76657aad3743e6500df535.png

If you want to edit your filename or output format, you can find more information in Add export channel.

Export via the Productsup Proxy Servers

If your export destination needs to whitelist certain IPs in order to guarantee a successful upload, you can add the word proxy in front of the host. Please be aware that this will only work for our FTP Server Export Destination:

Example: proxyftp://...

You can find the IPs of our proxy servers in the Data Sources tab under Settings > Services. They are as follows:

148.251.96.244

148.251.96.243

78.46.60.217

78.46.61.222

78.46.60.184

78.46.60.183