Supporter participation in your campaigns is likely to be higher if their details are pre-populated in the form fields.
As long as the supporter has the relevant data fields populated in their supporter record, there are several ways to achieve the pre-population of your page forms when using Engaging Networks:
Marketing Tools
When emailing your supporter using broadcasts or automations, it’s possible to pre-populate form fields using:
‘links & inserts > insert page link .' This will pre-populate any form fields on a page for which your supporter has data.
Chaining Pages
Page chaining links two Engaging Networks pages together. It can be accomplished by using either the ‘Insert Campaign Link’ or by adding the parameter?chain to the end of an Engaging Networks page URL.
External Links to Engaging Networks
It’s possible to populate the fields using tools other than Engaging Networks. To achieve this, you will need to construct a URL using the relevant Engaging Networks page parameter.
Broadcast emails
When sending emails using Engaging Networks, pre-population will
Only work the first time a campaign link is clicked from the email (for security reasons), and not with subsequent attempts
Not work when testing via Email Classic.
Custom URL parameters
You can add custom URL parameters to your campaign links using Marketing Tools - Broadcasts and page builder, and when linking to Engaging Networks from third-party tools and sites. These parameters can be used to pre-populate additional data, such as the donation amount.
We do not recommend including personally identifiable information or sensitive data in a URL, as this could expose data through a browser or analytics software such as Google Analytics.
Constructing a URL to pre-populate fields
To pre-populate your Engaging Networks page without using campaign links, you need to construct a URL which contains the names and values of the fields you want to pre-populate.
Example of adding an appeal code parameter to your URL:
Find the base URL
https://secure.charity.org/page/20145/donate/1
Create the name and value pairs in the query string
supporter.appealCode=NY%20S-001 In this example, the appeal code will be NY S-001
i. Add the name and value into the query string starting with?: https://secure.charity.org/page/20145/donate/1?supporter.appealCode=NY%20S-001
Example of adding a transaction amount to the Appeal Code URL:
Add name and value pairs in the query string
transaction.donationAmt=20
i. Add the name and value into the query string starting with&: https://secure.charity.org/page/20145/donate/1?supporter.appealCode=NY%20S-001&transaction.donationsAmt=2
URL Parameters for tagged fields
URL parameters for tagged fields —those fields associated with your account data structure —never change.
What are the other tagged fields and URL Parameters
Tagged Field
URL Parameter
Title
supporter.title
First Name
supporter.firstName
Middle Name
supporter.middleName
Last Name
supporter.lastName
Address 1
supporter.address1
Address 2
supporter.address2
Address 3
supporter.address3
City
supporter.city
Region
supporter.region
Email Address
supporter.emailAddress
Postcode
supporter.postcode
Country
supporter.country
Phone Number
supporter.phoneNumber
Fee cover
transaction.feeCover
Donation Amount
transaction.donationAmt
Payment Type
transaction.paymenttype
Credit Card Number
Sensitive data shouldn't be passed over a URL
Credit Card Expiration Date
transaction.ccexpire
Credit Card Verification Value
Sensitive data shouldn't be passed over a URL
Card Holder Name
supporter.creditCardHolderName
Bank Account Number
supporter.bankAccountNumber
Bank Routing Transit Number
supporter.bankRoutingNumber
Bank Account Type
supporter.bankAccountType
Payment Currency
transaction.paycurrency
Recurring Payment
transaction.recurrpay
Recurring Day
transaction.recurrday
Recurring Start Date
transaction.recurrstart
Recurring End Date
transaction.recurrend
Recurring Count
transaction.recurrcnt
Recurring Frequency
transaction.recurrfreq
Recurring Period
transaction.recurprd
Tax Deductible
transaction.taxdeductible
Recognize Gift
transaction.recnzegft
Additional Comments
transaction.comments
Anonymous Donor
supporter.anonymousDonor
In Memoriam
transaction.inmem
Inform Email
transaction.infemail
Inform Name
transaction.infname
Inform Address 1
transaction.infadd1
Inform Address 2
transaction.infadd2
Inform City
transaction.infcity
Inform Region
transaction.infreg
Inform Postcode
transaction.infpostcd
Inform Country
transaction.infcount
Honoree Name
transaction.honname
Gift Reason
transaction.gftrsn
Tribute Options
transaction.trbopts
Direct Gift
transaction.dirgift
Appeal Code
supporter.appealCode
Supporter Birthday
supporter.dateOfBirth
Shipping Title
transaction.shiptitle
Shipping First Name
transaction.shipfname
Shipping Last Name
transaction.shiplname
Shipping Email Address
transaction.shipemail
Shipping Address 1
transaction.shipadd1
Shipping Address 2
transaction.shipadd2
Shipping City
transaction.shipcity
Shipping Region
transaction.shipregion
Shipping Postcode
transaction.shippostcode
Shipping Country
transaction.shipcountry
Shipping Notes
transaction.shipnotes
Shipping Enabled
transaction.shipenabled
How to find other URL parameters
To find out the name of a field, it is best to look at the HTML of the page in your browser:
Right-click on the field or question and select Inspect
Find the corresponding input tag and name attribute in the HTML
i. In this example, the name attribute for inclusion in the URL is: supporter.questions.42761
ii. As this is an opt-in question*, it would be added into the query string with either a Y or N value. This could be the query string starting with&: https://secure.charity.org/page/20145/donate/1?supporter.appealCode=NY%20S-001&transaction.donationsAmt=20&supporter.questions.42761=N
It’s not recommended to use an opt-in question as URL parameters
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.
