About the asset report for responsive search ads

The asset report lists each asset used in your responsive search ads and allows you to compare assets within your responsive search ad. You’ll be able to see which assets to replace and which assets are most effective to enhance the performance of your ads.

Before you begin

You’ll need to create a responsive search ad to see your asset report. Learn more about responsive search ads.

You can also view your asset reports at the cross-campaign level.

How it works

To see your asset report for responsive search ads, follow these instructions:

  1. Sign in to your Google Ads account.
  2. Click Ads & extensions from the page menu.
  3. Find and click on the relevant responsive search ad.
  4. Click View asset details at the bottom of the relevant responsive search ad.

This should bring you to the assets report for your responsive search ad.

What you’ll find in your assets report

Filters and views

If you have a long list of assets, you can filter by enabled state, asset type and performance. You can also download the report.


In the 'Assets' column, you’ll see the content of each asset.

Asset type

The 'Asset type' column defines how each asset is used. Here are the kinds of assets you may find:

  • Headline
  • Description

Position pinning

The 'Position pinning' column shows you where your headlines and descriptions appear when pinned to specific positions. Learn more about pinning headlines and descriptions to specific positions


The 'Impressions' column displays how often your asset is shown. An impression is counted each time your asset is shown in an ad on a search result page or other sites on the Google Network. Learn more about impressions


The 'Performance' column helps you compare how your assets perform relative to other assets of the same type within your responsive search ad. This will allow you to prioritise optimising your responsive search ads by adding or replacing assets based on their performance. Learn how to create effective responsive search ads

Note: Responsive search ads usually need around 5,000 impressions in the 'Google Search: Top' segment over 30 days to display a rating in the 'Performance' column. Learn more about the 'Top vs Other' segment

Once you add an asset, a 'Learning' rating will appear while the system reviews that asset’s performance relative to other assets in the responsive search ad. After your asset has enough traffic, it can receive a 'Low', 'Good' or 'Best' performance rating.

Note: Changing the date range does not affect the 'Performance' column. The rating shown is always the current rating.

You should replace 'Low'-performing assets, keep 'Good'-performing assets and use 'Best'-performing assets to help you improve your ads.

Tip: Add as many assets as you can. The more assets you add to your responsive search ad, the more options there are for creating high-performing ads.

You can edit your assets by selecting the edit icon  above your assets report.

You can review the different performance ratings below:

Asset performance rating Description
Pending This asset doesn’t have any performance information yet. A performance rating for this asset will be shown once enough information has been collected.
Learning Information needed to rate this asset is still being collected. A performance rating for this asset will be shown once enough information has been collected.
Low This asset is one of your lowest-performing assets of its type. Replacing this asset could improve your overall ad performance.
Good This asset is performing well relative to other assets of this type. Keep this asset and try adding more assets to improve the performance of your ad.
Best This asset is one of your best-performing assets of its type. Adding more assets like this one could increase your chances for better ad performance.
'--' (Unrated) A dash ('--') means that a performance rating is not available for this asset. This can happen if there are not enough assets of the same type to compare it against, the asset isn’t active or if the asset doesn't get enough traffic to determine its relative performance.

Related links

Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue