File format: NDJSON

Newline-delimited JSON (NDJSON) is a data format for structured data that defines the structure of JSON data using lines as separators. Each line in a NDJSON file is a valid JSON value.

Pull NDJSON files

To pull NDJSON files to Amperity:

  1. Select a data source.

  2. Configure a courier for the location and name of the NDJSON file.

  3. Define a feed to associate the fields that were selected from the NDJSON file with semantic tags for customer profiles and interactions, as necessary.

Data sources

Pull NDJSON files to Amperity using one of the following data sources:

Load data

Use a feed to associate fields in the NDJSON file with semantic tags and a courier to pull the NDJSON file from its upstream data source.

Couriers

A courier brings data from an external system to Amperity.

A courier must specify the location of the NDJSON file, and then define how that file is to be pulled to Amperity.

  1. File settings

  2. Feed selection

File settings

Use the File settings section of the courier configuration page to specify the path to the NDJSON file and to define formattting within the file.

Feed selection

Use the Feed selection section of the courier configuration page to identify the feed for which this courier pulls data, and then which files are loaded.

From the Load type dropdown select one of:

  • Load Use this option to load data to the associated domain table.

  • Truncate and load Use this option to delete all rows in the associated domain table, and then load data.

Feeds

A feed defines how to load data into a domain table, including specifying required columns and columns with semantic tags for customer profile (PII) or transactions data.

Apply profile (PII) semantics to customer records and transaction, and product catalog semantics to interaction records. Use blocking key (bk), foreign key (fk), and separation key (sk) semantic tags to define how Amperity should understand values that exist across data sources.

Send NDJSON files

Amperity can send NDJSON files to downstream workflows using any of the following destinations: