Skip to main content

Using Country and Language Rules in Formulayt

Understanding when to use country versus language rules for compliance and localized content in Formulayt forms.

Updated over 9 months ago

Creating a consistent user experience is essential to any successful marketing campaign. Formulayt allows your forms to perform various functions through rules and other features. Many of these rules depend on the user's country or language preferences.

Understanding country vs. language rules

When to use country-based rules

Use country-based rules for compliance requirements tied to a user's physical location. For example:

  • GDPR checkboxes should display based on the user's current country location, not the domain or language they view the page in.

When a user is on a Chinese domain with French language settings but physically located in the United Kingdom, GDPR rules should still apply because these regulations depend on the user's physical location.

When to use language-based rules

Use language-based rules for content that should match the user's selected language preference. For example:

  • Privacy policy links should direct to the version matching the gate language (form language).

  • If we set privacy policy links to follow country rules, a user viewing a Chinese language form might be directed to an English privacy page.

Key definitions

Gate language:

  • Set in the gate editor when building your form

  • Determines which set of translations to use

  • Remains fixed based on the gate and the page it's on

  • Does not change based on user location

Country field:

  • Customer-facing field used primarily for data collection

  • Often uses geolocation to detect the user's location

  • Changes depending on where the user is physically located

Summary

The gate language is a fixed property of your form and determines its display language. The user's country is variable and depends on their physical location. Understanding this distinction helps you create properly localized forms that maintain both compliance and a good user experience.

Did this answer your question?