OK
thanks for the update
pete
--
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-...@googlegroups.com.
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com.
For
In v13, you can get the information even though you supplied a normal
account.
Is the v200909 implementation currently flawed, meaning that it should
work in the same conditions as v13?
Or is the current implementation a result of new restrictions (i.e.
only MCC account of token is allowed)?
In
Hi all
I'm using .net api v13, amd try to create placement performance report
with this selected columns
[PlacementDomain,PlacementSpecialCategory,SiteTargeted,CPC,CTR,Clicks,Cost,Impressions,CustomerName]
,
report type is ContentPlacement and the
aggregationTypes[Account,Domain,Summary]
but
Hello everyone,
I'm working porting a v13 application to v2009 and I'm having problems
because I keep getting a QUOTA_EXCEEDED error with the number of
requests per minute (RequestsPerMinute).
I didn't found any information about this in Google's documentation.
With v13 I didn't have any issue
I'm trying to develop a small app using the API but when I try to run
it I always come across the following error:
Not agreed to latest AdWords Api terms and conditions.
I've logged in with my MCC account to check if there was any alert on
the new Terms Conditions but there's nothing. I've also
Hi,
I am having an active Ad and i want to change the text of that Ad. Is
there any ways to do that. Please help me and thanks in Advance.
-Vamsi
--
You received this message because you are subscribed to the Google Groups
AdWords API Forum group.
To post to this group, send email to
Hi,
I'm not clear on what mutually exclusive options you are referring to,
but you can validate your requests using the validateOnly header:
http://adwordsapi.blogspot.com/2009/12/discover-v2009-validateonly-header.html
Best,
- Eric
On Feb 3, 9:10 am, ipsita rout afixi.ips...@gmail.com
Hi Kyle,
It looks like this error was caused because the keyword you were
trying to add was already present in the ad group. This type of error
is normally handled automatically, and I'll work with the core
engineering team to resolve this issue.
Best,
- Eric Koleda, AdWords API Team
On Feb 3,
Hi Kyle,
It looks like this error was caused because the keyword you were
trying to add was already present in the ad group. This type of error
is normally handled automatically, and I'll work with the core
engineering team to resolve this issue.
Best,
- Eric Koleda, AdWords API Team
On Feb 3,
Hi Ajit,
The Keyword.text field can only accept one value. Instead what you
should do is create multiple Keyword objects and pass them into the
field RelatedToKeywordSearchParameter.keywords as an array.
Best,
- Eric Koleda, AdWords API Team
On Feb 3, 12:59 pm, Ajit ajitscor...@gmail.com
Hi Eric,
Thanks for the response. Is there anyway I can check for this before
I make the request (like using the validate only flag in the request
header)? If not do you know or have an ETA on a solution for the
engineering team? Also what are you defining as handled
automatically of the
Hi Shane,
Thanks for expanding on your question. The cause of confusion here is
that the match type of the input keywords has no effect on the results
generated. You can see this in the web interface and even the old v13
KeywordToolService.
Best,
- Eric
On Feb 3, 4:50 pm, Shane
Hi Ajit,
This is a known issue and the core engineering team is aware of the
problem. Unfortunately I don't have any estimates on when it will be
resolved.
Best,
- Eric Koleda, AdWords API Team
On Feb 3, 5:08 pm, Ajit ajitscor...@gmail.com wrote:
Hello team
I am pulling some keyword
Hi,
The current behavior is the intended behavior, and we will work on
updating the documentation to reflect this restriction.
Best,
- Eric
On Feb 4, 4:58 am, Zweitze zwei...@gmail.com wrote:
In v13, you can get the information even though you supplied a normal
account.
Is the v200909
Hi Kyle,
I don't believe the validateOnly header would catch this particular
issue. Unfortunately I don't have an ETA on a solution, but for the
mean time I would try to avoid re-adding keywords to an ad group.
Normally an ADD operation like this would be treated like a SET
operation if the
Hi Eric,
I can see why the match type for the input keywords might be ignored
but why is the KeywordMatchTypeSearchParameter (which is set to
PHRASE) being ignored when the input dataset is small ( 4) ?
Shane
On Feb 4, 7:42 am, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hi Shane,
Hello team
I am trying to get suggested keyword for a give website. it is working
fine.. but I only want BROAD match type..
is there a way to specify matchtype = BROAD for
RelatedToUrlSearchParameter method.
following is my code:
related_search =
Hi,
I am migrating Google API v13 to v2009.
I updated the getAllCampaigns method and successfully ran it for an
account.
Everything else seems to be fine but I am not sure about the network
type.
The value returned by campaign.stats.network is 'ALL' which I assume
means both content and search
I'm working on a project that uses the v13 api and I'm trying to
migrate to v200909. The v13 call to getKeywordsFromSite returns
SiteKeywords with the fields advertiserCompetitionScale,
lastMonthSearchVolume, and avgSearchVolume. Using the v200909
TargetingIdeaService, I'm able to get a bunch of
19 matches
Mail list logo
