Hi Pete,
For the benefit of the forum I thought I would review the solution.
The problem we found was that you were explicitly setting the
keywordStatuses field of the job. Although you were setting it to
every possible status, since the content network doesn't have any
keyword data those results
Eric, I'll try the crossClient change.
I'm here at NYC Hackday ... I thought I heard your name mentioned that
you were present ... I'm in the green flannel shirt near the front if
you want to try and hash this out in person.
Thanks
Pete
On Jan 14, 11:39 am, AdWords API Advisor
wrote:
> Hi Pete,
Hi Pete,
We've seen a couple cases in the past where include certain columns in
reports leads to strange side effects, so it may be worth trying your
report with only the required columns and building it up from there.
Also, I took another look at your request, and you currently are
specifying cr
Eric,
I've tried grabbing Content Network data a few times before and have
had success off and on ... an anomaly I've experienced in the past is
the raw XML report adding columns I didn't request ... I've tried the
reports in the UI and I can get the Content Network data ... the only
thing I can
Hi Pete,
Is this new behavior or simply your first crack at Content Network
reports? It may make sense to try various reports in the UI first, to
ensure you have the right settings. Once you have that working you
can try to schedule the same reports in the API, and if there are
problems we can m
