Payments and reports

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.

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

To ensure that your payments are properly configured, work with your Cloud Partner Engineer.


To get access to monthly reporting, you must send your Partner Engineer a list of email addresses that should be given access to the monthly reports. The reports are shared from a Google Drive folder, so the email addresses must be Google accounts.

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 gibyte-hours, depending on your pricing model.

  • Currency: The currency in which the following three columns are measured.

  • Charges: Costs associated with the usage.

  • 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, but 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 this is not the customer's GCP billing ID, but it 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.

If you need your report to be broken down by these dimensions, contact your Partner Engineer.

Customer Insights reports

For customers who are using business accounts, 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 Daylight Time (PDT), 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:

Field Description
date The date for the usage reports.
company The customer's company name. If the customer is using a personal account, the company name is excluded from the report.
domain 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.
external_account_id A unique ID generated for the billing account associated with the customer's project.
account_id The billing account associated with the customer.
country The customer's country.
state_or_province The customer's state or province, if applicable.
postal_code The customer's postal code, if applicable. If the customer is using a personal account, the postal code is excluded from the report.
sku_id 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.
sku_description 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)".
usage The quantity of resources used by the customer.
unit The metric that usage is measured as, such as hour or gibibyte hour.
currency The currency that you are paid in.
charges The charges that the customer was billed for during the period.
due_vendor The amount that you receive for the usage.
trial_use Trial credits (if applicable) that the customer consumed.
num_vms The number of VMs that the customer has deployed the solution on.
num_cpus 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.
ram_mb The size of the RAM in the customer's deployment.
num_gpus The number of GPUs in the customer's deployment.
gpu_types A space-separated list of the GPU types in the customer's deployment. For example, the value "NVIDIA_TESLA_P4 none NVIDIA_TESLA_P100" indicates that at least one VM used an NVIDIA® Tesla® P4, at least one used a P100 GPU, and at least one VM had no GPU. For a list of GPUs available on Compute Engine, see GPUs on Compute Engine.
earliest The earliest date (UTC) on which the customer created a VM that was live during the reporting period.
latest The latest date (UTC) on which the customer created a VM that was live during the reporting period.

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.
  • The URL for the privacy policy that governs how you use the fields that you collect. We recommend being explicit about what you use the information for, so that customers are comfortable sharing their information.
  • How frequently you want the report generated.

The fields and privacy policy are used to create a consent form. When customers start deploying a VM solution, they can grant or deny their consent to share their information with you.

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 shown as 2019-03-14T00:00:00+00:00.

For customers who opted in, the report contains the following information:

Field Description
Name The customer's name.
Email 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 FR.
Address The customer's address.
Phone The customer's phone number.
هل كانت هذه الصفحة مفيدة؟ يرجى تقييم أدائنا:

إرسال تعليقات حول...