Event Data Scheduler
Scheduling events data via sFTP/S3
With this feature, users will be able to send all event data back to the client's FTP/S3 bucket as a zip file.
All web & app events - custom & system events (along with all payloads) that are tracked by Netcore CE can be scheduled on a daily basis.
This is a premium feature that will be charged on a monthly basis.
Interested clients can reach out to respective account managers for the details. The feature will be enabled by the product team.
Clients should have their own sFTP server/S3 bucket & should share the following details.
- Console login
- Bucket link
- Access key
- Secret key
- Server details
- Path details
- Port details
Format of the scheduler
Daily scheduler will consist of a zip file that will contain multiple CSVs - each CSV for individual event data
These CSV files will contain all the event data (including all event payload data)
Zip file format - clientID_date-of-data.zip
CSV file format - event-name_date-of-data.csv
Each file will be exported to client's sFTP/S3 bucket by 7 am of the next day.
Once the feature is enabled, clients will receive the files by morning 7am
If they are receiving 1st Jan's event data, they will receive the file by Jan 2nd, 7am
Name of the file will be Client ID_ 01012022.zip
Say Add to cart & product purchase were the events performed
In that case, 2 CSV files will be part of the zip file:
add to cart_01012022.csv
Event CSV file format
Following event parameters will be part of the CSV:
appVersion - App version of the end user
appId - Unique identifier for your app integrated on Netcore CEE
siteId - Unique identifier for your website integrated on Netcore CEE
model - Device model number
eventId - Unique ID for event
eventType - event performed on app or web
ts - Timestamp of when the event was performed
purl - URL of previous page (for web event)
url - Current url of the page (for web event)
pts - Time spent on page (for web event)
sdkVersion - SDK version
osVersion - version of the OS
Identity - Primary key of the end user
osType - Type of OS on device (e.g. Android, iOS)
Make - Device brand name
Medium - Broadcast / Journey / Onsite
msgId - Message id of attributed campaign (wherever goal event is added in campaigns)
sessionId - Session ID for app
sid - Session ID for web
Payload. - value for the event parameter (payload)
Updated 4 months ago