We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When recording events triggered by user interactions, include the user's client metadata in the event metadata.
Currently, client metadata is sent to the server using HTTP headers. They follow the format of Inventory-Client-* (I think).
Inventory-Client-*
Consider storing all HTTP heading data matching that pattern. This will allow some clients to opt-in extra data (like OS version, for example)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When recording events triggered by user interactions, include the user's client metadata in the event metadata.
Currently, client metadata is sent to the server using HTTP headers. They follow the format of
Inventory-Client-*
(I think).Consider storing all HTTP heading data matching that pattern. This will allow some clients to opt-in extra data (like OS version, for example)
The text was updated successfully, but these errors were encountered: