[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-11。"],[],[],null,["# Monitoring your product's analytics\n\nAfter your product launches, you can monitor its analytics to gain insight into\nhow users find, deploy, and run your products, including how your marketing\ncampaigns are performing.\n\nTo see your analytics:\n\n1. Open Producer Portal.\n2. Click **Analytics** .\n The direct link to the Analytics page is\n `https://console.cloud.google.com/producer-portal/analytics`.\n\n [Go to Analytics](https://console.cloud.google.com/producer-portal/analytics)\n\nIn the analytics dashboard, you can see a view of your data,\ngrouped by specific time intervals, and filter the data by the types of\nproducts you sell. You can also view the data organized by how users found your\nproduct, such as through a Google search, a direct link, or a specific\nreferral URL.\n\nThe following sections describe the metrics that you can track in your\ndashboard.\n| **Note:** The data shown in the analytics dashboard count unique users per day, not the number of clicks. If you're using other systems to track visitors to your product, such as tracking clicks on Google Ads, you might see differences between the number of users shown on your Cloud Marketplace analytics dashboard and the dashboards for other systems.\n\nTo filter your data by time, product type, or acquisition channel, open the\nfilter panel at the right of the page. If the panel isn't open, click\n**Show panel** on the top-right.\n\nAnalyzing your conversion rate\n------------------------------\n\nThe **Conversion rate** tab shows how users move through the journey\nof discovering your products, and then deploying them or signing up, as\napplicable. Use these insights to develop and refine your go-to-market\ninitiatives for more effective acquisitions.\n\nYou can group your data by solution or by *channel* , which shows how users found\nyour product's Cloud Marketplace listing. Each channel is a combination\nof the *source* of the traffic, such as a social networking site,\nand the *medium* , such as a paid ad. For example, the\n`Paid Social` channel indicates traffic that came from a paid\nad on a major social network.\n| **Note:** If a channel led to five or fewer deployments or sign-ups, its data is grouped in the `Other` channel, to protect users' identities.\n\nLearn about the [default channels in Google Analytics](https://support.google.com/analytics/answer/3297892).\n| **Note:** This report might not contain information on all of your customers who've deployed your VM product if [command-line deployment](/marketplace/docs/deploy-through-cli) is enabled for the product. You don't see information in this report for on customers who deploy your product through the command-line interface (CLI).\n\nIf you use custom URLs for marketing campaigns, use the following sections\nto create your campaigns and add them for tracking.\n\nCreating and tracking marketing campaigns\n-----------------------------------------\n\nYou can track conversion rates for your marketing campaigns by creating\ncustom URLs that direct users to your product's page. The custom URLs typically\nhave `utm_` parameters that identify how users learned about your product.\n\nFor example, if you promoted your product in a winter newsletter to your\ncontacts, the custom URL might look similar to the following: \n\n https://console.cloud.google.com/marketplace/your-organization/solution-name?utm_source=newsletter&utm_medium=email&utm_campaign=winter_promo\n\nAfter you create a custom URL, you can add the parameters from the URL to\nProducer Portal. When you select **Campaigns**, only traffic attributable to\nthe campaign names you added is shown in the chart.\n\n### Creating custom URLs for campaigns\n\nTo create custom campaign URLs, set the `utm_campaign` query parameter on your\nproduct URLs to a unique value. For example, the following URL sets the\n`utm_campaign` query parameter to `ft_spring_promo` for the Google Click to\nDeploy Wordpress product: \n\n https://console.cloud.google.com/marketplace/details/click-to-deploy-images/wordpress?utm_campaign=ft_spring_promo\n\nYou can also filter and group by `utm_source` and `utm_medium` values, as long\nas there is also a `utm_campaign` value defined.\n\nYou can use a tool like\n[Google Analytics Campaign URL Builder](https://ga-dev-tools.appspot.com/campaign-url-builder/)\nto create your campaign URLs.\n\nFor background information on custom campaigns, and the types of `utm_`\nparameters you can use, see the [Google Analytics documentation](https://support.google.com/analytics/answer/1033863).\nYour products dashboard shows the source, medium, and name of your campaign.\n\n### Tracking campaigns in Producer Portal\n\nIn Producer Portal, use **Add campaigns** to add your campaigns for tracking.\nEnter the `utm_campaign` values used in your URLs --- just the `utm_campaign`\nvalue, not the whole query string from the URL. For example, if you had the\nfollowing URL: \n\n https://console.cloud.google.com/marketplace/\u003cvar translate=\"no\"\u003eyour-organization\u003c/var\u003e/\u003cvar translate=\"no\"\u003esolution-name\u003c/var\u003e?utm_source=newsletter&utm_medium=email&utm_campaign=winter_promo\n\nYou would enter `winter_promo` as the campaign ID.\n\nThe portal can track multiple `utm_campaign` values, up to a limit of 2000. Use\n**Manage campaigns** to rename or remove existing campaign values. Campaigns are\nsaved, and are loaded every time you visit Analytics.\n\nThere are two special campaign values that are always available: `(not set)` and\n`(other)`. `(not set)` means traffic with no campaign associated. `(other)` is\nfor campaigns with fewer than 5 users with success events.\n\nAfter you add your campaigns, Producer Portal displays funnel analytics for\nall historical visits to your product's details page that include the specified\n`utm_campaign` values. This means you can retrieve for prior marketing\ncampaigns, not just new ones.\n\nYou can filter your campaign data by the following dimensions:\n\n- **Source** : the origin of your traffic, for example, a search engine\n (google.com), a domain (example.com), or the way you distribute the campaign\n information, such as `monthly_newsletter`.\n\n [Learn about traffic sources](https://support.google.com/analytics/answer/1033173).\n- **Medium** : the category of the source, such as organic search, web referral,\n paid media, etc. When you set up a custom campaign URL, you can create a\n custom medium as part of the URL using the `utm_medium` parameter.\n\n#### Attributing funnel steps to campaign names\n\nIn most cases, a user follows your custom link, views a product, configures\nthat product, and then deploys the product in a single session. In these\ncases, the campaign name is clearly attributable to each stage.\n\nIn other cases, a customer might follow the custom link to your listing, but\nmight exit before deploying. If that customer returns later and deploys, that\ndeployment is counted for the campaign that originally brought the customer to\nyour Cloud Marketplace listing. If the customer visited your listing\nmultiple times from different campaigns before finally returning in a session\nwith no campaigns, the earliest campaign where they signed up for or deployed\nthe product is credited.\n\nUsage metrics for virtual machines (VMs)\n----------------------------------------\n\nIf you offer virtual machine (VM) products on Cloud Marketplace, the\n**Usage metrics** tab shows how much your products are being used over time.\nThis information can be useful in answering questions like \"Is my product's\nusage increasing?\", or to estimate your monthly revenue for fixed-rate or\nusage-based billing models. You can group the data by products, deployment zones, and\nmachine types.\n\nYou can view your product's usage by *VM hours* and *core hours*. Each metric\nis aggregated for a 24-hour period. For example, if you have 48 VM hours on a\ngiven day, that means an average of 2 VMs were running your product during\nthat day. Similarly, if you have 144 core hours on a given day, there might\nhave been 10 customers running g1-small VMs (0.6 cores each), or one customer\nrunning a 6-core custom VM.\n\nActive users for VMs\n--------------------\n\nIf you offer VM-based products, the **Active users** tab shows how many users\nare running your product over time.\n\nThis information can be used to answer questions like \"How many active\ndeployments of my software are there?\" and \"What size of VM do most of my users\nrun?\"\n\nYou can view the active users by *projects* , or by *billing accounts*. VMs are\ndeployed to Google Cloud projects, but some customers might have multiple\nprojects linked to a single billing account."]]
