Overview

Within the 'Settings' tab of the app's form builder, you'll find an 'Advanced' section that allows you to control a form's whitelisted tags:

Pro-tip: Learn more about form settings using this help article.

What is the purpose of whitelisted tags?

Tags are required to be whitelisted to prevent tampering, as some Shopify apps and themes utilize customer tags to identify certain types of customers and provide unique functionality to those customers that would otherwise be limited. For example, it's quite common for apps and themes to use customer tags in Shopify to grant customers access to special pricing for products, or perhaps a special collection of hidden products that are not available for the general public.

For these reasons, we have purposely designed our Customer Fields app to prevent customers from tampering with tags. The form settings for whitelisted tags simply allow you to control this logic if/when necessary.

Do I need to use the whitelist for a form?

In most circumstances, No; you do not need to use the whitelist for a form.

If you're using the auto-tag feature for a dropdown, checkbox, or radio field type, then the app's backend will automatically whitelist the values for each of the field options. The app will also automatically whitelist any static tag values that you define when using form rules to tag a customer.

To be clear, there's really no need to worry about a form's whitelisted tags unless you are trying to tag a customer with a value from a Google Sheet (found in the 'dropdown with search' field type - see here for more details), or if you're trying to tag a customer with a value via the app's frontend JS API. Both of these are semi-advanced use cases, so normally you can leave a form's whitelisted tags setting as-is.

Configuration

To add a tag to a form's whitelist, simply type the value of the desired tag into the Whitelisted tags field. You are welcome to add multiple tags to the form's whitelist by adding a comma (,) between each tag. You can also add a space after the comma to make the list of tags easier to read. For example: vip, early-access, locked

Wildcard support

In addition to static tag values, form whitelists are also designed to support wildcards! Wildcards in a form's whitelist allow for dynamic tag values, which is especially helpful when using an external data source for field data (I.E. a Google Sheet).

Tag wildcards are defined by an asterisk (*). The asterisk can be appended or prepended to a static value, and it can also be used on its own. Some examples are shown below:

  • facility:* would match facility:123, facility:abc, and any other tag value that starts with facility:

    • Similarly, vip_id_* would match vip_id_123, vip_id_abc, and any other tag value that starts with vip_id_

  • *_member would match vip_member, non_member, and any other tag value that ends with _member

  • * would match any and all values, so make sure to use this with caution!


Have questions or need help?

Reach out to our support team via chat or email and we'll be happy to assist! 💪

Did this answer your question?