Integrations
      Back to home
      1. Help Center
      2. ELT+ | Technical User Documentation
      3. Integrations

      Integration: Ometria

      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.

      Key Topics

      Click on the links below to take you to the section where you can learn more about this Integration

      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:

      • Pro V2

      NOTE: You are considered V2 if...

      • Your account says Pro V2 in the Daasity App

      Not sure? Reach out to Support@Daasity.com

      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)

      The embedded diagram houses the ERD for the Daasity Ometria integration illustrating the different tables and keys to join across tables. Hover over the embedded diagram to reveal controls to zoom and scroll.

      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
      JSON Element Database Column
      id profile_id
      email email
      phone_number, limit: 32 phone_number
      customer_id, limit: 64 customer_id
      name, limit: 128 customer_name
      lastname, limit: 128 last_name
      firstname, limit: 128 first_name
      gender, default: nil gender
      country, limit: 32 country
      marketing_optin, default: nil marketing_optin
      timezone timezone
      date_of_birth, limit: 64 date_of_birth
      seen, default: nil seen
      lifecycle_status lifecycle_status
      is_email_valid, default: nil is_email_valid
      properties::zip, limit: 16 zipcode
      properties::city, limit: 64 city
      properties::address1 address1
      properties::address2 address2
      properties::province, limit: 64 state
      properties::shopify_tags shopify_tags
      dates::account_created account_created_date
      update_since updated_at
      dates::marketing_optin marketing_optin_date
      dates::marketing_optout marketing_optout_date
      Daasity: account_id _account_id
      Daasity: source_id __source_id
      Daasity: MD5(source_id + id) __sync_key
      Daasity: timestamp when loaded into DB __synced_at

      Member Lists

      • Endpoint: Lists
      • Update Method: UPSERT
      • Table Name: ometria.member_lists
      JSON Element Database Column
      MD5(source_id + id + profile_id + timestamp) member_list_id
      id, limit: 64 list_id
      profile_id, limit: 64 profile_id
      email email
      timestamp event_at
      event event
      Daasity: account_id _account_id
      Daasity: source_id __source_id
      Daasity: MD5(source_id + id + profile_id + timestamp) __sync_key
      Daasity: timestamp when loaded into DB __synced_at

      Lists

      • Endpoint: Lists
      • Update Method: UPSERT
      • Table Name: ometria.lists
      JSON Element Database Column
      id list_id
      title list_title
      description list_description
      status, limit: 32 list_status
      type, limit: 32 list_type
      timestamp_created created_at
      timestamp_stats_updated updated_at
      Daasity: account_id _account_id
      Daasity: source_id __source_id
      Daasity: MD5(source_id + id) __sync_key
      Daasity: timestamp when loaded into DB __synced_at

      Email Events

      • Endpoint: Email Events
      • Update Method: UPSERT
      • Table Name: ometria.email_events
      JSON Element Database Column
      MD5(source_id + to_address + event_type + dt_occurred) email_event_id
      event_id event_id
      uuid send_id
      to_address email
      event_type event_type
      dt_occurred event_at
      bounce_class bounce_class
      reason bounce_reason
      device_type device_type
      geo_country geo_country
      geo_region geo_region
      geo_timezone geo_timezone
      target_url target_url
      campaign_title campaign_title
      campaign_type campaign_type
      Daasity: account_id _account_id
      Daasity: source_id __source_id
      Daasity: MD5(source_id + to_address + event_type + dt_occurred) __sync_key
      Daasity: timestamp when loaded into DB __synced_at

      Unsubscribes

      • Endpoint: Unsubscribes
      • Update Method: UPSERT
      • Table Name: ometria.unsubscribes
      JSON Element Database Column
      MD5(source_id + profile_id + timestamp) unsubscribe_id
      profile_id profile_id
      email_address email
      timestamp event_at
      send_id send_id
      mass_campaign_id mass_campaign_id
      trigger_campaign_id trigger_campaign_id
      reason unsubscribe_reason
      reason_text unsubscribe_reason_text
      Daasity: account_id _account_id
      Daasity: source_id __source_id
      Daasity: MD5(source_id + profile_id + timestamp) __sync_key
      Daasity: timestamp when loaded into DB __synced_at

      Related Resources