Donation pages can now accept dynamic suggested donation amounts through URL parameters, commonly used in personalised URLs (PURLs) for direct mail and email campaigns. Instead of every recipient seeing the same default suggested amounts, each link can pass its own set of values, tailored per recipient or per segment.
This works across all Studio form templates: Classic, Digital, and Card Update.
The parameters
Three parameter formats are supported, and can be used interchangeably:
sdaURLParam_SuggestedDonationAmtSuggestedDonationAmt
All three formats work the same way and can even be mixed within the same URL. Adding the number directly after the parameters (1 through 6, e.g. sda1) determines which suggested amount position on the form the value overrides.
How to use it
Append the parameter(s) to your donation page URL, with each one pointing to the suggested amount position you want to set:
This sets all six suggested amounts on the form to the values passed, under the default payment frequency.
Pre-selecting a payment frequency
Add PayFrequency to also pre-select which frequency the amounts apply to:
This pre-selects Monthly as the frequency, and sets the six suggested amounts under the Monthly view specifically.
Partial overrides
You don't need to pass all six values. Any position left out keeps whatever was configured in Manage Forms - Edit Form:
https://carelink.payments2us.com?PayFrequency=Monthly&sda1=10&sda2=20&sda3=30
Here, only the first three suggested amounts are overridden (10/20/30). Positions 4, 5, and 6 stay exactly as set in Manage Forms.
Notes
All three parameter formats are interchangeable and can be mixed freely in the same URL, e.g. sda1=10 and SuggestedDonationAmt2=20 can both appear together and will each apply correctly to their respective position.
If two parameters target the same position, the first one entered in the URL is the one applied — the later one is ignored for that position.
Values that aren't valid numbers are ignored. If a non-numeric value is passed (e.g. letters or special characters), that position is treated as if nothing was passed, and the suggested amount stays as configured in Manage Forms .
This works whether the PURL is encrypted or not. The existing encryption/decryption functionality is fully compatible. Forms will prefill correctly whether the parameters arrive encrypted or in plain text.
Â