Each month, Google computes how much customers paid for your solution and what Google owes you. We generate a report to allow you to reconcile the payments you receive from us, and to give you information about how your customers are deploying your solution.
Setting up payments
If this is the first time you're integrating with GCP Marketplace, you must enroll for partner payments after your partner agreement is in place, and you're ready to launch. Use the Partner Enrollment Form to enroll for payments. You need your tax ID and bank account information to complete the enrollment.
Payments for a month of usage are made 4 business days before the end of the month. You receive payments from up to three Google corporate entities, depending on the entity that received the money from the customer. For questions related to payments, contact firstname.lastname@example.org.
To ensure that your payments are properly configured, work with your Cloud Partner Engineer.
Reports that you receive
For all of your solutions on GCP 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 the software, such as the number of VMs that they deployed your solutions on.
- Lead generation report (for VM solutions): Contains contact information for customers who have consented to share this information with you.
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.
Usage and disbursement reports
By the tenth business day of every month, a report is generated in the shared Google Drive folder, 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 GCP Marketplace solution.
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 solution ran. The resource shown depends on your pricing model.
Usage: The quantity of the resource used by deployments of the solution.
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 solution.
Trial Use: The cost that was covered by solution trial credits.
Due Partner: Payment accrued for you. This is calculated as
(Charges - Trial Use) * revenue share.
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 an Account ID column to the report, which shows a billing ID for the customer. You can use this ID to track churn, trial conversions, and so on. Note that this is not the customer's Google Cloud billing ID, but is specific to the customer's billing account.
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 reports
You also get a daily and monthly Customer Insights report, which includes information about how customers are using your software. The daily reports are for two days before, based on Pacific Time (PT), and 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.|
||A unique 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 solution 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 solution 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 solution 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 created a custom quote, the quote associated with the solution and billing account.|
||The email address of the quote creator.|
Lead Generation report
For VM solutions, you can get a Lead Generation report that includes customers' information, such as email addresses, phone numbers, and so on. 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 solution, 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.|
Setting up reporting
To receive your GCP Marketplace reports, set up a Google 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 Google Drive location, a Cloud Storage bucket, or both. When you add your report destination, the following accounts are added as editors or storage object administrators, as applicable:
email@example.com account, which uploads reports to the bucket.
firstname.lastname@example.orgGoogle group, to debug and troubleshoot issues that you might have with reports.
After you have set up a location to store the reports, use the following steps to set up how your reports are delivered:
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, which you create when you set up the dev environment for your Kubernetes app, VM solution, or managed service.
To add a report destination, click Add destination.
Under Destination location, select whether you want to send reports to a Google Drive folder or 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 detailed usage and disbursement reports, select one or more of the following 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 customers' 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 GCP Marketplace accounts access to your report destinations.