# Ticketek Data Ingestion Flow

This document outlines the process for ingesting Ticketek data into our Snowflake data warehouse, ensuring seamless data management and availability for analysis.

## S3 Drop Location
Incoming data files are stored here:  
`S3://prod-orcdbucket/feed-drop/Ticketek/`

## Snowflake Destination
Ingested data is loaded into the following Snowflake environment:

| **Property** | **Value**         |
|--------------|-------------------|
| **Account**  | `DELPHI`          |
| **Database** | `FAN_LIVE_EVENTS` |
| **Schema**   | `QA\PROD`         |

## Daily Reports
The following reports are generated from the raw data:

| **Report Name**   | **Staging Raw Table**          | **Frequency** |
|-------------------|--------------------------------|---------------|
| Event Booking      | `RAW_TICKETEK_EVENT_BOOKING`       | Daily         |


## Key Features
### 1. Protecting PII  
We handle sensitive information such as email addresses and phone numbers with care by RBAC on these fields, ensuring compliance with data governance standards.

### 2. Data Validation   
The ETL pipeline includes robust validation checks to:
- Verify no required fields are null.
- Ensure data conforms to expected formats and ranges.

### 3. Monitoring and Alerts  
Comprehensive logging and alert systems are in place to monitor the flow, detect anomalies, and resolve issues swiftly.

---

For more details on transformations, validation rules, or pipeline configurations, please refer to the [Technical Design Document](#).