Adding ConfigCat source documentation #6596
Conversation
Hello @tcgilbert , many thanks for your review. I will fix these mistakes, but i'll be OOO this week, so probably i will do it early next week. |
Co-authored-by: Thomas Gilbert <[email protected]>
|
|
||
| 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. | ||
|
|
||
| The default behavior is for ConfigCat to pass the user object's identifier property used during the feature flag evaluation as the userId or sending the ConfigCat User's ID who made the changes as the userId. |
There was a problem hiding this comment.
What happens when there is no user object identifier? Is the default to send ConfigCat User's IDas the Segment userId in it's place?
Will there every be a situation where nothing is used as the Segment userId, and you send an event with only with anonymousId? If so what is used for anonymousId
There was a problem hiding this comment.
There are two ways how we are sending data to Segment. They are totally different and they have nothing in common related to User ID handling.
The feature flag evaluated event is sent from ConfigCat's customer's application with a code snippet we provide in our documentation. The user object's identifier is our customer's application's user's identifier. If that is not provided we are sending an empty string. However it seems to be pointless at first glance, but in ConfigCat terminology it totally makes sense to not have an user object during feature flag evaluation. But we would like to send events in this case too. We don't send explicitly anything in this case as anonymusId, but the code snippets we provide are using Segment's SDKs. Is it handled there? What is your suggestion in this case? Should we generate a GUID and send it as the anonymusid? These applications don't know anything about ConfigCat User's ID.
The feature flag changed event is sent from ConfigCat's backend and we always provide the userId there (ConfigCat User's ID).
Co-authored-by: Thomas Gilbert <[email protected]>
Co-authored-by: Thomas Gilbert <[email protected]>
Thank you very much for your review! |
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
Adding the ConfigCat source documentation to be able to publish our integration.
Merge timing
ASAP once approved