*Event Data Integration: File Dump
Share CSV file dumps to Symbiosys via shared cloud storage bucket (e.g., GCS, S3, Azure). Symbiosys will create and share a bucket for you, or you can share your own bucket if you prefer.
Bucket Sharing Options
[Preferred] Option 1: Using a Symbiosys-owned GCS Bucket
Symbiosys will provide a Google Cloud Storage (GCS) bucket for data ingestion. At your request, your team will receive write access via email and/or a service key.
Requirements:
[Optional] Encryption: If you prefer the service key to be encrypted before sharing via email, please provide your Symbiosys Sales Engineer with your public key for encryption.
[Optional] Test File: We recommend sending a test file to validate the connection before regular data uploads.
File Upload Schedule: Files should be uploaded on a regular cadence – hourly or at least once daily.
Processing Window: Files can contain events from previous days as per your order processing window, but do try to limit this window to 3 days if possible.
Folder Structure: Files containing visits and orders should be stored in separate folders to ensure organized processing.
File Formatting: Files should be in CSV format with UTF-8 encoding and use a standard delimiter (e.g., comma or tab).
File Naming Convention: Use a structured format, such as:
retailername_visits_YYYYMMDD.csvretailername_orders_YYYYMMDD.csv
Option 2: Using a Retailer-owned Cloud Storage Bucket
If you prefer to use your own storage solution, Symbiosys can access your designated bucket.
Requirements:
Create or Use an Existing Bucket: Ensure that the bucket is accessible to Symbiosys.
Folder Structure & Update Schedule: Files should be structured similarly to Option 1, with separate folders for visits and orders, and updated at least once daily.
Access Permissions: Provide Symbiosys with the necessary credentials and assign appropriate IAM roles:
Google Cloud Storage (GCS):
Storage Object ViewerorStorage Object AdminAWS S3:
AmazonS3ReadOnlyAccessor equivalentAzure Blob Storage:
Storage Blob Data Reader
Service Key Security: If required, encrypt the service key before sharing.