Hi,

When adding keywords via the AdWords API, you should set the Keyword.text 
<https://developers.google.com/adwords/api/docs/reference/v201609/AdGroupCriterionService.Keyword#text>
 attribute 
to the keyword *without* any of the special match type symbols. Those 
symbols exist as a convenience for users of the AdWords user interface, but 
in the AdWords API you explicitly set the match type to avoid any ambiguity.

In your experiment, I would expect the keywords added via the API to have 
match type *BROAD* before you edited them in the user interface. You could 
confirm this by retrieving the keywords via AdGroupCriterionService 
<https://developers.google.com/adwords/api/docs/reference/v201609/AdGroupCriterionService>
 or 
by running a KEYWORDS_PERFORMANCE_REPORT 
<https://developers.google.com/adwords/api/docs/appendix/reports/keywords-performance-report>
 and 
including the *KeywordMatchType* field. I suspect that when you started 
editing the keywords in the user interface, the user interface symbol 
processing kicked in and switched the keywords to *EXACT*.

Cheers,
Josh, AdWords API Team

On Tuesday, October 18, 2016 at 1:35:06 PM UTC-4, Evan wrote:
>
>
> We've built an ads editor which contains a series of keyword inputs. 
> Upon submission, each input value is sanitized and will only include valid 
> characters. We then explicitly set *match type* via the API. 
>
>  
>
> I was wondering what would happen if the user input itself contained* match 
> type* symbols that conflicted with our explicit setting. 
>
>  
>
> For example, if I set,
>
>  
>
> keyword.text = "[baseball cap]"; 
> keyword.matchType = "BROAD";
>
>
> would this configuration *BROAD*ly match the text "[baseball cap]" (with 
> brackets) or would it *EXACT*ly match the text "baseball cap". Or would 
> it ignore the brackets and *BROAD*ly match "baseball cap".
>
>  
>
> In order to test what would happen, I created a campaign through the API 
> to experiment. My AdGroup contained each of the symbol variations of 
> "baseball cap". However, each keyword had its *match type* explicitly set 
> to *BROAD*. 
>
>
> When I opened the campaign in the Adwords GUI, I could confirm that the 
> text retained its inputted symbols and had been designated as *BROAD **match 
> type* (even if the symbols were denoting *PHRASE* or *EXACT*).  
>
>  
>
> For example, he UI had the following values for our input text "[baseball 
> cap]":
>
>  
>
> Text: [baseball cap]            Match Type: BROAD
>
>  
>
>  However, when I gave focus to the text input, the UI's validator would 
> take over and update *match type* to *EXACT* (as long as the brackets 
> remained). 
>
>  
>
> Should we therefore be checking user input and using it to set match type 
> (according to the detected symbology) on our end? Or will any overrides be 
> handled by the API despite what I saw initially in the GUI?
>
>  
>
> Thanks!
>
>  
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/787b7f58-3c2e-4bb8-9b1d-cde6087659c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Do symbols in key... Evan
    • Re: Do symbo... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum

Reply via email to