AWS Revenue Measurement adds identity and SaaS account tagging
The service now supports two additional ways for partners to attribute AWS consumption to their products. One uses an IAM identity, while the other assigns eligible consumption in a tagged account to a SaaS product.
Partners can associate measurement with the IAM user or role used by their solution, without changing code.1
For eligible SaaS products, AWS assigns all eligible consumption in a tagged account to that product.1
An account used for Account Tagging must be reserved for a single product; partners sharing accounts can use other listed methods.1
Story
Two new tagging options change how partners can measure AWS revenueAWS Revenue Measurement now supports Identity Tagging and Account Tagging for SaaS Products, adding two options for partners measuring product-related AWS consumption.1 Identity Tagging associates measurement with the IAM user or role used by a partner’s solution, rather than requiring tags on individual resources.1 Account Tagging instead uses the AWS account hosting a SaaS solution as the basis for measuring revenue impact.1 For that account-based method, AWS attributes all eligible consumption within each tagged account to the product associated with it.1 The change therefore adds identity-level and account-level approaches alongside existing resource-level and other attribution methods, without replacing those methods.1
With Identity Tagging, partners can tag the IAM user or role their solution uses instead of applying tags to each individual resource.1 AWS says this approach makes attribution simpler and can be used without making code changes.1 The method is not exclusive: it works alongside Resource Tagging, the User Agent string, and SaaS Account Tagging.1 This lets partners use identity-based attribution while retaining those other supported methods as part of the measurement options.1 The announcement describes the identity method in terms of the user or role used by a solution, not individual resources.1
Account Tagging measures a SaaS product’s revenue impact by tagging the AWS account where the solution is hosted, rather than its individual resources.1 AWS assigns all eligible AWS consumption in each tagged account to the product linked to that account.1 The method is available for products that have a SaaS listing on AWS Marketplace.1 Each account used for this tagging approach must be dedicated to a single product.1 The account-level attribution rule therefore covers eligible consumption in a tagged account, rather than only consumption associated with separately tagged resources.1
The dedicated-account condition matters when a partner operates more than one product: an account tagged through this method cannot be shared across products.1 Partners whose products share an account can continue measuring with Resource Tagging, the User Agent string, or Identity Tagging.1 Those alternatives preserve options for shared-account arrangements, while Account Tagging is restricted to an account devoted to one product.1 The announcement identifies the methods partners can use in that shared-account situation, rather than extending Account Tagging to shared accounts.1 The stated account rule is specific: every account tagged for SaaS Account Tagging must serve one product.1
The available methods differ in what the partner tags: an identity, an AWS account, or individual resources, with the User Agent string also supported.1 Identity Tagging uses the IAM user or role behind a solution, while Account Tagging uses the account hosting that solution.1 Resource Tagging remains an option, and both the User Agent string and SaaS Account Tagging are listed alongside Identity Tagging.1 For products sharing an account, AWS specifically names Resource Tagging, the User Agent string, and Identity Tagging as continuing choices.1 These distinctions describe the attribution basis and account constraint; the announcement provides no figures comparing the methods’ measured results.1
AWS Revenue Measurement is generally available across all commercial regions, according to the AWS announcement.1 That availability statement concerns the measurement service, while the release separately describes the requirements for the two new tagging options.1 For Account Tagging, a product needs a SaaS listing on AWS Marketplace and a tagged account dedicated to that product.1 Identity Tagging is described as using the solution’s IAM user or role and requiring no code changes.1 The announcement does not give a numerical measure of adoption, revenue attributed, or the size of the change in partner results.1
AWS Revenue Measurement was previously known as Partner Revenue Measurement, so the current service name differs from its earlier name.1 The announcement presents the new identity and SaaS account capabilities under the AWS Revenue Measurement name.1 Its description combines the service’s commercial-region availability with the new tagging options and the rules governing account attribution.1 The named options allow attribution through an IAM identity or, for qualifying SaaS products, through a dedicated AWS account.1 The older service name is the only prior-state detail given; the announcement does not quantify any earlier measurement coverage or performance.1
For partners, the practical choice described is between the tagging basis that fits their solution and the conditions attached to that basis.1 Identity Tagging avoids tagging individual resources by using the IAM identity employed by the solution, and it needs no code changes.1 Account Tagging avoids resource-by-resource attribution by assigning eligible account consumption to a product, but the account must be product-specific.1 The account option also applies only to products with a SaaS listing on AWS Marketplace.1 Partners with products sharing an account retain the named alternatives of Resource Tagging, the User Agent string, and Identity Tagging.1
Taken together, the release adds two ways to associate AWS consumption with a partner product while keeping existing attribution methods in use.1 Identity Tagging associates measurement with the IAM user or role used by a solution, and AWS says it requires no code changes.1 Account Tagging assigns all eligible consumption in a tagged account to a SaaS product, subject to Marketplace listing and single-product account requirements.1 Where products share an account, AWS identifies other methods partners can continue using rather than Account Tagging.1 The service is generally available in all commercial regions and carries the current name AWS Revenue Measurement, formerly Partner Revenue Measurement.1
Structure
Who is connected to whom- 1AWS Revenue Measurement
- uses →Fact
- serves →Fact
History
How it came to this- PreviouslyEarlier service nameAWS Revenue Measurement was formerly called Partner Revenue Measurement.
- NowNew tagging options announcedAWS Revenue Measurement adds Identity Tagging and Account Tagging for SaaS products.
- NowIdentity and account tagging New attribution options in AWS Revenue Measurement
Impact
Spreading outward, level by level- Level 1Attribution method
Identity Tagging uses the IAM user or role associated with a solution and does not require code changes.1
Fact - Level 2Product-level measurement
Account Tagging attributes all eligible consumption in a tagged account to its product, and is available to products with a SaaS listing on AWS Marketplace.1
Fact - Level 3Account-sharing constraint
A tagged account must serve a single product. Partners with products sharing an account can continue with Resource Tagging, the User Agent string, or Identity Tagging.1
Fact - Level 4Partner measurement choices
The added options may let partners select an attribution basis that fits their setup while retaining existing methods.
Analysis
Sources
What each source supportsWritten by AI from the sources listed below: every fact was checked word for word against its source, and inference is marked apart. How we write