GTV-Connector

The GTV-Connector is an out-going gateway for customer data. Data is pushed to an external system from Gotransverse.

The connector supports two base types: integrations and extracts.

• Integrations allow synchronizing Gotransverse data into external systems. The GTV-Connector understands the data being delivered, keeps track of each records status, ensures that each record is delivered (without duplicates), while also maintaining an audit trail for each delivered record that is returned to Gotransverse. Each Integration has a Data Set, which defines the records in Gotransverse that are considered part of the Integration, and a set of Source and Target fields. The Source fields are the available data points in Gotransverse, and the Target fields are the available data points in the target system. Both Source and Target fields vary with configuration and integration type. A configuration defines how the data in the Source fields maps to the Target fields to create records in the target system. Users can create one or multiple configurations for a given integration and create runs from it both on demand and on a schedule.

• Extracts allow pulling data, usually in the form of a file, out of Gotransverse and pushing it to an external system, usually AWS S3 or SFTP. Different Extract types vary in how data is queried and sent. Extracts can be run either on demand (using a Custom Job run) or on a schedule (using a Rolling Date Range and the inception date). Some Extracts can also run on a schedule as full Extracts, without any data selectors, if the inception date is not set. Some Extracts provide standard functionality, while others require custom configurations.

  When using Extracts, the GTV-Connector does not understand the data being extracted and does not keep track of the delivered data.

The GTV-Connector application also includes a Run Manager module, where runs and schedules for integrations and extracts are managed.