How many different ways are there to pull back the current values of
AdParams? I realize I can do this with a small piece of code, but
was wondering if there are other ways, such as pulling reports, or
spot checking values in the AdWords GUI?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
I really like the ability to view the values for param1 and param2 in
the keyword details in the Sandbox Account Viewer Utility. Could this
feature be added to an upcoming release?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsap
OK, I got it. Code is almost correct. Just needed PAUSED and Not
PAUSE
On Feb 12, 10:51 am, Joe_Rocket wrote:
> I have an update function that updates Keyword Max CPC and Status.
> The Max CPC updates fine. But the Keyword Status does not change.
> Can you see anything wrong with
I have an update function that updates Keyword Max CPC and Status.
The Max CPC updates fine. But the Keyword Status does not change.
Can you see anything wrong with this code? Thanks in advance.
/**
*
* @param int $belongsToAdGroupId
* @param int $kwid
OK, I've manage to migrate our application from v13 to v2009. We've
got some serious speed issues in keyword generation with the Bulk
Processing. So I'm wondering if someone could take a look and tell me
if I could construct the Bulk jobs more efficiently. Thanks.
Test Campaign Run
-
I've been successful at the basic of v2009, but have not been able to
run a bulk job. In experimenting with the sample
PerformBulkMutateJobs.php code, I could never get it to complete. It
would always have a run on status of PENDING. Now, I've managed to
get the error "TOO MANY JOBS IN QUEUE".
I do some heavy campaign generation using Apility. I always test the
result of creation operations by checking for NULL values as suggested
by the Apility documentation, and then process any faults found on the
Apility Fault stack. Usually things go fairly well and we are able to
log the faults w
