Data warehouse integrations are available as a premium add-on for our Web Experimentation and Feature Experimentation module. For more information, please contact your Customer Success Manager.
Once you have enabled the Amazon Redshift integration for your project, you can activate Use Amazon Redshift as a destination to seamlessly send events to your Amazon Redshift account whenever visitors are exposed to one of your Kameleoon experiments.
Activate Amazon Redshift as a destination
To activate Amazon Redshift as a destination:
- Click Use Redshift as a destination.
- Choose your cluster type: Provisioned or Serverless.
- For the Provisioned cluster type, you must provide:
- Redshift cluster ID: Associated with your Amazon Redshift cluster. This cluster ID is a critical component for directing campaign results to the correct destination within Redshift.
- S3 bucket name: The full name of an Amazon S3 bucket that will be used for staging streamed events before periodic bulk loading into Redshift. The policy attached to the AWS role you provided needs to grant access to this bucket.
- Redshift AWS region: A Region code of where your source Redshift cluster resides. This code can be found in your AWS console. Example:
us-west-2. - Database: The name of the Redshift database containing the data you are ingesting.
- For the Serverless cluster type, you must provide:
- Redshift serverless workgroup: Your workgroup’s name.
- S3 bucket name: The full name of an Amazon S3 bucket that will be used for staging streamed events before periodic bulk loading into Redshift. The policy attached to the AWS role you provided needs to grant access to this bucket.
- Redshift AWS region: A Region code of where your source Redshift cluster resides. This code can be found in your AWS console. Example:
us-west-2. - Database: The name of the Redshift database containing the data you are ingesting.
What “Use Amazon Redshift as a destination” does
Enabling Use Amazon Redshift as a destination will stream all Kameleoon experiment exposure events into Amazon.
Events will be stored in the kameleoon_events schema of your {database}—the name of the Redshift database where data is being ingested. This is the AWS database you set up during setup, with write access granted to the Kameleoon user. The data will be saved in a table named kameleoon_experiment_event.
The SQL schema of this table is the following:
CREATE TABLE kameleoon_experiment_event (
nonce BIGINT PRIMARY KEY, -- unique identifier of the event
timestamp BIGINT, -- timestamp in millis of the event
visitor_code VARCHAR(255), -- Kameleoon visitor identifier
custom_visitor_id VARCHAR(255), -- Visitor identifier used by your company
experiment_id BIGINT, -- Kameleoon id of the experiment
variation_id BIGINT -- Kameleoon id of the variation
);The custom_visitor_id is read from the Cross Device Reconciliation custom data, if it has been set.
With campaign data stored in Amazon, you gain the ability to perform in-depth analysis and reporting. You can leverage Amazon’s querying capabilities to extract valuable insights from the collected data, helping you make data-driven decisions to optimize your campaigns and user experience.
By centralizing Kameleoon campaign results in Amazon, you contribute to the enrichment of your Amazon database, making it a comprehensive repository of user data that can be used for a variety of analytical and business intelligence purposes.
