For all of your products on Google Cloud Marketplace, you can receive the following reports:
- Usage and disbursement report: Contains details of your software's usage, and the amount to be paid to you.
- Customer insights report: Contains information about who your customers are, and how they are using your software, such as the number of VMs that they deployed your products on.
- Lead generation report (for VM products): Contains contact information for customers who have consented to share this information with you.
- SKU migration report: If we migrate your product SKUs to a different Cloud Billing service or structure, this report tells you about the migration so you can adapt your report ingestion.
Your reports are delivered to a Google Drive folder, a Cloud Storage bucket, or both. For steps to set up your report destinations, see Setting up reports.
If you want to set up how you receive payments, see Receiving payments from Google.
Setting up reports
To receive your Google Cloud Marketplace reports, set up a Drive folder, a Cloud Storage bucket, or both. You must be an owner for the destination you choose. For example, if you use a Drive folder, your Google Cloud account must have the Can organize, add & edit permission for the folder.
Your reports can be stored in a shared Drive location, a Cloud Storage
bucket, or both. When you set up your destination, your Google Workspace or
Cloud Storage administrator must ensure that the destinations can
be shared with the
- Learn about sharing permissions for Drive.
- Learn about restricting access to Google Cloud resources by domain.
When you add your report destination, the following accounts are added as editors or storage object administrators, as applicable:
firstname.lastname@example.org account, which uploads reports to the bucket.
email@example.comGoogle group, to debug and troubleshoot issues that you might have with reports.
After you have set up a location to store the reports, set up how they are delivered by following these steps:
In Partner Portal, open the Partner Reports page. The direct link to the page is:
Your public project ID is the ID of the project that hosts the components of your solution. You create this project when you sign up to become a partner.
To add a report destination, click Add destination.
Under Destination location, select whether you want to send reports to a Drive folder or a Cloud Storage bucket.
Click Browse and select a folder or bucket, as applicable.
Select the types of report to save in that destination. You can send each type of report to as many destinations as you need.
If you want additional levels of detail in usage reports, select one or more of these options:
- Separate customer usage by location: Splits your usage and disbursement report by the customers' locations.
- Separate customer usage by billing account: Splits your usage and disbursement report by the customers' Cloud Billing accounts.
For information on what is included in the report, see Usage and disbursement reports.
If you want to set up more destinations, repeat these steps.
To save your changes, click Save. You must agree to give the Google Cloud Marketplace accounts access to your report destinations.
Usage and disbursement report
By the tenth business day of every month, a report is generated in the destination that you set up, with the details of usage and revenue for the previous month.
The monthly report contains the following content. For any questions about the report, contact your Partner Engineer.
SKU: The description of the Google Cloud Marketplace product.
Google Entity: The Google corporation that received the payment from customers. The payment to you originates from this corporation.
Resource: The resource on which the product ran. The resource shown depends on your pricing model.
Usage: The quantity of the resource used by deployments of the product.
Units: The unit in which the Usage column is measured, such as hours, core-hours, or gibibyte-hours, depending on your pricing model.
Currency: The currency in which the following three columns are measured.
Charges: The customer's costs for using your product.
Trial Use: The cost that was covered by product trial credits.
Due Partner: Payment accrued for you, calculated as
(Charges - Trial Use) * revenue share.
Payment Type: The means by which you will receive the disbursement: If it is
old, you receive payments from one or more of Google US / Ireland / Singapore to your US-based bank account. If it is
new, you receive a single payment to your local bank account.
Withheld: If a Google Cloud customer's billing account is placed on due to lack of payment, Google withholds disbursements until the account is back in good standing.
This column tells you how much we would have paid you if we had collected it from the customer.
When the billing account is back in good standing, we release the withheld funds in the next payment to you. If it never returns to good standing, we abandon the withheld funds.
Released: If Google had withheld funds, this column shows the total of the funds that are now released to you because the customer's billing account is back in good standing.
Abandoned: If Google had withheld funds, this column shows the total of the funds abandoned because we have terminated the billing account.
Probation Start: The first day that Google started withholding funds, in
YYYY-MM-DDformat. If we are releasing or abandoning funds, this may be in an earlier month. If the account is still on probation, this is the first day in the current month where we withheld funds (which may not be the very first day on which we withheld funds).
Probation End: The last day that Google withheld funds, in
YYYY-MM-DDformat. The day after this, the account either returned to good standing, or we closed it. If this is blank, then the account is still on probation.
Refund Start: The first day that Google refunded a customer's usage, in YYYY-MM-DD format.
Refund End: The last day that Google refunded a customer's usage, in YYYY-MM-DD format.
Refund Balance Deducted This Month: The amount of payout Google subtracted during the month related to a customer refund.
Refund Balance Outstanding: If the offset related to a customer's refund is greater than the month's payout, the remaining offset due to your future payout.
Refund Reason: The reason why a customer received the refund.
By default, the report is broken down by the SKU, Google Entity, and Resource. When you set up your reports, you can choose these additional breakdowns:
By account: This adds Account Id and Insights Account Id columns to the report, which show a billing ID for the customer. You can use this ID to track metrics like churn or trial conversions. The Account Id isn't the customer's Google Cloud billing ID, but it is specific to the customer's billing account. There are two forms of obscured account ID in the report because, for historical reasons, the two reports use different algorithms to obscure the actual account ID. Use the Insights Account ID to match the disbursement to the information about the customer in the Customer insights report.
By location: This adds a Location column to the report, which holds the country code for the customer's location. If the customer is in the US or Canada, the column includes the country and state code.
Customer insights report
You also get a daily and monthly Customer insights report, which includes information about who your customers are, and how they are using your software. The daily reports are generated on a two-day delay, based on Pacific Time (PT). For example, the report for June 1st is generated on June 3rd. The monthly report is generated on the 2nd calendar day of the subsequent month.
If customers use their personal accounts, some of their information is excluded from the report.
The sales report contains the following information, starting from July 13, 2018:
||The date for the usage reports.|
||The customer's company name. If the customer is using a personal account, the company name is excluded from the report.|
||The email domain for the organization's billing administrator. If there are multiple administrators associated with the billing account, the domain in the report is the domain used by most of the administrators. If the customer is using a personal account, the domain is excluded from the report.|
||The Insights account ID, generated for the billing account associated with the customer's project.|
||The billing account associated with the customer.|
||The customer's country.|
||The customer's state or province, if applicable.|
||The customer's postal code, if applicable. If the customer is using a personal account, the postal code is excluded from the report.|
||The SKU that the customer was charged for. Depending on how a product is configured, a single deployment might have multiple SKU IDs. For example, one SKU might cover the cost of using CPUs in the deployment, and another SKU ID might cover the cost of using RAM.|
||The description of the SKU. For example, if a customer deployed a WordPress product that charged by the number of CPU cores, the SKU description is similar to "Licensing Fee for Click to Deploy Wordpress (CPU cost)".|
||The quantity of resources used by the customer.|
||The metric that usage is measured as, such as hour or gibibyte hour.|
||The currency that you are paid in.|
||The charges that the customer was billed for during the period.|
||The amount that you receive for the usage.|
||Trial credits (if applicable) that the customer consumed.|
||The number of VMs that the customer has deployed the product on.|
||The number of vCPU cores in the customer's deployment. If the number is a fraction, it indicates that the customer chose a shared vCPU.|
||The size of the RAM in the customer's deployment.|
||The number of GPUs in the customer's deployment.|
||A space-separated list of the GPU types in the customer's deployment. For
example, the value "
||The earliest date (UTC) on which the customer created a VM that was live during the reporting period.|
||The latest date (UTC) on which the customer created a VM that was live during the reporting period.|
||A space-separated list of new and total counts per [machine type](/compute/docs/machine-types).
For example, the value "
||If you've generated revenue from a private offer, the quote ID associated with the offer's solution and billing account.|
||If you've generated revenue from a private offer, the email address of the offer creator.|
||If you've generated revenue from a private offer, an optional internal note for the offer. You can use internal notes to tag offers for additional processing, such as tracking the revenue and/or usage data they generate. You specify the internal note when you create the offer.|
||The means by which you will receive the
disbursement: If it is
||If a Google Cloud customer's billing account is placed on due to lack of payment, Google withholds disbursements until the account is back in good standing. This column tells you how much we would have paid you if we had collected it from the customer. When the billing account is back in good standing, we release the withheld funds in the next payment to you. If it never returns to good standing, we abandon the withheld funds.|
||If Google had withheld funds, this column shows the total of the funds that are now released to you because the customer's billing account is back in good standing.|
||If Google had withheld funds, this column shows total of the funds are abandoned because we have terminated the billing account.|
||The first day that Google started withholding funds,
||The last day that Google withheld funds, in
Lead generation report
For VM solutions, you can get the Lead generation report that includes customers' information, such as email addresses and phone numbers. You can choose to receive this report daily, weekly, biweekly, or monthly.
If you want to collect this information, contact your Partner Engineer with the following information:
For each product, the fields that you want in your report.
How frequently you want the report generated.
The first row of the report holds the number of customers who opted out of
sharing their information, and the start and end times that are covered by the
report. All customer answers in the report are from between the two times.
The times are based on the UTC timezone, and are in the ISO format
YYYY-MM-DDTHH:MM:SS+00:00. For example, midnight UTC on March 14, 2019 is
For customers who opted in, the report contains the following information:
|Name||The customer's name.|
|The customer's email address.|
|Company||The customer's company name. If the customer isn't associated with a company, the value is `_none_`.|
|Country Code||The two-letter country code for the customer's country. For example,
the two-letter code for France is
|Address||The customer's address.|
|Phone||The customer's phone number.|
SKU migration report
Occasionally, we might shift how the SKUs related to your products are
structured, or the product in Cloud Billing where they appear. When
this happens, we create a file
sku-migration-report.csv in the same location
as your Customer Insights reports. Each SKU is located in a service, which has
a 3-part hexadecimal ID of the form
0123-4567-89AB. In addition, each SKU
has its own 3-part hexadecimal ID that is independent of the service ID, and
unique across all services. You see the SKU ID in the
in the Customer insights report.
The SKU migration report is updated each day. If you have a retention policy on your Cloud Storage bucket, the update is delayed until the retention period has passed. The report contains the following information:
||The SKU ID of the old SKU.|
||The SKU ID of the SKU that has replaced the original. If this is blank, then the original SKU has no replacement.|
||The service ID in which the replacement SKU is defined. If this is blank, then the original SKU has no replacement.|
||Your company name.|
||The name of the product that the SKU relates to.|
||A human-readable name of the source SKU (this is not how it appears on the customer invoice).|
||A human-readable name of the SKU that has replaced the original. If this is blank, then the original SKU has no replacement.|