AWS introduces user agent string for partner revenue measurement
AWS has launched the Partner Revenue Measurement User Agent string, enabling partners to track AWS service consumption driven by their solutions, providing insights into revenue impact and consumption patterns.
AWS has announced the general availability of its new Partner Revenue Measurement User Agent string. This feature enables AWS Partners to track the consumption of AWS services driven by their solutions through the use of AWS APIs and SDKs. With this tool, Partners can gain a clearer understanding of the revenue impact their solutions have on AWS and analyze consumption patterns of their products.
The User Agent string feature allows Partners to include a unique product code from their AWS Marketplace listing as a user agent. This facilitates the quantification and measurement of the AWS revenue impact of their solutions across specific services. Partners are now able to incorporate a user agent in the format APN_1.1/pc_<AWS Marketplace product-code>$ into their applications. This enables the measurement of AWS service consumption by solution across both partner-managed and customer-managed accounts.
Additionally, Partners can configure their SDKs by setting an environment variable or adjusting a setting in their AWS shared configuration file to automatically apply the User Agent string to all AWS service calls. This approach supports automated deployments across various AWS SDKs, including Python, Node.js, Java, and Kotlin. It captures attribution for API-driven workloads and complements the existing capabilities of Partner Revenue Measurement, such as Resource Tagging and AWS Marketplace Metering integration.
The Partner Revenue Measurement feature is now available in all commercial regions. For more information on the implementation of the User Agent string, interested parties can refer to the User Agent implementation guide and the list of supported services. Those looking to explore the broader capabilities of Partner Revenue Measurement can consult the onboarding guide for further details.