Webpage Target

[Yasin]

Hi,

Webpage targeting is a required feature in RMF (https://developers.google.com/adwords/api/docs/requirements).Web page criterion is Beta and I didn't get webpage criterion with

AdGroupCriterion and Criterion Performance report.How I get this criterion properties.

Thanks...

[Josh Radcliff (AdWords API Team)]

Hi,

The reporting documentation is incorrect.  The WEBPAGE value for CriteriaType is out of Beta.  Thanks for pointing this out - I'll have the documentation updated.

In terms of AdGroupCriterion, you can get back the WebpageParameter by including "Parameter" in your Selector fields.  The Webpage criterion objects will be returned with "CriteriaType" of "WEBPAGE".

Cheers,

Josh, AdWords API Team

[Kevin]

It also appears that AdGroupCriterionService.get() doesn't return webpage criteria unless I include "CriteriaType" of "WEBPAGE" as one of the predicates in the selector.

[Josh Radcliff (AdWords API Team)]

Hi,

Thanks for pointing this out.  I confirmed the behavior you described and I'm looking into it.  I'll post an update once I have more information.

Cheers,

Josh, AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi,

A fix is in and AdGroupCriterionService now returns Webpage criteria without a filter on CriteriaType = WEBPAGE.  Thanks again for bringing this to our attention.

Best,

Josh, AdWords API Team

[Georg Döhring]

Am Montag, 13. Januar 2014 20:08:46 UTC+1 schrieb Josh Radcliff (AdWords API Team):

Hi,

A fix is in and AdGroupCriterionService now returns Webpage criteria without a filter on CriteriaType = WEBPAGE.  Thanks again for bringing this to our attention.

Best,

Josh, AdWords API Team

The Problem seems to linger in the CRITERION_PERFORMANCE_REPORT. When I request a report without any predicate, the WEBPAGE criteria are missing from the report.

 

When I include new Predicate('CriteriaType', 'EQUALS', 'WEBPAGE'); then the criteria are returned, but the criteriaType is missing. Also the "Dynamic Ad target" values are filled with strange Symbols. This is an exemplary row:

Campaign ID

Ad group ID

Keyword ID

Criteria Type

Is negative

Keyword/Placement state

Keyword / Placement

First page CPC

Max. CPC

Max CPC source

Max. CPM

Quality score

Keyword/Placement destination URL

Max. CPA%

Approval Status

Top of page CPC

Dynamic ad target

xxxxxx

xxxxxxx

xxxxxx

--

false

enabled

--

0.00

0.05

ad groups

--

5

--

approved

0.00

���#� � *

Can you please verify this issue?

[Josh Radcliff (AdWords API Team)]

Hi,

We are aware of the strange symbols for Dynamic ad target (field name Parameter) and are working on it.

Regarding the filtering question, since this behavior is in reporting it's a separate issue from the original AdGroupCriterionService question.  It's also a tricky one, because the Criterion Performance Report is a single attribution report, so AdWords attributes each impression to the "best" criterion according to the rules described in the documentation.  If the WEBPAGE criteria in question do not have any impressions or AdWords decides to attribute those impressions to a different criterion, then the WEBPAGE criteria will not appear on the report.  When you then filter to only pick up WEBPAGE criteria, that may have an impact on how the attribution rules apply.

Could you send the customer ID and report definitions only to me by clicking Reply to author?  I'd like to look into your particular use case so I can provide you with a complete answer.

Cheers,

Josh, AdWords API Team

[Abin Thottakara]

Hi,

Has the Dynamic ad target issue been resolved yet? CriteriaType and Criteria are missing are missing for dynamic ad targets.

Thanks!

[Josh Radcliff (AdWords API Team)]

Hi,

The issue with garbled text in reports has not been resolved yet. I'll post here as soon as I have an update.

Thanks,

Josh, AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi,

I'm glad to report that the issue with strange symbols in Parameter for dynamic targets has been fixed. Please let me know if you still see any problems with the text returned.

Thanks,

Josh, AdWords API Team