GDPR Feature: Conditional CTA form fields & Label Only field type


Learn how to use Conditional CTA Form Fields and the Label Only Field Type to make your Form CTAs compliant with the GDPR.


Before you Begin

  • To use these features, you need to be a member of the Account Administrator or Content Manager user groups.
  • Before you can get started, you'll need to determine which opt-in checkboxes and privacy policy details will need to be added to your Form CTAs.
  • You'll also have to set up any corresponding opt-in and privacy policy fields in the Marketing Automation Platform(s) tied to your Form CTAs.


What are conditional CTA form fields?

Conditional CTA Form Fields (or just conditional fields for short) is a feature available on Form CTAs. The concept is pretty simple: not every user requires the same experience when interacting with a Form CTA. Conditional fields allows you to choose which fields on a Form CTA are shown to a given user, based on whether certain conditions have been met.


What is the Label Only form field?

You can specify several different types of fields on a Form CTA, including text, dropdown, etc. The Label Only field type allows you to add a field that consists only of the text label, with no associated input field.


How do these features relate to GDPR requirements?

The GDPR has specific requirements for the collection and management of data belonging to EU citizens, so you have to design your CTAs accordingly to incorporate opt-ins, a privacy statement, etc.

Designing to meet these requirements typically makes a Form CTA more complex. If you adopt a one-size-fits-all approach, this would mean presenting the most complex version of the CTA to all visitors to your Hub — including to non-EU visitors, to whom the GDPR requirements don't apply. Doing this could potentially hurt your conversion rates.

With conditional fields, you can tailor the Form CTA experience to your visitors: EU visitors will see a GDPR-compliant version of the CTA, while non-EU versions will see a simplified version.

And, using the Label Only field type, you can display a note about your privacy policy along with a link to it right within the CTA. Combined with conditional fields, you can also make this note appear only for EU visitors.


How does this work in practice?

To illustrate how this works, consider an example Form CTA with the following fields:

  • First Name
  • Last Name
  • Company
  • Email

If the Hub visitor interacting with this Form CTA is an EU citizen, we would need to also display a privacy policy on the CTA, as well as one or more opt-in checkboxes. With Conditional Fields, we can simply add a checkbox to the Form CTA, like this:

  • First Name
  • Last Name
  • Company
  • Email
  • [  ] I'm an EU Citizen

By tying this checkbox to Conditional Fields, we can display the necessary opt-ins and privacy policy links for GDPR compliance when an EU citizen checks the box. The result might look like this:


Below, we'll show you how you can do this with your own Form CTAs.


Create a condition for conditional fields

To create conditional fields on Form CTAs, you first have to create a condition: when this condition is met, the conditional fields will be displayed.

  1. Log in to your Uberflip account and use the Hubs menu to select the Hub you want to work in.
  2. In the sidebar menu on the left, click on Calls-To-Action, then click on Form Calls-To-Action.
  3. In the list on the right, find the Form CTA you want to modify and click on it to open it in the CTA Editor (or create a new Form CTA).
  4. Click on the Layout button, and find the section labeled Form Fields, then click on Manage next to the Form Fields heading:
  5. In the pop-up window that appears, click on +Add New.

  6. You can now add a new field that will form the condition to be met. This can be anything you like, but in this example, we will look at using a checkbox for users to self-select if they are EU citizens.
    • One other possible option is to use a country selection drop-down where the condition is tied to EU countries only, but this is more time-consuming to set up.
  7. In the Add New Field menu, use the dropdown next to Field Type to select Checkbox. Next to Field label, type "I'm an EU Citizen" (or something else of your choice). Finally, click on Save.

  8. You'll be returned to the Manage Fields view.


Add privacy policy and/or opt-in conditional fields

You can now add conditional fields that will display based on the condition you set up being met: in this case, if the visitor checks the box that they're an EU citizen, they will be shown your privacy policy and an opt-in email field.

  1. On the Manage Fields view, click on +Add New again.


  2. In the Add New Field menu, use the dropdown next to Field Type to select Label Only.
  3. The displayed fields will change, and you will now see a large text field. You can either directly type your Privacy Policy into this field, or use a link to another page. Dont forget to, type in a label next to Field label.

  4. Lastly, use the dropdown next to Displays to change the selection to Conditionally.

  5. This will cause an additional Field Conditions section to appear at the bottom of the window. Use the dropdown menus to set up the condition to be met. From left to right, these select:
    • The form field to use as a condition (which you set up previously)
    • The conditional statement (Equal To or Not Equal To)
    • The condition (e.g. Checked or Not Checked)

  6. If you want, you can also set up multiple conditions to be met. To do that, just click on the + button to the right.

  7. When you're finished, click on Save to add the new conditional field.
  8. You can also set up the GDPR-mandated opt-in fields the same way: click on +Add New again, then select Checkbox under Field Type and type something like "Opt in to future emails" into the Field label field. Under Displays, choose Conditionally again and set up the same condition as before:

  9. Finally, click on Save to add this field as well. Repeat this as many times as you need for each opt-in that needs to be on the CTA.
1 out of 1 found this helpful