4. January 2022
Switching between integrations within the same project
If you need to route some campaigns to the CRM, others to an email tool, and store the results from surveys in an independent database, this solution is also easy to set up.
We'll show you how easy it is to route data from campaigns to different integrations.
Create the necessary connectors
first, set up all the necessary integrations
name each integration with a unique name, you will refer to this name later (it can be a number, hash or any alphanumeric string)
name each integration with a unique name, you will refer to this name later (it can be a number, hash or any alphanumeric string)
Switching between connectors
The example above contains four integrations where the default tool is MailChimp.
However, if we want to store the questionnaire data in a separate database and not send it to MailChimp, we simply use the integration name in the following hidden input, which we insert into the campaign source code (design) between the tags
This way, all data will be transferred to the internal datastore instead of MailChimp, where you can download it as a CSV file (but you can also transfer it to CRM, etc.).
If no integration is found, the default one marked in the status column is always used.mailocator.om
However, if we want to store the questionnaire data in a separate database and not send it to MailChimp, we simply use the integration name in the following hidden input, which we insert into the campaign source code (design) between the tags
<form>:<input type="hidden" name="mlc_integration" value="Form Data Collection">This way, all data will be transferred to the internal datastore instead of MailChimp, where you can download it as a CSV file (but you can also transfer it to CRM, etc.).
If no integration is found, the default one marked in the status column is always used.mailocator.om