You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are reaching out to request the addition of a feature to the amp-analytics component. Specifically, we would like to inquire if it would be possible to include support for adding a custom Authorization parameter in the request headers originating from amp-analytics.
This feature is particularly important for our internal tracking system, which relies on authorization tokens to ensure secure and authenticated data collection. Adding this functionality would allow us to seamlessly integrate amp-analytics with our existing infrastructure.
If this functionality is not currently supported, would it be possible to consider implementing it in a future release? We believe it would greatly enhance the flexibility of amp-analytics for developers working with secured data sources.
Thank you for considering this request. Please let us know if additional details or use cases would be helpful.
Alternatives Considered
If the feature request will be refused can you give us any advice to reach our goal without adding the header param? we are trying to do this without the definition of a proxy that add the authorization param
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Description
We are reaching out to request the addition of a feature to the amp-analytics component. Specifically, we would like to inquire if it would be possible to include support for adding a custom Authorization parameter in the request headers originating from amp-analytics.
This feature is particularly important for our internal tracking system, which relies on authorization tokens to ensure secure and authenticated data collection. Adding this functionality would allow us to seamlessly integrate amp-analytics with our existing infrastructure.
If this functionality is not currently supported, would it be possible to consider implementing it in a future release? We believe it would greatly enhance the flexibility of amp-analytics for developers working with secured data sources.
Thank you for considering this request. Please let us know if additional details or use cases would be helpful.
Alternatives Considered
If the feature request will be refused can you give us any advice to reach our goal without adding the header param? we are trying to do this without the definition of a proxy that add the authorization param
Additional Context
No response
The text was updated successfully, but these errors were encountered: