Hi Steve,
Here are the rules about id uniqueness to go by when joining reports:
CampaignId is globally unique
AdGroupId is globally unique
AdGroupId + Criterion Id (keyword id, placement id, etc.) is globally
unique. KeywordId alone isn't.
AdGroupId + Ad Id (keyword id, placement id, etc.) is gl
Oops - should add that *definitely* you need a minimum of adgroupid and
keywordid -- I definitely get back entries which are different in this way.
Not sure if campaignid is necessary, but I'm using it to be safe. On
the other hand, while I have no examples of keyword id reuse across
acco
I'm likewise using the accountid, campaignid, adgroupid, and keywordid - I
think that's probably best if you want to be safe.
Also noticing a small percentage of missing keywords, however. Still
trying to track this one down and see if I can solve it. - latest I have is
that they were reported
Thanks for the reply!
I'm currently using just the keywordId, which "seems" to be working for
now. I'm following the information under 'Report Fields Normalization'
on http://code.google.com/apis/adwords/docs/reportguide.html#normalization.
Someone told me that keywordId is not unique to a cam
I ended up joining on accountid, campaignid, adgroupid, and keywordid. It
may be over kill, but it has worked for me.
If you are using .net 3.5 or higher take a lookat the the linq join. That
is how I did it.
On Monday, February 27, 2012 9:53:33 AM UTC-5, mmasters wrote:
>
> Hello,
>
> I'm migr
