Reference for Email Delivery

This guide lists the predefined objects in Resource Analytics for Email Delivery. You can find information about views, entity relationships, subject areas, and sample queries.

Views

This section provides information about views within Resource Analytics Email Delivery and their columns, data types, keys, and the referred view and column names. The following views are available:

Email Delivery Views
NameDescription
EMAIL_DELIVERY_DKIM_DIM_V This view stores information on the properties that define a DKIM.
EMAIL_DELIVERY_EMAIL_DOMAIN_DIM_V This view stores information on the properties that define an email domain.
EMAIL_DELIVERY_EMAIL_RETURN_PATH_DIM_V This view stores information on the properties that define an email return path.
EMAIL_DELIVERY_SENDER_DIM_V This view stores information on approved senders.
EMAIL_DELIVERY_SUPPRESSION_DIM_V This view stores information on email suppressions.
EMAIL_DELIVERY_DKIM_FACT_V Fact table for Email Delivery DKIMs.
EMAIL_DELIVERY_EMAIL_RETURN_PATH_FACT_V Fact table for Email Delivery return paths.
EMAIL_DELIVERY_SENDER_FACT_V Fact table for Email Delivery senders.
EMAIL_DELIVERY_SUPPRESSION_FACT_V Fact table for Email Delivery suppressions.

The suffixes in the view names specify the view type:

  • FACT_V: Fact
  • DIM_V: Dimension

Relationship Diagram

This section provides diagrams that define the logical relationship of a fact table with different dimension tables.

The contents of each view and their relationships are listed in the following file: Email Delivery views.

These diagrams show the relationship of the Email Delivery fact views with different dimension views.

EMAIL_DELIVERY_DKIM_FACT_V
Relationship diagram showing the fact table, EMAIL_DELIVERY_DKIM_FACT_V.

EMAIL_DELIVERY_EMAIL_RETURN_PATH_FACT_V
Relationship diagram showing the fact table, EMAIL_DELIVERY_EMAIL_RETURN_PATH_FACT_V.

EMAIL_DELIVERY_SENDER_FACT_V
Relationship diagram showing the fact table, EMAIL_DELIVERY_SENDER_FACT_V.

EMAIL_DELIVERY_SUPPRESSION_FACT_V
Relationship diagram showing the fact table, EMAIL_DELIVERY_SUPPRESSION_FACT_V.

Sample Queries

Sample queries for Email Delivery.

List active DKIMs that were created more than three months ago:
SELECT
    DKIM_ID,
    NAME,
    REGION,
    COMPARTMENT_ID,
    TIME_CREATED,
    LIFECYCLE_STATE
FROM
    OCIRA.EMAIL_DELIVERY_DKIM_FACT_V
WHERE
    IS_ACTIVE_DKIM = TRUE
    AND TIME_CREATED < ADD_MONTHS(TRUNC(SYSDATE), -3);
List the domain IDs associated with each email return path:
SELECT
    EMAIL_RETURN_PATH_ID,
    NAME,
    PARENT_RESOURCE_ID AS DOMAIN_ID,
    LIFECYCLE_STATE,
    TIME_CREATED
FROM
    OCIRA.EMAIL_DELIVERY_EMAIL_RETURN_PATH_FACT_V;
List senders in a specific compartment:
SELECT
    SENDER_ID,
    EMAIL_ADDRESS,
    COMPARTMENT_ID,
    LIFECYCLE_STATE,
    TIME_CREATED
FROM
    OCIRA.EMAIL_DELIVERY_SENDER_FACT_V
WHERE
    COMPARTMENT_ID = '<YOUR_COMPARTMENT_OCID>';
List suppressions that have bounced:
SELECT
    SUPPRESSION_ID,
    EMAIL_ADDRESS,
    REASON
FROM
    OCIRA.EMAIL_DELIVERY_SUPPRESSION_FACT_V
WHERE
    REASON IN ('HARDBOUNCE', 'SOFTBOUNCE');

Data Lineage

The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for Email Delivery provides an end-to-end data lineage summary report for physical and logical relationships in your data.

For more information, see Data Lineage.

Subject Areas

This section provides information on the subject areas with data you maintain in Email Delivery. These subject areas, with their corresponding data, are available for you to use when creating and editing analyses and reports. The information for each subject area includes:

  • Description of the subject area.

  • Business questions that can be answered by data in the subject area, with a link to more detailed information about each business question.

  • Job-specific groups and duty roles that can be used to secure access to the subject area, with a link to more detailed information about each job role and duty role.

  • Primary navigation to the work area that's represented by the subject area.

  • Time reporting considerations in using the subject area, such as whether the subject area reports historical data or only the current data. Historical reporting refers to reporting on historical transactional data in a subject area. With a few exceptions, all dimensional data are current as of the primary transaction dates or system date.

  • The lowest grain of transactional data in a subject area. The lowest transactional data grain decides how data are joined in a report.

  • Special considerations, tips, and things to look out for in using the subject area to create analyses and reports.

The subject area is: