Default Values

You can prefill form fields with default values so that when users open the form, some information is already filled in. This improves user experience and reduces input effort.

There are two types of default values you can use:

• Static Prefills – set manually in the Form Builder.
• Dynamic Prefills – passed through query parameters in the URL.

Priority Rule

Dynamic prefills override static default values when both are present for the same field.

---

Static Default Values

Static values are configured in the Form Builder and always apply, regardless of how the form is accessed.

How to Set Static Values

• In the Form Builder, click the Set Default Values button at the top.
• Select a screen to view its fields.
• Check the fields you want to prefill and enter default values.

These defaults will be automatically filled in when the form loads - unless overridden by dynamic values.

✅ Static prefills work with all form links: short URLs, full URLs, embedded forms, and integrations.

---

Dynamic Prefills (via Query Parameters)

Dynamic values are passed into the form using query parameters that match the form field’s Unique Name.

Example

If you have a field with Unique Name firstName, opening:

https://hptz.io/abc123?firstName=Alex

will prefill the field with the value Alex.

When It Works

Dynamic prefills are supported only when the form is accessed using one of the following methods:

• The form is opened using its short URL (e.g., https://hptz.io/...)
• The form is embedded on a web page using:
  • The embed script from Form Settings → Integrations → Embed Script
  • One of our official platform integrations (Wix, Webflow, etc.)

In embedded forms, dynamic values are pulled from the parent page’s URL.

---

Security, PHI, and PII considerations

Important

URLs are not a secure channel for transmitting PHI or sensitive PII.

Dynamic prefills are intended for non-sensitive context only. They should not be used to pass PHI.

Guidelines

• Do not use dynamic prefills for PHI
• Do not include diagnoses, medical details, SSNs, or patient identifiers in URLs
• Limit query parameters to non-sensitive identifiers

Appropriate uses for dynamic prefills

Dynamic prefills are best suited for values such as:

• Clinic or location IDs
• Workflow routing flags
• Internal reference identifiers (non-PHI)
• Campaign or attribution values (UTMs)

---

Example: Capturing UTM Tags

Suppose your landing page is:

https://example.com/page?utm_source=google

To capture utm_source:

1. Add a field with Unique Name utm_source to your form.
2. Place the field on a visible or hidden row.
3. Embed the form using the provided script or use the short URL.
4. The field will automatically receive the value google.

---

Summary

Type	Description	Works With	Priority
Static Prefill	Set manually in Form Builder via “Set Default Values”	All forms (short URL, full URL, embedded, integrations)	Lower priority
Dynamic Prefill	Passed via query parameters (e.g., ?firstName=Alex)	Only short URL and embedded forms	Higher priority (overrides)

Use default values to streamline input, prefill known data, and enhance your form workflows.