Change Details

To make it easier for developers to log exposure in their all user traffic experiments, it should be possible to log exposure server-side but have the event sent client-side. For privacy reasons, all-user-traffic experiments – which use edge uniques for enrollment – can only use the JS SDK for data collection. An experiment which uses the PHP SDK for feature toggling needs a way of triggering exposure logging on the client side. Without this functionality, developers would be required to write client-side instrumentation that detects whether the current page view has any elements (or lack of elements!) that are only there (or only not there!) because user is enrolled in the experiment. ## Acceptance criteria [ ] A call to `Experiment#logExposure()` in the PHP SDK results in an exposure event sent by the JS SDK, regardless of enrollment authority / identifier type used for enrollment.

NOTE: This task was previously called "Enable queueing of client-side events from server-side" For logged-in user experiments, calling `Experiment#logExposure()` in PHP right before calling `Experiment#isAssignedGroup()` in the same server-side execution context is straightforward. For privacy reasons, all-user-traffic experiments – which use edge uniques for enrollment – can only use the JS SDK for data collection. An experiment which uses the PHP SDK for feature toggling needs a way of triggering exposure logging on the client side. We need a way to log experiment's exposure on the client-side such that there are no false positives (logging exposure when there was no exposure) or false negatives (not logging exposure when there was exposure). ## Acceptance criteria NOTE: AC previously said "A call to `Experiment#logExposure()` in the PHP SDK results in an exposure event sent by the JS SDK, regardless of enrollment authority / identifier type used for enrollment." [ ] A way to trigger `Experiment#logExposure()` client-side from server-side using some mechanism

To make it easier for developers to log exposure in their all user trafficNOTE: This task was previously called "Enable queueing of client-side events from server-side" For logged-in user experiments, it should be possible to log exposure server-side but have the event sent client-sidecalling `Experiment#logExposure()` in PHP right before calling `Experiment#isAssignedGroup()` in the same server-side execution context is straightforward. For privacy reasons, all-user-traffic experiments – which use edge uniques for enrollment – can only use the JS SDK for data collection. An experiment which uses the PHP SDK for feature toggling needs a way of triggering exposure logging on the client side. Without this functionality, developers would be required to write client-side instrumentation that detects whether the current page view has any elements (or lack of elements!) that are only there (or only not there!) because user is enrolled in the experimente need a way to log experiment's exposure on the client-side such that there are no false positives (logging exposure when there was no exposure) or false negatives (not logging exposure when there was exposure). ## Acceptance criteria [ ] ANOTE: AC previously said "A call to `Experiment#logExposure()` in the PHP SDK results in an exposure event sent by the JS SDK, regardless of enrollment authority / identifier type used for enrollment." [ ] A way to trigger `Experiment#logExposure()` client-side from server-side using some mechanism