This issue describes the logic to integrate with the API schema as defined in this issue. We will also need to make sure that we send the Flagsmith-User-Agent header to satisfy the requirement in this issue.

This logic should behave the same as the current flag analytics integration which batches evaluations and sends them to the /analytics/flags/ endpoint, but it should send the data to the new endpoint based on the schema defined in the previously referenced issue.

The current flag analytics logic, however, only cares about feature_name, and the count of evaluations, but there is a version of the code here that also enriches the analytics data with the identifier and whether the flag was enabled.

Notes:

• When we release the JS client, I think this should be a separate tag for internal use only