Transactional data

Load transactional data directly into your Apteco CDP alongside contact and individual data, creating hierarchical relationships and updating records incrementally.

How transactional tables relate to individuals

Transactional tables connect to the 'Individual' table in one-to-many relationships. Each individual can have multiple transaction records, and you can create parent-child relationships between transactional tables.

Tip: Create multiple sibling transaction tables as well as parent-child structures. The sibling approach works well when you have different transaction types in a single file.

E-commerce order history

Load customer data with order and product information from repeated rows per customer and order.

Data source includes:

  • Customer details

  • Order information (order ID, date, status, payment method)

  • Order items (product, quantity, unit price, total price)

Transactional tables:

  • Order (parent: Individual)

  • Order Item (parent: Order)

Banking transaction history

Load customer account data with transaction records and categories.

Data source includes:

  • Customer details

  • Transaction information (transaction ID, date, amount, type)

  • Transaction categories (category ID, description, merchant)

Transactional tables:

  • Transaction (parent: Individual)

  • Transaction Category (parent: Transaction)

Prerequisites

Before you begin, ensure that:

  • You’ve imported your data source into Orbit

  • Your source data includes a unique identifier for each transaction type

  • You understand the hierarchical relationships between your transaction types

Note: Duplicate row counts are expected when loading transactional data, as multiple transaction records per individual create repeated rows in the source.

Net out duplicate rows during the ID resolution processing.