We'd like to gather data on important operations occurring within our e-commerce infrastructure. In order to do so, we need to identify an appropriate set of analytics events to collect, as well as the locations at which these events should be emitted.
...
The following signals could be paired with Segment's e-commerce API to emit events of interest to marketing.
| Signal | Corresponding Segment e-commerce API Event, if any |
|---|---|
| basket_addition | Added Product |
| voucher_addition | None (custom: edx.bi.ecommerce.voucher_applied) |
| start_checkout | Started Order |
| pre_payment | None (custom: edx.bi.ecommerce.to_payment_processor) |
| post_payment | None (custom: edx.bi.ecommerce.payment_completed) |
| order_placed | None (custom: edx.bi.ecommerce.order_created) |
| post_checkout | Completed Order |
| refunded_order (custom signal) | Refunded Order |
This information constitutes business intelligence (BI). As such, it is not researcher-facing, does not need to be included in our tracking logs. However, victorR (Deactivated) thinks we could benefit from including this information in the tracking logs, for debugging purposes.
...
Finally, these events could be complemented by a set of new events outside of the ecommerce service. For example, events like "Viewed Product Details" and "Clicked Product" could be emitted when users view course about pages and click course cards. Events like "Viewed Promotion" could be used when marketing uses special means (e.g., a dedicated page) to advertise certain products.
A Note About Enrollments
...