Events - from Databricks

With the integration of Blueshift and Databricks, you can easily import customer interaction data (events and transactions) into your Blueshift account and build a 360-degree view of all your customers. For information about data types and formats, see Import event data.

Prerequisites

Before you can import data from Databricks, you must set up Blueshift integration with Databricks and configure at least one adapter.

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

• Select an adapter: Choose the configured adapter from the dropdown.
• Import type: Choose between import from a table or view.
• Select the respective table or view to import from the dropdown.
• 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.

Select date and timezone format for import

• Select the appropriate format from the Source Date Format dropdown, or leave it blank to use ISO 8601.
• Select the appropriate timezone from the Source Timezone dropdown, or leave it blank to use UTC.

Additional configuration

• Type of Import:
  • Select Full Import to import the entire table or view for each iteration of a recurring task.
  • Select Incremental Import to import only incremental data for each iteration.

• Diff Identification (for Incremental Import): Select Time or Number Based to identify incremental data based on an attribute in the data source.
• Diff Identifier: Select the attribute from the source table or view that will be used to identify incremental changes (e.g., joined_at).

• Save Event (Checked by default): Uncheck if you don’t want to use event activity for segmentation.
• Update Customer Attributes (Checked by default):
  • Uncheck if custom attributes in the event shouldn’t be updated on the customer profile.
  • Identifier attributes will still be updated.
• Update Catalog Activity (Checked by default): Uncheck if you don’t want catalog activities to be used in segmentation.
• Update Transaction Events (Checked by default): Uncheck if you don’t want transaction event data to be updated.
• Allow Blank Event Attributes (Unchecked by default): Select to include blank attributes in the event payload.
• Enable Goal Events Tracking (Checked by default): Uncheck if you don’t want to attribute the event to any campaign.
• Save Products for Recommendations (Unchecked by default):
  • Select to save product interactions for generating recommendations.
  • Product Saving Mode (opens when selected):
    • Replace Products: Replace previous product interactions.
    • Append Products: Add new interactions without removing existing ones.
    • Add to Timeline: Save interactions in chronological order.

• Click Continue to proceed to the next step.

Scheduling and launching the import task

• Select the Start Date using the date picker.
• Check 'Is it a recurring data import?' to enable recurring imports.
• Choose when the task ends:
  • 'Never' for an indefinite schedule.
  • 'At some time' to set an End Date.
• Set the execution frequency (e.g., every 15 minutes).
  • Scheduling options: Minutes, Hourly, Daily, Weekly, and Monthly.

• Review the setup and the top right corner of the screen:
  • Click the Save button to save the task.
  • Click the Launch button to start the task.

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.