ConfigCat Source

ConfigCat is a feature flag and remote configuration service that empowers developers to control and customize the functionality of their applications. With ConfigCat, you can easily toggle features on and off, alter their settings, and roll out updates to specific users or groups. Targeting is supported through attributes, percentage-based rollouts, and segmentation. ConfigCat is available for all major programming languages and frameworks.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by ConfigCat. For any issues with the source, contact their Support team.

Getting started

1. From your workspace’s Sources catalog page click Add Source.
2. Search for “ConfigCat” in the Sources Catalog, select ConfigCat, and click Add Source.

3. On the next screen, give the Source a name.

   • The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. ConfigCat_Prod, ConfigCat_Staging, ConfigCat_Dev).
4. Click Add Source to save your settings.
5. Copy the Write key from the Segment UI.

Sending feature flag change events from ConfigCat to Twilio Segment

1. Open the integrations tab on the ConfigCat Dashboard.
2. Click on Twilio Segment’s CONNECT button and set the Twilio Segment Write Key acquired while adding the ConfigCat source in Segment.
3. OPTIONAL - Set the proper server of your Twilio Segment account.
4. You’re all set. Go ahead and make some changes on your feature flags then check your events in Twilio Segment.

Sending feature flag evaluation analytics from ConfigCat to Twilio Segment

1. Log in to the ConfigCat Dashboard and copy the SDK Key for your Config in the specific Environment.
2. In your application’s code, Configure SDKs::
   • ConfigCat SDK: Initialize with your ConfigCat SDK key.
   • Segment SDK: Set up with the Segment Write Key acquired while adding the ConfigCat source in Segment.
3. Integrate Feature Flag Evaluations:
   • During the initialization of the ConfigCat SDK, subscribe to the flagEvaluated hook.
   • Send feature flag evaluation data to Segment using the Feature Flag Evaluated event name. Include the following parameters:
     • feature_flag_key: the feature flag’s key
     • value: the evaluated feature flag’s value or Variation ID
     • variation_id (optional): the evaluated feature flag’s Variation ID
     • user (optional): the user object used during feature flag evaluation.
   • You can find code samples in the ConfigCat Segment Source documentation.

Stream

ConfigCat uses our stream Source component to send Segment event data. It uses a track method to send data to Segment. These events are then available in any destination that accepts events, and available in a schema in your data warehouse, so you can query using SQL.

In the “Feature Flag Evaluation” event, the default behavior for ConfigCat is to use the user-object’s identifier property as the Segment userId. If no identifier is present, the event will be sent with a randomly generated anonymousId.

For “Feature Flag Changed” events, the ConfigCat User’s ID who made the changes will be sent as the Segment userId.

Events

The table below lists events that ConfigCat sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.

Event Properties

The tables below list the properties included in the events listed above.

Feature Flag Evaluated event

Feature Flag Changed event

Adding Destinations

Now that your Source is set up, you can connect it with Destinations.

Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.

If there are any issues with how the events are arriving to Segment, contact the ConfigCat support team.