@Michael_Soprano One thing to note there is that the 20GB limit per hour is regarding Batch Ingestion API. Ingestion from batch source can handle up to 200GB per hour. 

Hi @RyanMoravick Multiple eventTypes in one dataset should not be a problem. For example we have ingested multiple Cart Events into one dataset. Each eventType shall still hold its own unique timestamp based on the event.Hope this helps.David

Complete - thanks @brekrut 

Table name will always stay consistent with original dataset name - you could create a new dataset as @itsme_ssj mentioned, but if you already have data loaded to the first dataset and do not want to delete and re-ingest, then this would not be advised.

Completed the new form @brekrut 

Hi AllI have a few questions I wanted to pose: 1. Should there be a limitation on event types from the source data that will exist in our specific schema (AEP Event Schema) in this example?  Any concerns if this schema continues to grow without limitation on objects existing in Event Classification ...

Hi @AdamKi1 I believe you might be thinking of this incorrectly. Audiences that are batch evaluated, are being fed via datasets that are sourced from batch ingestion data. (Think Amazon S3) Audiences that are streaming, are being fed via datasets that are sourced from near real time data (Think Amaz...

@Michael_Soprano Yes, this is correct. Timestamp is based on the most recent ingested record via timestamp. Whereas Dataset Precedence allows you to set which dataset you trust over the other, when it comes to the same data attributes that may live in multiple datasets.Hope this helps.David

@JeanBaro_  yes that is correct

Hi @kendallhall You are unable to export that ID to a destination. That is just the internal ID given by AEP. You also cannot look that ID up in the profiles browse tab. You can only search by identity values.Thanks,David