Definition and overview of Census integration

Census is a powerful data integration tool that seamlessly connects with Statsig, enabling you to ingest data from various sources supported by Census directly into your Statsig account. By leveraging the Census integration, you can effortlessly sync data from your preferred platforms and databases, eliminating the need for manual data transfer or complex ETL processes.

Once the Census integration is set up, Statsig automatically includes all events received from Census in your Pulse and Experiment results. This means that any relevant data points captured by Census will be instantly available for analysis within Statsig, providing you with a comprehensive view of your feature gates and experiments.

The Census integration empowers you to make data-driven decisions by combining the insights from multiple sources in one centralized location. Whether you're tracking user behavior, monitoring key metrics, or evaluating the performance of your experiments, the Census integration ensures that all the necessary data is readily accessible within Statsig.

Configuring and using the Census integration

Setting up the integration

Enabling the Census integration in Statsig is straightforward. First, copy your Statsig "Server Secret Key" from the API Keys tab in the console. Then, create a new destination in Census and select Statsig from the options. Paste your secret key and click save.

Next, create a Sync to the Statsig destination. Finally, enable the Census integration on the Statsig Integrations page.

When mapping Census data to Statsig events, certain fields are required:

• userID: User ID

• eventName: Event Name

• timestamp: Timestamp

• value: Value

Other fields will be included in the event metadata.

Custom ID mapping

The Census integration supports mapping arbitrary fields to Statsig Custom IDs. This is done in the "Map Identifier" section of the Census panel on the Statsig Integrations page.

It's crucial that the input Event Field matches the exact spelling from the original Census event. This ensures proper mapping of custom identifiers between the two systems.

By configuring the Census integration and setting up custom ID mapping, you can seamlessly ingest data from various sources into Statsig. This enables powerful analytics and experimentation capabilities across your entire data pipeline.

Best practices and additional resources

Optimizing Census integration

Efficient data syncing requires careful mapping of fields between Census and Statsig. Ensure the required fields (userID, eventName, timestamp, value) are correctly mapped. Additional fields can be included in the metadata section for richer event data.

When moving from proof-of-concept to production, consider setting up custom ID mapping. This allows you to map arbitrary fields from Census events to Statsig Custom IDs. Verify the input Event Field matches the exact spelling in the original Census event.

Further reading

For more details on setting up the Census integration, refer to the Statsig documentation. This covers the step-by-step process of enabling the integration and configuring incoming events.

The Census documentation provides guidance on creating a new Statsig destination. It also covers the specifics of sync configuration and field mapping for seamless data transfer.