Once Partner Revenue Measurement is tagging correctly, you have a number: the AWS consumption your solution drives. The next question from anyone in sales is which deals it came from.
That is what a Revenue Attribution ID does. It is also where expectations need managing, because the answer does not come back to you.
What a RAID does
PRM already measures your product’s influenced consumption. A Revenue Attribution ID associates that already-measured revenue with a specific deal. AWS maps the revenue to the deal based on inputs you provide.
The important property: no changes to your existing resource tags or user agent strings are required. This is a layer on top of the measurement you already have, not a second implementation. If your tagging is in place, adding deal association is configuration rather than engineering.
What you supply
Either an Offer ID or an Opportunity ID — the unique identifier of the deal you are associating.
There is a shortcut worth knowing. If an AWS Marketplace offer is already linked to an ACE opportunity, you only need to provide the Offer ID and AWS automatically attributes the revenue to the associated opportunity.
That rewards a discipline you should have anyway: linking marketplace offers to ACE opportunities when you create them. Teams that treat the marketplace offer and the co-sell opportunity as two unrelated records end up doing this mapping by hand later.
The limitation to state up front
Read this before you promise a report to your CRO.
Deal level revenue attribution remains internal to AWS. Google’s own documentation says so plainly. You provide the association; AWS uses it. You do not get a per-deal consumption breakdown back.
So a RAID is not a reporting feature for you. It improves what the AWS account team can see about your contribution to their customer. That is valuable — it is arguably the whole point of co-sell — but it is not a dashboard.
Set this expectation internally before someone builds a forecast around a number that does not exist on your side.
Why it still matters
Because the AWS seller’s view of your contribution is what drives their behaviour.
The mechanism, as always, is quota credit. An AWS account manager who can see that your solution drove measurable consumption in their account has a reason to bring you into the next conversation. One who cannot see it has only your assertion. That is the difference between co-sell as a documented contribution and co-sell as an anecdote in a partner review.
Connecting consumption to a named opportunity is what makes the claim legible to the person whose compensation depends on it.
Service coverage keeps expanding
PRM’s reach has been widening through the year, which is worth re-checking periodically rather than assuming your initial assessment still holds.
Two changes this year:
- April — PRM added support for the AWS Marketplace Metering Service for certain Marketplace products, closing a gap for metered SaaS.
- August 31 — the user agent string capability expanded to additional AWS services, with revenue attribution for those services available from September 1.
That second one landed two weeks ago. If you previously concluded that part of your footprint was not attributable because the services involved were not supported, that conclusion may now be out of date. Worth a review rather than a rebuild.
Where this sits in the sequence
The full chain, for anyone arriving at this mid-way:
- Migrate to Partner Central in the AWS Console
- Connect your accounts via Subsidiary Account Connections
- Deploy tagging and verify coverage
- Associate deals with Revenue Attribution IDs
Steps 1 to 3 are not optional prerequisites you can shortcut — the dependency between them is where most partners stalled this year. Step 4 only makes sense once step 3 is producing a real number.
CloudX’s PRM tagging covers step 3, including coverage reporting per account so you know what the number actually represents before you start attributing it to deals. Co-sell covers the motion that the attribution is ultimately feeding.
The summary
A Revenue Attribution ID connects measured consumption to a named deal using an Offer ID or Opportunity ID, requires no change to your tagging, and keeps the per-deal breakdown inside AWS. Link your marketplace offers to ACE opportunities as a habit and the association becomes nearly automatic. Do not promise anyone a deal-level revenue report, because that is not what this produces.