AddressFinder

The best way to find exact addresses in Australia

  • Skip to Main Navigation
  • Skip to Footer Sitemap
  • Skip to Top

Menu

Get Started Free

  • Pricing
  • Features & plugins
  • About us
  • Case studies
  • FAQ
  • Contact
  • Blog
  • JavaScript widget docs
  • API developer docs
  • Log in
  • Pricing
  • Features
  • More
    • Company & product
      • About Us
      • Case Studies
      • FAQ
      • Partners
      • Blog
      Contact Us
    • Integrations
      • Magento
      • WooCommerce
      • BigCommerce
      • Salesforce
      • Shopify Plus
      See all integrations
    • JavaScript widget docs
      • Integration Guide
      • Widget Code Generator
      • Widget Reference
      • Code Examples
      See all JavaScript docs
    • API developer docs
      • Address Autocomplete
      • Address Metadata
      • Address Verification
      See all API docs
  • Log in
  • Get Started Free

JavaScript Widget: best practices

Many registration forms need to capture an address from the customer. Often the address captured is the customer’s home address or a delivery address.

The typical registration form will ask the customer for their address in a format such as:

  • Address Line 1
  • Address Line 2
  • Suburb
  • State
  • Postcode

Adding AddressFinder

There are two main approaches to applying AddressFinder to your registration forms. You can either include the JavaScript widget in an existing unmodified form, or you can choose to adjust your form to take advantage of AddressFinder’s capabilities. We suggest the second option. Examples of form integration can be found on the demos page.

Adding the JavaScript Widget to an existing form

You can add the JavaScript Widget to the Address Line 1 field (in the example above), and configure it to automatically populate the existing address form fields when the user selects an address.

Optimising a form to use the JavaScript Widget

When you add AddressFinder to your registration form, we suggest that you reduce the number of fields captured to just a single address line. When the user selects an address, all of the address components will remain within that one address field.

Depending on your requirements, you will probably want some or all of the individual address elements. You should store these in hidden form fields.

Capturing address data

As described above, we suggest that you display the selected address on a single line, but store the individual address elements separately in hidden fields.

Hiding these fields from the user will reduce the size of your form, which may lead to a higher conversion rate. In addition, hiding these fields will reduce the opportunity for the user to tamper or adjust them.

Have a look at the response documentation on the address elements returned. We suggest you store everything, so as to future proof yourselves against any future requirements.

Capturing address meta data

As well as the address elements, we also make available additional meta data about the address. We provide the following meta data for most addresses:

  • Street name, Suburb, etc
  • GPS coordinates (latitude and longitude)
  • The canonical address

At a minimum, we suggest that you capture the GPS coordinates.

Handling missing addresses

Our data comes from PSMA Australia Limited, an authoritative source.

In cases where an address will appear to be missing from AddressFinder, it makes sense to allow your users to provide their address in a manual manner. We suggest adding a link such as “Enter your address manually” which displays a set of hidden address fields when clicked.

Handling failure

AddressFinder is a very stable platform with an impressive uptime. Our infrastructure has multi-site redundancy and handles failure well.

But, no service can ever be 100% reliable, and occasionally there may be a problem.

We suggest that you allow users an option to manually enter an address for when AddressFinder is unavailable. You could use the approach suggested above.

More information

Our AddressFinder knowledge base has further information about how to use AddressFinder on your website. We are happy to help, so please click the Help button on the bottom right corner of this page to contact support at your leisure.

  • JavaScript Widget
    • Integration guide
    • Widget code generator
    • Code examples
    • Best practices
    • Fixing browser quirks
    • Advanced usage
    • JavaScript widget reference
  • API Specs (AU)
    • Address Autocomplete
    • Address Metadata
    • Address Verification
    • Location Autocomplete
    • Location Metadata
    • API Errors
  • API Specs (NZ)
  • Integrations
    • Magento
    • WooCommerce
    • BigCommerce
    • Salesforce
    • Shopify Plus
    • Spiffy Stores
    • Ruby
    • iOS
    • Drupal
    • Microsoft Dynamics 365
    • Vue
    • Gravity Forms

Sitemap

Home

  • About
  • Contact
  • Blog
  • FAQ
  • Pricing
  • Case Studies
  • Status Page
  • Privacy Policy
  • Terms & Conditions

Features

  • Australian Address Autocomplete
  • Australian Address Verification
  • Australian Address Metadata
  • Geocode Australian Addresses
  • Street, Suburb & City Search
  • Customer Portal

Integrations

  • WooCommerce
  • BigCommerce
  • Shopify Plus
  • Magento
  • Salesforce
  • Spiffy Stores
  • iOS
  • Ruby
  • Drupal
  • Microsoft Dynamics 365
  • Vue
  • Gravity Forms

API Documentation

  • Address Autocomplete
  • Address Metadata
  • Address Verification
  • API Errors
  • Another 2 APIs
  • NZ API specs

Widget Documentation

  • Integration Guide
  • Code Generator
  • Code Examples
  • Javascript Reference

Get Started Free

AddressFinder is also available in New Zealand