These features are not provided simply because they are convenient; there is a reason for each one. And those reasons have a consistent axis, which is the philosophy of the platform.
Even if Google AdWords offers a high degree of operational flexibility and excellent functions, if your account is not designed and its functions are not utilized correctly, it may malfunction and not perform to its full potential .
This time, I would like to look at some of AdWords' often-overlooked features , understand their significance, and give you some tips on how to create a better account.
*This article is titled "Learning from Features
and Specifications" and will be delivered in two parts. This time we will focus on "features", and next time we will focus on "specifications".>>Download the document set (service documents and case studies) to learn about Ollie's
Table of Contents [ Hide ]
If you have experience using AdWords, you may be aware of this function (whether you actively use it or not).
When you display "Search terms" in the Keywords tab, the "Included, Excluded" flags for keywords are displayed as required fields by default . (Hereinafter referred to as "Keyword flags")
%e7%ae%a1%e7%90%86%e7%94%bb%e9%9d%a2%e3%82%ad%e3%83%a3%e3%83%97%e3%83%81%e3 %83%a3
This function literally allows you to check whether the search query that actually generated an ad impression or click is set as a keyword . If the query is set as a keyword, it will be displayed as "Added", and if not, it will be displayed as "None". (If it is excluded, it will be displayed as "Excluded".)
Expected usage scenarios include:
Use the filter function to extract only search queries that have converted and register them as keywords in bulk.
Use the filter function to display only queries with no flag, check the ones you think are good queries, and register them all at once as keywords.
It is a great feature that allows you to easily add good queries as keywords.
However, a common misconception about this function is that the "Added or Not" flag does not refer to information for the entire account, but rather to whether or not a string identical to the query exists as a keyword within the "ad group" to which the keyword that generated the query belongs .
In other words, in order to effectively use this function, it is assumed that " ad groups are composed of keywords as a "keyword axis ." If this assumption is not met, the keyword flagging function will become extremely difficult to use. It is no exaggeration to say that it will no longer be usable.
Why is this the case? Let me explain the situation with an example below.
