Dynamic Redirects with @ Mentions

Redirect users to custom URLs after form submission and include their form responses in the redirect URL using @ mentions.

Overview

When a form is submitted, you can redirect users to a custom URL. With @ mentions, you can dynamically include form field values in the redirect URL, enabling personalized experiences and seamless data passing to your destination page.

Basic Usage

1. Navigate to your form's Settings → General
2. Enable Redirect on completion
3. Enter your redirect URL in the Redirect URL field
4. Use @ to include form data in your URL

Using @ Mentions

Type @ in the redirect URL field to see available fields from your form. You can include:

• Input fields: User responses (text, email, number, etc.)
• Calculated fields: Computed values from your form logic

Syntax

Simply type @ followed by the field name or ID. The field value will be automatically substituted when the form is submitted.

Example:

https://example.com/thank-you?email=@email&name=@full_name

When submitted, this becomes:

https://example.com/thank-you?email=user@example.com&name=John%20Doe

Examples

Passing User Information

Redirect to a personalized thank you page with user details:

https://example.com/thank-you?email=@email&name=@full_name&plan=@selected_plan

Including Calculated Values

Pass calculated fields like scores or totals:

https://example.com/results?score=@total_score&percentage=@score_percentage

Multiple Query Parameters

Combine multiple fields in your redirect URL:

https://example.com/confirmation?order_id=@order_id&email=@email&amount=@total_amount&status=@order_status

Field Types Supported

You can use @ mentions with:

• Text fields: Short text, long text, email, phone, etc.
• Number fields: Numeric inputs, ratings, linear scales
• Choice fields: Multiple choice, checkboxes, dropdowns
• Date fields: Date picker values
• Calculated fields: Any calculated field from your form logic

URL Encoding

Field values are automatically URL-encoded when included in redirect URLs. Special characters, spaces, and reserved URL characters are properly encoded.

Example:

• Field value: John Doe

• In URL: John%20Doe

• Field value: user@example.com

• In URL: user%40example.com

Best Practices

1. Test your URLs: Always test redirect URLs with sample data to ensure they work correctly
2. Handle missing values: If a field is empty, it will be replaced with an empty string in the URL
3. Use meaningful field names: Clear field names make your redirect URLs more readable
4. Keep URLs reasonable length: Very long URLs may cause issues in some browsers
5. Validate on destination: Always validate and sanitize data received via URL parameters on your destination page

Conditional Redirects

For more advanced redirect logic (redirecting to different URLs based on user responses), you can:

1. Create a calculated field that determines the redirect URL based on form logic
2. Use that calculated field in your redirect URL: @calculated_redirect_url

This allows you to redirect users to different pages based on their answers, plan selection, or any other conditional logic.

Troubleshooting

@ mentions not working?

• Ensure the field name matches exactly (case-sensitive)
• Check that the field has a value when the form is submitted
• Verify the field is on a page that appears before or on the same page as the submit button

URL not redirecting correctly?

• Check that your URL is properly formatted (starts with http:// or https://)
• Verify special characters are being encoded correctly
• Test the URL manually to ensure it's accessible

Empty values in URL?

• Fields that are not answered will result in empty query parameters
• Consider using conditional logic to only include fields that have values