Skip to main content

Aperture Data Studio - Validate addresses step

Use the step

We strongly recommend that you tag data before using this step. This will allow the relevant tagged columns to be automatically selected.

Use this step to validate and enrich addresses in bulk using Experian Batch, depending on your licence.   

If your data has address columns tagged already, this step will automatically pick up all the columns tagged as addresses and list as Selected columns.

To enrich your data, choose one of the available Additional datasets. These will depend on your licence and the data available to you.

Using Additional options you can specify how the validated addresses will be returned:

  • Output columns - the layout of addresses
    • Standard (7-line layout)
    • Component (28-line layout)
  • Results columns - the validation results
    • Standard (basic match code)
    • Detailed (confidence of the match, etc.)

When using this step immediately before the Find duplicates one, the Generate find duplicates data option is selected by default. This speeds up the Find duplicates step by bypassing the address standardization process for addresses with a high quality match. 

Find out how to configure Experian Batch for the Validate addresses step.

Address validate cache

The maximum number of address searches that can be stored in Data Studio's in-memory cache. 

The default is 1 million. To change this, go to Configuration > Step settings > Validate addresses > Address  validate cache.

The higher the value, the larger the cache, meaning more memory will be used and more searches will be saved, improving the performance of the Validate Addresses step if that same search is submitted a second time.  

Validation result Description
Verified Correct Experian Batch verified the input address as a good-quality match to a complete address. No corrections or formatting changes were necessary.
Good Match Experian Batch verified the input address as a good-quality match to a complete address, although minor corrections or formatting changes may have been applied.
Good Premise Partial Experian Batch was not able to find a full match to a correct address, but found a good match to premise level by excluding organization or sub-premise details.
Tentative Match Experian Batch found a match to a complete address, but the overall differences between the input and cleaned addresses are significant enough to reduce the confidence in the match.
Multiple Matches Experian Batch found more than one correct address which matched the input address. This means that no single address could be matched with high confidence.
Poor Match Experian Batch found a match to an address, but with low confidence. This often means that the cleaned address is not deliverable.
Partial Match Experian Batch was unable to find a full correct address which matched the input address. This often occurs when the property number is missing from the input address.
Foreign Address Experian Batch could not find a matching address because the input address referred to a different country.
Unmatched Experian Batch was unable to match the input address to any correct address. 

Logging progress

To get a more detailed view of how many addresses have been validated, you can customize how often an entry in the log will be created.

Go to Configuration > Step settings > Validate addresses > and change the value of Address Validate Log Step Size to the required integer value. The default value (0) means that no specific progress logging will be given for the Validate addresses step. Changing the value to 10, 000 will mean that a log entry will be created after every ten thousand processed rows.

Configure Experian Batch

Use Data Studio to apply your Experian Batch reference data license: click on your username, select the Update license dialog and enter your license key. Note that you will have to restart the service for the changes to take effect.

You have to install and configure Experian Batch reference data:

1. Install 
Install any of the datasets you have received. Experian data files have a vintage and built-in expiry date.

Note that you will have to keep your data updated on a regular basis for address validation to continue to work.

2. Configure

Navigate to addressValidate\runtime folder in the Aperture Data Studio installation directory (by default C:\ProgramData\Experian) and edit the qawserve.ini file.

Show hidden files/folders has to be enabled for the ProgramData folder to be visible.

This file defines where data files are and how the data is mapped to a country.

Installed data directory
Under the [QADefault] section, add a line to the InstalledData setting, specifying the location where the data is installed:
InstalledData={ISO},{Data Directory}
If you have more than one dataset, each one must be on its own line preceded by a '+' sign. For example:


Data mapping
In the same section, add at least one line to the DataMappings setting to specify the datasets you wish to use:
DataMappings={data mapping identifier},{dataset/group name},{dataset+additional datasets}
If you have data for more than one country, each one must be on its own line preceded by a ‘+’ sign. For example:

DataMappings=GBR,Great Britain,GBR

USA data only
If you are using USA data, you have to also specify the location of the supplementary USA Batch data and libraries. In the same section of qawserve.ini file, set the path using the CorrectADataLocUSA setting. For example:


Canada data only
If you are using Canada data, you have to also specify the location of the supplementary Canada Batch data and libraries. In the same section of qawserve.ini file, set the path using the CorrectADataLocCAN setting. For example:


USA or Canada data only
If you are using USA or Canada data, you have to update the CorrectAApiLoc setting to point to the CorrectAddress library used for USA and Canada address matching. This supplementary library is usually installed alongside the Correct Address data. For example:


Please restart the Experian Aperture Data Studio Database Server service after making any configuration changes.

Custom layouts

From Data Studio v1.6 onwards, user-defined layouts can be used to specify the number, content and format of the address output columns.

When a custom layout is defined in the Experian Batch API qaworld.ini config file, a Custom option will be available in the Additional options menu (in addition to addition to the Standard (7-line) and Component (28-line) default layouts).

To create a custom layout, navigate to addressValidate\runtime folder in the Aperture Data Studio installation directory (by default C:\ProgramData\Experian\addressValidate\runtime) and edit the qaworld.ini file using a text editor.

The custom layout has to be named [CustomISO], where ISO matches the country base name, and only one of these can be defined per country data set.

If this is your first time creating a custom layout, see the relevant data guide for Address Element Codes and the Batch API guide for some additional settings.

Once you've created a custom layout, we recommend checking that it is valid and correct using the BATWV64.EXE test harness before using it in Data Studio. 

We also recommend that you restart the Data Studio service after adding/updating a custom layout.

Here's an example of a custom layout that will return a 5-column output with:

  • Line 1 containing business name and department information
  • Line 2 containing automatically formatted premise and street information
  • Lines 3 to 5  containing town, county and postcode, respectively




If you can't find an answer or a solution, contact support.

Unable to read countries

Your Experian Batch isn't configured correctly.

To check, go to the addressValidate\runtime folder in your Data Studio installation (e.g. C:\ProgramData\Experian\addressValidate\runtime).

Show hidden files/folders has to be enabled for the ProgramData folder to be visible.

Using the Command  Prompt, run BATWV64.EXE (the Experian Batch API test harness). You should see the list of available address layouts. For Use layout number enter the number of the layout from the list that corresponds to a country you have configured. 

If you get an error, Experian Batch hasn't been configured correctly. Contact support for help.

Note that when configuring the TigerLine dataset for the USA, the TigerLineAPI= setting is not optional.

Unable to read countries but the layouts are working in Experian Batch test harness

By default, the qaworld.ini contains all the address and component layouts used by each data set.

You shouldn't delete these layouts but you can make modifications as long as the layout continues to be valid (i.e. it works in the test harness).

If the qaworld.ini no longer contains address and component layouts, we recommend rolling back to the default version which can be found in addressValidate\templates.