diff --git a/_docs/_partners/braze_currents/data_storage_events/event_delivery_sematics.md b/_docs/_partners/braze_currents/data_storage_events/event_delivery_sematics.md index cf86f14d186..e3eb23f373e 100644 --- a/_docs/_partners/braze_currents/data_storage_events/event_delivery_sematics.md +++ b/_docs/_partners/braze_currents/data_storage_events/event_delivery_sematics.md @@ -32,7 +32,7 @@ The Braze Currents data storage integrations output data in the `.avro` format. Currents will create a file for each event type using the format below: ``` -/dataexport..S3.integration./event_type=/date=///dataexport..S3.integration.++.avro +/dataexport...integration./event_type=/date=///dataexport...integration.++.avro ``` _Can't see the code because of the scroll bar? See how to fix that [here]({{ site.baseurl }}/help/help_articles/docs/scroll_bar_overlap/)._ @@ -41,6 +41,7 @@ _Can't see the code because of the scroll bar? See how to fix that [here]({{ sit |---|---| | `` | The prefix set for this Currents integration. | | `` | For internal use by Braze. Will be a string such as "prod-01", "prod-02", "prod-03", or "prod-04". All files will have the same cluster identifier.| +| `` | The identifier for type of connection. Options are "S3", "AzureBlob", or "GCS". | | `` | The unique ID for this Currents integration. | | `` | The type of the event in the file (see event list below). | | `` | The hour that events are queued in our system for processing. Formatted YYYY-MM-DD-HH. |