Send query results to Experian

Experian provides credit reporting services and scores to businesses and consumers to help protect them from fraud and identity theft.

This topic describes the steps that are required to send CSV files to Experian from Amperity:

  1. Build a query

  2. Add orchestration

  3. Run orchestration


Experian must be enabled before you can configure an orchestration to send query results. Ask your DataGrid Operator or Amperity representative to enable Experian for your tenant.

Build query

You may need to build a query that shapes the data so that fields in the output are mapped to the fields required by Experian. Data shaping is typically required only one time.

You can do this in the following ways:

  1. Add a SQL table (using Spark SQL) to the customer 360 database that selects PII fields from the Customer 360 table, and then outputs them to a table with columns that map to the required naming patterns.


    PII fields may require SHA-256 hashing or conversion to a UUID using the CAST() function.

  2. Add a SQL query (using Presto SQL) that filters within the query, and then outputs results that map to the required patterns.


    PII fields may require SHA-256 hashing or conversion to a UUID using the CAST() function.

The correct approach here depends on the data and the desired use case (or cases) for downstream workflows.

Map fields to Experian

Required fields will vary based on the Experian product (and downstream use case) to which Amperity will send data, but they generally require the following fields:

  • Inquiry ID (A unique identifier that is present within Experian data)

  • First and last names

  • Complete addresses (street, city, state, zip code)


    Ensure that zip code values do not contain leading zeroes.

Build a query that maps fields in Amperity to the Experian data schema. For example:

  ,given_name AS firstname
  ,surname AS lastname
    WHEN billing_address IS NOT NULL THEN billing_address
    ELSE shipping_address END AS address
    WHEN billing_address IS NOT NULL THEN billing_address2
    ELSE shipping_address2 END AS address2
    WHEN billing_address IS NOT NULL THEN billing_city
    ELSE shipping_city END AS city
    WHEN billing_address IS NOT NULL THEN billing_state
    ELSE shipping_state END AS state
    WHEN billing_address IS NOT NULL THEN billing_postal
    ELSE shipping_postal END AS postal
  ,email AS email_1
  ,phone AS phone_1

Append previous day’s data

In some use cases, you may want to append data that was sent to Amperity from Experian to the data that is sent from Amperity to Experian. The following example queries historical Experian data tables to collect data from the previous day, and then join it to the results:

WITH Experian_Import_Table AS (
    amperity_version = (
      SELECT DISTINCT version
      FROM amperity_table_versions
      WHERE offset = 1

  Experian_Append ex
  LEFT JOIN Experian_Import_Table pr ON pr.clid = ex.clid
  pr.clid IS NULL
  AND substr(ex.clid,14,1) = '-'

Add orchestration

An orchestration defines the relationship between query results and a destination, including the location to which those query results will be sent and the frequency at which the orchestration will be run.

To add an orchestration

  1. From the Destinations tab, click Add Orchestration. This opens the Add Orchestration dialog box.

  2. From the Object Type drop-down, select Query.

  3. From the Object drop-down, select the query for which results will be sent to Experian.

  4. From the Destination drop-down, select a destination that is configured for sending data to Experian.

  5. From the Data Template drop-down, select a data template.

  6. Verify all settings.

  7. Set the workflow to Manual. (You can change this to automatic later, after verifying the end-to-end workflow.)

  8. Click Save.

Run orchestration

Run the orchestration manually to validate that it works.

To run the orchestration

  1. From the Destinations tab, under Orchestrations, open the    menu for the Experian orchestration, and then select Run.

  2. The Status column for the orchestration will update to say “Waiting to start…”, after which the notifications pane will update to include a notification that shows the current status.

  3. When the orchestration has run successfully, the status is updated to “Completed”.