Integration Specifications
This article will help you learn about how Daasity replicates data from Ometria, limitations to the data we can extract and where the data is stored in the Ometria schema
Integration Overview
Ometria is a customer data and marketing platform that helps retailers drive CRM growth through their "Ometria Retail Sucess Model", which has proven to accelerate revenue.
There are two ways that Daasity pulls data from Ometria:
Ometria API Endpoints
Self-Serve Data Export: data is sent to an AWS S3 bucket (you can enter your S3 details or contact support to use the Daasity S3 server)
This document provides context on what kind of data is being gathered through this extractor, which endpoints that data is coming from, and how the extracted tables relate to each other.
Integration Availability
This integration is available for:
Enterprise
API Endpoints
The Daasity Ometria extractor is built based on this Ometria API documentation. The following endpoints are used by Daasity to replicate data from Ometria:
AWS S3 Feed
The Daasity Ometria extractor is also built based on this Ometria Self-Serve Data Export documentation. The following is used by Daasity to replicate data from Ometria:
Entity Relationship Diagram (ERD)
Click here to view the ERD for the Daasity Ometria integration illustrating the different tables and keys to join across tables.
Ometria Schema
The Daasity Ometria extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.
Profiles
Endpoint: Profiles
Update Method: UPSERT
Table Name: [
ometria.profiles]
Member Lists
Endpoint: Lists
Update Method: UPSERT
Table Name: [
ometria.member_lists]
Lists
Endpoint: Lists
Update Method: UPSERT
Table Name: [
ometria.lists]
Email Events
Endpoint: Email Events
Update Method: UPSERT
Table Name: [
ometria.email_events]
Unsubscribes
Endpoint: Unsubscribes
Update Method: UPSERT
Table Name: [
ometria.unsubscribes]
Last updated