Re: v13 / sunset / mcc 20xx

Also, one last question. Long ago, an adgroup id was unique only to its parent campaign id. (or at least this is what google said) Is this still the case? -tim On Aug 5, 10:25 am, timp wrote: > Actually now I have two questions: > > 1.  The "caveat" information for "CampaignChangeData" > > Can

Re: v13 / sunset / mcc 20xx

Actually now I have two questions: 1. The "caveat" information for "CampaignChangeData" Can you give a rough estimate of a result size which would cause a failure? 2. Other size related failures: A. Let's say I requested all the campaign IDs for an account. (using campaign service, where se

Re: v13 / sunset / mcc 20xx

Thanks! Do you have any "caveat" information for "CampaignChangeData" Are there any conditions where it will refuse to return results? (data set too large?) I guess if this happens I can revert to iterating over all items, but I thought I would ask. -tim On Aug 3, 4:24 pm, David Torres wrote:

Re: v13 / sunset / mcc 20xx

Hi Tim, Unfortunately most of the answers to your questions are not available yet, the report generation will be asynchronous more or less how it is described here . Best, -David Torres - AdWords API Team -- =~=~=~=~=

v13 / sunset / mcc 20xx

Hey there, I seem to be tasked with moving from v13 to 20xx. 1. When will cross client mcc be ready? 2. Do you intend to keep the report generation time to be the duration of a get request? 3. Will there be any arbitrary restrictions on this mcc cc report? (size / number of accounts / etc)