Almost everyone running Google Ads campaigns these days is concerned about the lack of data available regarding Performance Max campaigns.
4 of the main concerns are:
1. Performance metrics split by networks
2. Performance of Text, Image and Video assets
3. Product performance
4. Placements performance
Currently advertisers can’t even guess where their budget is going when it comes to Performance Max campaigns. They wonder what is the cost per shopping part in PMax, the cost per Display in Pmax, cost per video in PMax, and so on.
Now, with Dolnai PMax tool you will be able to see and analyze Performance Max budget allocation by network.
But not only that...you will see other performance metrics of your PMax campaigns such as:
Moreover, you will see the evolution of these channels:
Advertisers work with a mixture of assets in their asset groups (Images, Texts, Videos) and need to know their performance metrics. Nevertheless, Google does not provide much information.
Until now, it’s been impossible for advertisers to, i.e., tell which variations of images (with or without text) work best. But not anymore…
Now with Dolnai PMax tool you will have performance data regarding your assets in Performance Max campaigns.
Read more on our post about Performance of Text, Image and Video assets in PMax campaigns.
Although Google Ads shows some reports regarding product performance, it is necessary the use of other tools to analyze and optimize product performance.
Dolnai PMax tool provides you with a "Product Radiography", clustering your products in different buckets based on their performance:
Read more on our post about PMax Product Performance.
In this section you will find the Display and Video placements where your ads showed, with performance metrics for each of those placements.
Although in the PMax context it is not allowed to exclude placements at the campaign-level, it is always a good practice to analyze your PMax placements in order to exclude at the account-level those that are draining your budget.
Keep reading our post about:
