Channel Deployment

Channel Deployment is a  feature that allows you to transfer configurations from a test channel to a productive channel with just one click. For example, you can test settings for the search algorithm and, if you like them, deploy them immediately. This eliminates the effort of having to manually configure all settings again in the productive channel.


The deploy function requires the same data structure in the test and production channels!

The deploy function may be used if the same CSV data is used in the current test channel and in the future (i.e. the current one after the deploy function has been executed) production channel. At least the header of test- and production-CSV files must be the identical. Please also note that all other configured settings, such as the import schedule, are transferred from the test channel to the production channel during the deploy process.


It is best to test the import of the post-deployment production CSV data (i.e.: the future live CSV data) in the test channel beforehand. If this test is successful, because both channels use the same CSV data, the test channel can be deployed to the production channel.


The function has been integrated directly into the Channel Installer.

Setting up a Deployment Target

To use a channel as a deployment target, select the corresponding test channel and click on the  icon to clone it.

If necessary, you can make further settings here, but for this function it is only important that the channel has a unique name, as always, and that you select the "Deployment Target" checkbox. Complete the process and the new channel is displayed, subordinate to the older one.

If you now make a change to the test channel, you only need to click the Deployment icon to apply it directly to the deployment target.

Deployment and Channel Hierarchies

The Deployment function can only be used at the lowest level of a channel hierarchy, i.e. a channel cannot have both child channels and a deployment target. Similarly, a deployment target cannot itself have child channels.

However, it is possible for a deployment target channel itself to have a subordinate channel as a deployment target. This allows you to map a multi-level approval process, for example.