Use Snowflake as a destination - Kameleoon Documentation

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

Kameleoon can write campaign events into a Snowflake database that you own, where you query them with SQL. The integration writes experiment exposure events by default, and it can also write conversion and custom data events, each to its own table in the KAMELEOON_EVENTS schema that you create in Setting up Snowflake. Use key-pair authentication for this direction, because the destination doesn’t support password authentication.

Activate Snowflake as a destination

Once you have enabled the Snowflake integration for your project, you can activate Use Snowflake as a destination to start writing Kameleoon events to Snowflake.

To do so, follow these steps:

In the selected project’s configuration, click Use Snowflake as a destination to expand it.

The Use Snowflake as a destination section, expanded, with a Warehouse field and a Confirm button.

Enter the name of the warehouse that you granted to the Kameleoon role in Setting up Snowflake in the Warehouse field, then click Confirm.
Click Validate to save and apply your configuration settings.

What “Use Snowflake as a destination” does

Enabling Use Snowflake as a destination starts writing Kameleoon events to Snowflake. Kameleoon saves the events in the KAMELEOON_EVENTS schema of the KAMELEOON database that you created, with table creation rights granted to the Kameleoon role during setup. Each of the three event types has its own table.

Kameleoon stores experiment exposure events in kameleoon_experiment_event:

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 stores conversion events in kameleoon_conversion_event:

CREATE TABLE kameleoon_conversion_event (
    nonce                   BIGINT PRIMARY KEY,  -- unique identifier of the event
    timestamp               BIGINT,              -- timestamp in millis of the event
    visitor_code            VARCHAR,             -- Kameleoon visitor identifier
    custom_visitor_id       VARCHAR,             -- visitor identifier used by your company
    goal_id                 BIGINT,              -- Kameleoon id of the goal
    revenue                 FLOAT,               -- revenue associated with the conversion
    negative                BOOLEAN,             -- negative set to true means that this event cancels a previous conversion
    metadata_id_to_values   OBJECT               -- map of goal metadata IDs to the set of values taken by that metadata
);

Kameleoon stores custom data events in kameleoon_custom_data_event:

CREATE TABLE kameleoon_custom_data_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
    index                   BIGINT,              -- index of the custom data
    count_by_value          OBJECT,              -- map of values taken by this custom data to their occurrence counts
    overwrite               BOOLEAN,             -- whether the value overwrites previous data within the session
    mapping_identifier      BOOLEAN              -- whether the index uses a mapping identifier
);

Kameleoon populates the custom_visitor_id field from the Cross Device Reconciliation custom data, if you set it. Kameleoon enables experiment exposure events by default. Conversion and custom data event collection is new and may change. You can’t turn it on in the UI. To activate it, contact the Kameleoon support team.

Limits of the destination

Kameleoon only inserts rows into these tables. It doesn’t read changes back from Snowflake, so a correction or deletion in your tables doesn’t change the events that Kameleoon has already written. Kameleoon doesn’t monitor the schema of these tables. If you change a column, Kameleoon doesn’t detect the change.

Integrations

​Activate Snowflake as a destination

​What “Use Snowflake as a destination” does

​Limits of the destination

Activate Snowflake as a destination

What “Use Snowflake as a destination” does

Limits of the destination