Why customize privacy links?
Online privacy is a growing priority for web users. Providing the right privacy policy link based on user context (language, location, or campaign) helps users find relevant information and demonstrates your commitment to transparency.
This guide shows you how to implement dynamic privacy policy links in Formulayt.
Setting up the base privacy statement
First, create the foundation for your privacy statements:
Create a custom content field called
Privacy_StatementAdd your default privacy statement text with HTML link:
"By submitting this form you agree to our <a href="https://www.formulayt.com/privacy">Privacy Policy</a>."
Method 1: Using translations for language-based links
If your privacy policy varies by language, use the translations area:
Enter your default privacy statement in your primary language
Add translations with appropriate links for each supported language
For example, the Spanish version might be:
"By submitting this form you agree to our <a href="https://www.formulayt.com/es/privacy">Privacy Policy</a>."
Method 2: Using rules for context-based links
If your privacy policy varies based on other factors like country, brand, or campaign ID, use rules to manage which links are shown.
โ
Example 1: Change privacy link based on user country
Trigger:
Set to run continuously (since country can change in real-time)
Conditions (IF):
Field: country
condition: equals
Value: ES
Actions (THEN):
Change the value of Privacy_Statement field to:
"By submitting this form you agree to our <a href="https://www.formulayt.com/es/privacy">Privacy Policy</a>."
Otherwise:
Reset the value of this field (to use the default)
Example 2: Change privacy link based on Campaign ID
Trigger:
Set to run on form load (since campaignID is pre-populated and won't change)
Conditions (IF):
Field: campaignID
condition: contains
Value: OutReach_47162
Actions (THEN):
Change the value of Privacy_Statement field to:
"By submitting this form you agree to our <a href="https://www.formulayt.com/privacy_outreach">Privacy Policy</a>."
Best practices
Always provide a default privacy policy link as a fallback
Test your rules thoroughly to ensure the correct links appear in all scenarios
Use descriptive link text (e.g., "Privacy Policy" rather than "click here")
Consider adding region-specific legal disclaimers alongside privacy links when necessary
Ensure all privacy policy URLs are valid and lead to the correct pages
