Events are one of the data points that occur on your site that we want you to import into our platform. You can use the Event Imports dashboard to import your events. You can either:
- Upload an events data CSV file from the UI.
- Upload events data files to an S3 bucket and schedule an import task.
- Import directly from Snowflake database.
- Use the Send an event API or the Send Bulk events API to send events to Blueshift.
- Events from your mobile app. If you use Blueshift's SDKs to integrate your apps with Blueshift, you can send customer data to Blueshift. For more information, see Blueshift's Developer Portal.
Include the following information with the events data:
- A customer identifier (email or customer_id).
- A Product ID (separated by a delimiter if there are multiple products).
- We recommend that you include a timestamp field. If you don't set the timestamp field, Blueshift considers the event's timestamp as the time when the event is imported into Blueshift. Ensure that you provide the timestamp in the ISO8601 format. For example, 2016-02-02T04:19:42Z.
- Ensure that event names do not contain periods, are not numeric, and the event name does not have more than 64 characters.
- In addition, the data format limitations on the user imports are applicable to event imports as well.
For more information, see Data types and attributes in Blueshift. You can also click the Download Sample CSV link in an import task and review its format to understand the type of file required.
View Import Tasks
To import events, go to the Setup menu and click Events. Click the Import Events icon and then click +Event Import.
Click an event to view the various import tasks for the event.
The status for each Snowflake task is shown on the Events imports page along with an overall status that identifies which state the task is in.
A task can be in one of the following four statuses:
|Draft||The task is saved along with the configuration but not launched as yet. This is an inactive state.|
|Launched||The task is active. If it is a recurring task, the task remains in this state for the entire duration of its lifetime.|
|Paused||The task has been paused. This is an inactive state which occurs only when a task is paused by the user.|
|Completed||The task has completed its life cycle. This is an inactive state and is reached only when a recurring task reaches its end time or when processing is completed for a one time task.|
Import task status
When you click an individual task, the Import task details page opens. You can view more details about the status for each execution run for a recurring task.
Last Fetch status
The top left corner of the details page shows the following information:
- Last Fetch Status - Shows the status for the last run of fetching of data from Snowflake into Blueshift. The status can be Fetching, Fetched, or Failed.
- Fetch Start time - Shows the start time for the last run of fetching of data from Snowflake into Blueshift
- Fetch end time - Shows the end time for the last run of fetching of data from Snowflake into Blueshift
File processing status
This provides details on the processing of fetched data for each recurrence. The status can be Processing, Processed, or Failed.
Note: If there are errors in processing the fetched data, the status is still set as ‘Processed’. The number of errored rows in the table indicate whether there were any errors when the data was processed.