Do you need to activate or suppress specific integrations based on form input data? We have an Extension for that!
The Conditional Integrations Extension allows you to activate specific integration IDs based on the "truthiness" of any form field, on any page, even for submissions where the conditional value is on a prior page.
Go to Extensions from the profile menu top right, and install "Conditional Integrations".
Then, you can activate specific integrations for form submissions on a given Campaign page using metadata.
Let's say you have this for page 1 of your Campaign, with checkboxes as form Custom fields 1 and 2.
Then on page 2 you have a separate (progressive) form:
And you have two Integrations that you want to call based on which checkboxes are checked (none, one, or both):
With the Conditional Integrations app installed, you can configure metadata on the 2nd page (i.e. at the page-level, under Layout) as follows:
The format is "ci:fieldName = integrationId", where fieldName is the specific field name, and integrationId is the ID of the integration. Below is a list of supported Metadata Key inputs:
| Metadata Key | Level | Value | Description |
| ci:email | Page | Integration ID | Activates the integration if the email field is truthy (non-blank) on submission. |
| ci:phone | Page | Integration ID | Activates the integration if the phone field is truthy (non-blank) on submission. |
| ci:opt_in | Page | Integration ID | Activates the integration if the opt_in checkbox is truthy (checked) on submission. |
| ci:custom_N | Page | Integration ID | Activates the integration if custom_N (non-blank) is truthy on submission. |
| ci:any | Page | Integration ID | A special conditional command that is always true. |
You can use metadata to control the integrations based on form data submissions for the same page, or a subsequent page. Typically, you should avoid attaching a (static) integration to the campaign itself. When the ci:custom_N page is submitted, any statically attached integrations will be replaced by any metadata dynamic integrations. If there are no dynamic integrations activated, static integrations will run as expected.
Note that you can use this app for Custom Fields that are not checkboxes. Integrations are activated if the value is "truthy". Custom fields are "truthy" if they are not blank, and not equal to "false".
WARNING: this app is not compatible with the "native" UI features for checkbox integrations or form level integration overrides.
Under Page > Form > Fields > (Field), when a checkbox:
Under Form > Form:
If you need to use these features, the Conditional Integration Extension also supports the same functionality. For example, with a checkbox of custom_1, you can say in page metadata ci:custom_1=12345 to get the same effect (where 12345 is integration ID).
For form level overrides, you can say in page metadata ci:any=12345. The metadata key ci:any is a special conditional command that is always true.
Want to get more from Digioh?
Get the playbooks leading brands use to convert more visitors into revenue.
Browse the Playbooks ?Platform Tour
See what else you can do with Digioh in our self-guided platform tour.
Take the Tour ?