URL Parameters

URL Parameters are used to pass data directly from a URL into an Action Page. They can also be used to pass data through a Callback URL to a thank you page.

URL Parameters Example

To use URL Parameters, determine what data you'd like to pass to the form, then simply pass it using a link to the browser such as:


Notice that before the first parameter is entered, you will need to add the "?" symbol; between each consecutive parameter, the "&" symbol will need to be entered.

Action Pages Parameters

  • amount ( 100 - single number to choose default amount)

  • amounts ( 10,25,50,100,250 - number separated list )   

  • city

  • country

  • email

  • embed

  • employer_name

  • first_name

  • last_name

  • line_1

  • line_2

  • nb_election_cycle

  • nb_election_period

  • nb_election_period_ngp_code

  • nb_is_private

  • nb_note

  • nb_recruiter_id

  • nb_recruiter_name_or_email

  • nb_tracking_code_slug

  • occupation

  • phone

  • postal_code

  • region

  • source_code

  • state (accepts state abbreviation; e.g. LA not Louisiana)

  • street

  • street_2

  • ucampaign_token

  • utm_campaign

  • utm_content

  • utm_medium

  • utm_source

  • utm_term

  • zip

The following aliases are also available for URL params:

  • street => line_1

  • street_2 => line_2

  • zip => postal_code

  • state => region

Custom field URL params are specified by their Internal Name set in Action Pages on the field. Hidden Fields internal name is their key. Note that you can use a URL parameter to specify and fetch custom field data.

For example, a hidden field named hidden_custom_field will be anedot.com/donate?hidden_custom_field=special

Callback URL Parameters

Action Page Callback URLs can utilize tokens to retrieve data. Simply reference the token in the call back url enclosed in double curly braces; {{ }}  (ex: {{address_city}} ).

The following tokens are supported in Action Page call back URLs:

  • address_city

  • address_country

  • address_line_1

  • address_line_2

  • address_postal_code

  • address_region email

  • employer_name

  • donation_ids (will contain an ID for single fund pages or a comma separated list of IDs for multifund)

  • donation_statuses (will contain a status for single fund pages or a comma separated list of statuses for multifund)

  • List order matches ID order for donation_ids)

  • fees

  • first_name

  • last_name

  • occupation

  • payment_method

  • payment_method_last_digits

  • phone

  • recurring

  • recurring_frequency

  • total_amount (value is returned in cents) 

Custom field values are also available by using their key as a token.
The following callback URL example references an ActionPage with a custom field having a key of custom1.