Maybe we’re setting up the callback incorrectly, but based on this doc - we need to set up the experiment result call back at client initiation. If that’s the case, how do we identify which GB response belongs to which request? The unique identifier is a uuid, but the same uuid can be part of multiple GB requests
rhythmic-agency-4145
04/03/2024, 3:39 PM
cc @adorable-cpu-56223
rhythmic-agency-4145
04/03/2024, 3:42 PM
in order to emit events based on these experiments / send downstream, we need more identifier data related to that particular request. That seems to be getting lost in the callback.
I hope I’m explaining this well, it’s a lot to understand without context haha
a
adorable-cpu-56223
04/03/2024, 3:43 PM
We are actually using the TrackingCallback, but maybe we need to feed the TrackingCallback into the ExperimentCallback? 🤷
We just need a way to get other data points within either the TrackingCallback or the ExperimentCallback so that we can do further analysis downstream, and currently if we only split based on uuid, that’s the only available datapoint within the TrackingCallback and is not very useful for analysis