Overview
With the April 2026 Studio release, forms can now accept URL parameters from the page URL and automatically prefill both standard fields and custom fields, enabling more personalised user journeys.
This allows you to:
- Pre-fill donation amounts
- Auto-populate contact details
- Pass campaign or tracking data
- Improve conversion rates
Step-by-Step Guides: Prefill a Studio Form
When a user lands on a Studio page with URL parameters, those parameters are passed into the form and mapped to corresponding fields.
Step 1 — Open one page
- Open your Studio page: "Page" → "…" → "View"
- You can see the page URL at theh top as below
Step 2 — Append URL parameters
AddAdd proper url parameters using standard query string format:
Step 3 — Load the page and verify
- Enter to load the page & check, the form will automatically populate matching fields
- If the value is not part of predefined options, it may appear as “Other amount"
Example:
Important rules:
- Parameter names are case-sensitive (e.g.
donationAmount≠DonationAmount) - URL values will override default form values
- Multiple parameters can be passed using
& -
The first parameter in a URL starts with
?, and additional parameters are connected using&.
Field Mapping Reference
Below is a structured list of commonly used parameters, ordered to match a typical form flow (donation → personal details → payment ).
| Field | Parameter (URL Key) | Example |
|---|---|---|
| Donation | ||
| Donation Amount | donationAmount | donationAmount=100 |
| Pay Frequency | PayFrequency | PayFrequency=Monthly |
| Currency Selection | x_Currency | x_Currency=AUD |
| Campaign & Tracking | ||
| Campaign Selection | camId | camId=CAM123 |
| Opportunity ID | oppId | oppId=006XXX |
| Contact Information | ||
| Contact ID | cId | cId=003XXX |
| Account ID | aId | aId=001XXX |
| Salutation | Salutation | Salutation=Mr |
| Last Name | LastName | LastName=Smith |
| First Name | FirstName | FirstName=John |
| Phone Details | ||
| Mobile Phone | Mobilephone | Mobilephone=0412345678 |
| Phone | Phone | Phone=0412345678 |
| Address | ||
| Mailing Street | MailingStreet | MailingStreet=10 Main St |
| Mailing City | MailingCity | MailingCity=Melbourne |
| Mailing State | MailingState | MailingState=VIC |
| Mailing Postal Code | MailingPostalCode | MailingPostalCode=3000 |
| Mailing Country | MailingCountry | MailingCountry=Australia |
| Payment By | ||
| Payment By Name | PanymentByName | PanymentByName=John Doe |
| Payment By Type | PanymentBy | PaymentBy=Individual |
| System Fields | ||
| Merchant Facility | payMSetting | payMSetting=ABC |
| Payment Form Type | payMType | payMType=XYZ |
| Membership ID | MembershipId | MembershipId=MEM001 |
NOTE
- ⚠️ Parameter keys must be spelled correctly to ensure successful mapping.
- ⚠️ In most cases, parameter matching is not case-sensitive, but it is recommended to follow the exact casing shown in the table for consistency.
Parameters list
Before mapping parameters to fields, you can refer to the full official list:
This page provides a complete list of all supported parameters across:
- Dynamic URL Parameters
- URL Tokens
- Encrypted URL Parameters
Contact Auto-Population (cId)
When cId (Contact ID) is included in the URL, Studio can automatically retrieve and populate existing contact details.
Example:
https://orgname.payments2us.com?cId=003ABC123
Auto-filled fields may include:
- First Name=Anna
- Last Name=Jones
- Email=Anna.Jones@email.com
- Phone=0412345678
- Address=100 xxx Street, VIC,Melbourne 3000
Important Notes
- Data is pulled from the corresponding Salesforce Contact record
- If a field is also provided via URL, the URL value takes priority
- Requires correct Salesforce permissions and configuration Contact Auto-Population
Common Issues
| Issue | Cause | Fix |
|---|---|---|
| Field not prefilled | Wrong parameter | Check naming |
| Custom field not working | API mismatch | Verify Salesforce field |
| Value ignored | Invalid format | Re-test URL |
Summary
URL parameter passing enables dynamic, personalised form experiences by mapping URL values to both standard and custom fields.
