Dynamic Yield collects data about user interactions with your site such as events and pageviews. To leverage this data outside of Dynamic Yield’s platform, such as your Analytics platform, you can enable a daily export of the raw user activity data.
Once enabled, the data for the previous 24 hours is exported every night at midnight to an S3 bucket (based on the site time in your site’s settings).
Note: This feature is only supported on Dynamic Yield sites of type Website (not Mobile Apps). It does not include offsite events fired from sites that do not have a Dynamic Yield script, or that are using a Dynamic Yield script from another site.
Enabling the Daily Activity Stream
- Go to Settings › General Settings › Daily Activity Stream.
- Click Turn On Daily Report. Your S3 bucket and credentials will be displayed. Copy the information to a secure location as it is only displayed once.
Every night at midnight (in the time zone defined in your site settings), a file will be uploaded to the S3 bucket. Each filename contains the date. - If you disable the export, and then enable it again, your S3 bucket will stay the same. However, the credentials will change.
- You can view the status of the daily export in the Daily Activity Stream area of the General Settings page.
Note: If you lost your credentials, click the additional option iconand select Generate New Credentials. There is a limit to the number of times you can generate new credentials, so please be sure to save the credentials in a secure manner.
Data Format
The file is in Apache Parquet format that is optimized for large data sets. It contains one entry for every instance of the following types of events:
- Dynamic Yield Events
- Pageviews
The following table displays information about the different columns in the Parquet file. Each line will only have values for some of the columns, depending on the type of data (event, pageview, etc.). Your file may include additional columns which are not supported at this time.
Attribute | Data Type | Description |
---|---|---|
dyId |
Long |
The internal identifier Dynamic Yield assigns to each visitor in the site or app, unique per device. |
timestamp |
Long |
The time of the event, pageview or variation engagement in milliseconds from the UNIX epoch. |
sectionId |
Integer |
The Dynamic Yield site ID as assigned in your Dynamic Yield account. |
eventType |
String |
The type of event fired. It is always one of the following:
|
sessionId |
Integer |
|
eventId |
Integer |
A unique identifier for each event explicitly fired from the site. |
eventName |
String |
The event name as written in the event API. |
eventProperties |
String (JSON) |
The event parameters as written in the event API. These differ depending on the eventType value. |
eventValue |
Long |
The monetary value of an event as written in the event API. |
uniqueTransactionId |
String |
A unique transaction id for purchase events, as written in the purchase event API. |
productIds |
String array |
One or more product SKUs, depending on the fired event. Purchase events may have more than one SKU, add to cart events may only have one SKU, and many other events have no value for this attribute. |
url |
String |
The URL from which the event was fired. |
urlClean |
String |
The URL from which the event was fired, after removing any URL parameters. |
contextType |
String |
Together with contextData, this information comprises the page context. This attribute specifies the type of page. It is only defined for pageview events. |
contextData |
String array |
Together with the contextType, this information comprises the page context. This attribute specifies different information depending on the page type. For example, if the contextType is Product, the contextData would contain the Product SKU. It is only defined for pageview events. |
audiences |
Integer array |
The list of audience identifiers the user is a member of at the time of firing the event. |
browser |
String |
The browser type from which the event was fired. |
operatingSystem |
String |
The operation system of the device that fired the event. |
screenResolution |
String |
The screen resolution of the device that fired the event. |
userAgent |
String |
The user agent string of the device from which the event was fired. |
Importing Data Into Your Analytics Platform
In order to analyze data based on daily activity data, you need to ingest the Parquet file from the S3 folder into the data warehouse used by your Analytics platform. Refer to the documentation of your data warehouse for more information. Here are some links to the relevant articles of some common ones: