Events - direct upload from UI

You can import event data into Blueshift by directly uploading a CSV file through the Blueshift UI. Ensure the CSV file is prepared with the correct data types and formats. Download the sample CSV file for reference.

Starting your event import journey

• Navigate to Events: Go to Customer Data > Events in the left navigation bar.
• Open the Import Menu: Click the Import Events button at the top of the Events page.

• Select a Data Source: Choose your preferred data source from the available options.

Proceed with the selected data source to configure your import settings.

Left-side panel overview

• Source: Displays the method of data upload. Example: Direct File Upload.
• Destination:
  • Specifies the target location for the data. Example: Events.
  • Requires selecting an event under Select Event (mandatory field).
• Trigger Campaigns: An optional checkbox to activate campaigns based on imported event data.
• Notification Preferences:
  • To: Email IDs to receive task notifications.
  • CC: Additional recipients for notifications.
  • Settings:
    • Notify - Any Status: Sends notifications for all task statuses.
    • Notify - If more than [X]% of records fail, send alerts based on a failure threshold, e.g., 70% of records fail.

Source configuration for CSV upload

Upload the CSV file and click the Continue button to proceed.

Import file settings

• Format (Mandatory): Choose from CSV or JSONL.
• Encoding (Mandatory): Options include:
  • Unicode (UTF-8, UTF-16, UTF-16 Little Endian, UTF-16 Big Endian)
  • Western Europe (ISO-8859-1).
• Delimiter (Mandatory): Options include:
  • Comma (,), Tabs (\t), Pipe (|), Semicolon (;)
  • Record Separator (ASCII 30), Unit Separator (ASCII 31), Others (customizable).
• Click Continue to proceed.

Data configuration & validation

• Sample Data: Displays 10 records fetched from the source to assist in field mapping.
• Field Mapping:
  • Map the Source Attribute Name to the corresponding Destination Attribute Name and specify the Destination Data Type.
  • Mapping Instructions:
    • Only columns mapped to a destination attribute will be imported.
    • Map Floating point numeric data types from the source to Decimal in Blueshift.
    • Example: For events like purchase, add_to_cart, wishlist, or view, map a column to product_ids (required for events interacting with product catalogs).
    • Ensure one column is mapped to a customer identifier, such as customer_id, email, my_custom_id, cookie, device_id, or my_external_id.

Data Quality Check:

• Use Check Data Quality to validate field mappings.
• View data quality percentages, errors, and hints for corrections in the modal.
• Adjust mappings as needed.

Test Run:

• Click Test Run to validate with up to 10 records.
• The modal displays source data alongside mapped JSON.
• Update mappings and re-run tests if necessary.

• Next Steps: Address all validation issues and click Continue to proceed with the import.

Scheduling and launching the import task

Select import immediately to begin the import instantly. Otherwise, select the start date and time for the import.

View task status

The status of each import task is displayed on the Event Imports page, providing a clear overview of the task's current state and key details like records processed and update frequency.