Explore the following options for seamlessly sending experimentation decision events to Amazon Redshift to enable robust data integration and enhanced analytical capabilities:
- Experimentation Events Export (E3) – Requires a custom ETL process or a Fivetran purchase.
- (Web Experimentation only) Custom analytics integration – Requires an event ingestion pipeline.
- (Feature Experimentation only) Notification listener – Requires an event ingestion pipeline.
Experiment Event Export (E3)
Use the Experimentation Events Export (E3) to securely access your Optimizely Experimentation event data, letting you flexibly analyze your experiment results.
Considerations
- Configure experiment event exports to enable your team to load these exports into the customer warehouse periodically.
- Prepare to manage long-term maintenance responsibilities.
Get data into experimentation
- Use the oevents CLI or Amazon Web Services SDK.
- Consider using Fivetran as an alternate solution.
Custom integrations for Web Experimentation
Implementing custom analytics integrations introduces extra code execution for an experiment. When you develop your own integration, consider how the target product expects to receive data and how Optimizely Web Experimentation and Optimizely Performance Edge transmit it.
- Modify frontend code to route new events appropriately.
- Develop custom instrumentation as necessary.
Historical data cannot be used, and customers are responsible for managing retries and batching.
Notification listeners for Feature Experimentation
Notification listeners let you programmatically monitor and respond to various events within the SDK in Optimizely Feature Experimentation. When you configure listeners, complete the following:
- Implement callback functionality within the SDK.
- Modify code to route decision events appropriately.
- Develop custom instrumentation as needed.
Historical data cannot be used, and customers are responsible for managing retries and batching.
Please sign in to leave a comment.