Editing custom content
Custom content fields allow you to display HTML content within your forms. To edit custom content:
Navigate to Setup > Fields
Select the custom content field you want to edit
Update the Content field with your desired text or HTML
Note: The custom content name will not be displayed to users but is only used internally to show gate editors where the content will appear on forms, and also to identify the content for translation.
For complete details on field configuration options, see our Managing Fields guide.
Dynamically changing custom content
Using rules to change custom content
Rules allow you to change custom content based on specific conditions such as user country, campaign ID, or other field values.
Example: Change offer messaging based on Campaign ID
First, create a custom content field with your default message:
html
<p>Download our free whitepaper.</p>
Then create a rule:
Trigger:
Set to run on form load (since campaignID is pre-populated and won't change)
Conditions (IF):
Field: campaignID
condition: contains
Value: Spring2025
Actions (THEN):
Action: Change field value
Field: offer_content
New Value:
<p>Limited time: Download our exclusive 2025 trends guide.</p>Translation Label: Spring2025Offer (identifier for finding this text in the translations area)
Otherwise:
Reset the value of this field (to use the default)
Using translations to change custom content
If your custom content needs to appear in multiple languages, use the translations area:
Navigate to Setup > Translations
Locate the relevant phrase for your custom content field
Select the language you want to edit
Enter the translated content
For example:
English: "Download our free whitepaper."
Spanish: "Descarga nuestro libro blanco gratuito."
French: "Téléchargez notre livre blanc gratuit."
For complete details on translation management, see our Managing Translations guide.
Adding links to custom content
Method 1: Using Field Settings to add a link
Navigate to Setup > Fields and select the custom content field
Add the link in HTML to the content area:
html
<p>For more information, see our <a href="https://www.companyname.com/privacy-policy/" target="_blank">Privacy Policy</a>.</p>
Method 2: Using rules to add links based on conditions
Rules allow you to change privacy policy links based on specific conditions such as user country or campaign.
Example: Change privacy link based on user country
First, create a custom content field called Privacy_Statement with your default privacy statement:
html
<p>By submitting this form you agree to our <a href="https://www.formulayt.com/privacy">Privacy Policy</a>.</p>
Then create a rule:
Trigger:
Set to run continuously (since country can change in real-time)
Conditions (IF):
Field: country
condition: equals
Value: ES
Actions (THEN):
Action: Change field value
Field: Privacy_Statement
New Value:
<p>By submitting this form you agree to our <a href="https://www.formulayt.com/es/privacy">Privacy Policy</a>.</p>Translation Label: PrivacyStatementES (identifier for finding this text in the translations area)
Otherwise:
Reset the value of this field (to use the default)
Method 3: Using translations to add links in multiple languages
Navigate to Setup > Translations
Locate the relevant phrase for your custom content field
Select the language you want to edit
Add your HTML link to the translation text
For example, the French version might be:
html
<p>Pour plus d'informations, consultez notre <a href="https://www.companyname.com/fr/privacy-policy/" target="_blank">Politique de Confidentialité</a>.</p>
This ensures each language links to the appropriate privacy policy page.
Using tokens at scale
Tokens allow you to inject dynamic data into your custom content, making it easy to manage variations at scale without creating multiple fields or complex rules.
How it works:
Create a hidden field to store your dynamic value (e.g., different privacy policy URLs)
Use rules to populate that hidden field based on conditions (language, country, campaign, etc.)
Go to your custom content field and click the {*} icon to insert a token
Select your hidden field as the token source
Set a default value if needed
Example: Dynamically change a privacy policy URL based on language
Create a hidden field called Privacy_Policy_URL and use rules to update it based on language. For example:
Then in your custom content field, use the token:
html
<p>By submitting this form you agree to our <a href="{{Privacy_Policy_URL}}">Privacy Policy</a>.</p>This approach allows you to manage complex variations centrally through hidden fields and rules, rather than maintaining multiple versions of the same content.
For complete details on how to implement tokens, including step-by-step examples, see our Using Tokens to Inject Dynamic Data guide.
Best practices
Always provide a default custom content value as a fallback
Test your rules and translations thoroughly to ensure the correct content appears 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 URLs are valid and lead to the correct pages
