Wingify Campaign Data Export: Schema and Reporting Guide

#Overview

Wingify provides integrations with data warehousing platforms that allow you to automatically export your Wingify campaign data to your respective platforms for deeper analysis and reporting. These integrations enable your analytics team to run advanced queries, create custom dashboards, and unify experimentation data with other critical business datasets for richer insights.

Once you enable the integration with your data warehousing platform, two datasets are created:

• {customer_defined_dataset} and
• {customer_defined_dataset}_internal

Each dataset contains tables that store visitor, metrics, and attributes data, providing you with comprehensive insights into user behavior, campaign performance, and conversion tracking.

This article lists the tables included in each dataset and explains their structure, column definitions, and reporting use cases.

#Datasets and Tables

Dataset: {customer_defined_dataset}

This dataset contains four core tables:

• vwo_${account_id}_visitors
• vwo_${account_id}_metrics
• vwo_${account_id}_attributes
• vwo_${account_id}_summary

These tables store detailed information about visitors, their interactions with your campaigns, and associated attributes.

#Table: vwo_${account_id}_visitors

This table records visitor information, including their location, device, browser details, and campaign-specific data.

Use Case: Use this table to track user activity, analyze regional performance, or understand the devices and browsers used to access your campaigns.

#Table: vwo_${account_id}_metrics

This table stores conversion data and other metrics recorded for Wingify campaigns.

Use Case: Use this table to calculate conversion rates, analyze the impact of different campaign variations, or track key performance metrics across campaigns.

#Table: vwo_${account_id}_attributes

This table logs user attributes associated with Wingify campaigns.

Use Case: Use this table to segment your audience based on user attributes and analyze how specific attributes impact user behavior or campaign success.

#Table: vwo_${account_id}_summary

This table provides a summary of key campaign metrics and attributes.

Use Case: Use this table when you need a structured overview of campaign components or when building entity-level reports.

#Dataset: {customer_defined_dataset}_internal

This internal dataset contains the raw data and metadata for all tables, providing full transparency into the data ingestion process. You can build SQL queries to join the visitors, metrics, and attributes tables based on common columns such as _uuid and campaign_id to get a holistic view of user interactions, conversions, and more. For example, you can build a query that answers: How did mobile users from organic traffic convert for Variation B in Campaign X?

By using these tables and joining them with common identifiers, your teams can achieve a holistic, in-depth view of user behavior and campaign performance.

#Supported Integrations

Wingify supports integrations with data warehousing platforms like BigQuery and Snowflake. For more information, refer to these integration articles:

• Integrate Wingify with Snowflake
• Integrate Wingify with BigQuery

#Need more help?

For more information or further assistance, contact Wingify Support.