Skip to main content

Experian Match release notes

2.7.1

Mar 29, 2018

Experian Match API v2.7.1

This release adds a new data connector, input types and performance improvements, alongside general fixes and improved clustering.

Enhancements

  • Improved clustering of low confidence matched records.
  • Email and Phone data types added.
  • JMS input and output connectors added. This will allow the use of message queues such as ActiveMQ.
  • A new system status endpoint has been added which exposes information on the current licensing status.
  • Intermediary match stores can be optionally purged on job completion.
  • Jobs can be queued if one is already running and cancelled if queued or running.
  • Performance improvements for GDQ Standardize, resulting in a 25% improvement for Match jobs.
  • Improvements to the performance of transactional Add/Update operations.

Breaking changes

Any existing integrations with Match will have to be updated to account for the following changes: 

  • GDQ Standardize will need to be updated to version 4.0.0. New prerequisite: .NET Framework 4.6.2.
  • The job state of “STARTED” has been changed to “PENDING”. A processing job will continue to have the state of “RUNNING”.
  • Licensing has changed and a new license key will be supplied. Please refer to the licensing information in the documentation for details.

2.4.0

Dec 12, 2017

Experian Match API v2.4.0

This release adds performance and stability improvements allowing for higher capacity processing, alongside general fixes and better default matching behaviour.

In addition, Match now allows the configuration of grouped elements of any input type opening up the ability to process multiple names, addresses and/or generic elements.

Enhancements

  • Stability improvements when processing large inputs.
  • Grouping ability allows multiple names, addresses and other generic input fields to be matched.
  • Updated rules and resources for UK and Australia leading to higher country address match coverage.
  • Stored Blocking Keys are stored securely using SHA-256 hashing.
  • New API method for retrieving default blocking keys per country.
  • Granular name elements, including Forenames and Surname can now be specified in input.
  • Better handling of non-alphabetic characters in Field group names.
  • Improvements to cancelled/failed job error handling.

Breaking changes

Any existing integrations with Match will need to be updated to account for the following changes: 

  • Search and Transactional operations will fail against existing Match Stores due to the new salt and hash of blocking keys. Consult the documentation for how to turn off hashing to continue using your existing sessions, or alternatively recreate your Match store.
  • Existing Match rules that include field groups for multiple generic strings will need to be prefixed by the field group name with a hash symbol e.g.

    AccountId.Generic_String.Exact={[ExactMatch]}

    Must now be written as

    #AccountId.Generic_String.Exact={[ExactMatch]}

    This hash notation only applies to the field group when it is used in the rules; no changes are required to the blocking keys or input field mappings.

2.0.0

Sept 15, 2017

Experian Match API v2.0.0

The latest version of Experian Match adds the ability to perform transactional updates against a match store.  Allowing users to synchronise the match store with operational systems, maintain linkage across data silos and trap and cascade contact data changes across the organisation. 

Enhancements

  • Match store can be maintained over time through a set of add, delete and update REST API requests.
  • Addition of Date data type for matching.
  • New API methods for configuring blocking keys
  • Addition of blocking key statistics to improve performance tuning
  • Clustering algorithm updated to produce optimal clusters where multiple potential matches/clusters exist
  • Support for different match rules for real time search and initial build of the match store
  • Improved logging for standardisation errors
  • Support for encrypted SQL Server data stores

Breaking changes

Any existing integrations with Match will need to be updated to account for the following changes:

  • The Match API is now at version 2. All API calls will need to be changed to v2 instead of v1.  Additionally, blocking key ids are now required when creating a session endpoint.
  • The match store schema has been altered. New tables have been added and the INDEX table has been modified.  It is required that the match store is re-created from scratch.