Use Amazon Redshift as a destination - Kameleoon Documentation

If your analysts query experiment data in Amazon Redshift, the exposure data in Kameleoon sits apart from the rest of your warehouse. When you turn on Use Amazon Redshift as a destination, Kameleoon writes each experiment exposure event to a table in your Redshift database, so your analysts can work with it there.

Data warehouse integrations are available as a premium add-on for the Web Experimentation and Feature Experimentation module. For more information, contact your Customer Success Manager.

To send events, first enable the Amazon Redshift integration for your project. Then activate Use Amazon Redshift as a destination to send events to your Amazon Redshift account whenever one of your Kameleoon experiments exposes visitors.

Two tables. The first shows Kameleoon sending exposure events to Redshift. The second marks web experiments, web personalizations and feature experiments as supported.

Activate Amazon Redshift as a destination

To activate Amazon Redshift as a destination:

Click Use Amazon Redshift as a destination.
Choose your cluster type: Provisioned or Serverless.

Use Amazon Redshift as a destination settings, with the Redshift cluster type options and the Redshift cluster ID, S3 bucket name, Redshift AWS region and Database fields.

Enter the fields for your cluster type:
- For the Provisioned cluster type:
  - Redshift cluster ID: the identifier of your Amazon Redshift cluster
  - S3 bucket name: the full name of an Amazon S3 bucket for staging streamed events before periodic bulk loading into Redshift. The policy attached to the AWS role you set up in Setting up Amazon Redshift must grant access to this bucket
  - Redshift AWS region: the region code where your Redshift cluster resides. Find this code in your AWS console. Example: eu-west-1
  - Database: the name of the Redshift database where Kameleoon writes the events
- For the Serverless cluster type:
  - Redshift serverless workgroup: your workgroup’s name
  - S3 bucket name: the full name of an Amazon S3 bucket for staging streamed events before periodic bulk loading into Redshift. The policy attached to the AWS role you set up in Setting up Amazon Redshift must grant access to this bucket
  - Redshift AWS region: the region code where your Redshift workgroup resides. Find this code in your AWS console. Example: eu-west-1
  - Database: the name of the Redshift database where Kameleoon writes the events
Click Confirm.
Click Validate to save your changes.

What Use Amazon Redshift as a destination does

Kameleoon first stages the events in the S3 bucket you provide, then loads them into Redshift periodically. Kameleoon stores events in the kameleoon_events schema of your {database} database, the Redshift database that you enter in the destination settings. You create this schema during setup, and the Kameleoon IAM role needs write access to it. Kameleoon saves the data 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
 );

Kameleoon reads the custom_visitor_id from the Cross Device Reconciliation custom data, if you set it.

Integrations

​Activate Amazon Redshift as a destination

​What Use Amazon Redshift as a destination does

Activate Amazon Redshift as a destination

What Use Amazon Redshift as a destination does