"caseValue" for ProductPartition unexpectedly null when subdivided by "Channel" or "Channel Exclusivity".

128 views
Skip to first unread message

HK

unread,
Feb 19, 2015, 3:54:13 PM2/19/15
to adwor...@googlegroups.com
Hi,

Similar to this post for Product Scopes, using v201409, if I subdivide a product partition using either "Channel" or "Channel Exclusivity", caseValue is returned as null on the criterion object. The forwardCompatibilityMap object on the AdGroupCriterion is also null. This will break our AdWords API integration if merchants start using it and will quickly become a serious problem as we have no way of representing these product partition with the current APIs/types. I assume new types will eventually be added to ProductDimension in a future API version, but in the meantime, we can't have this broken.

Any help to resolve this quickly would be greatly appreciated.

Thanks,
Hans

Michael Cloonan (AdWords API Team)

unread,
Feb 20, 2015, 9:44:34 AM2/20/15
to adwor...@googlegroups.com
Hello Hans,

I've heard other reports of issues when Channel and Channel Exclusivity are used; I will forward your findings as well to give the team more information when looking into the issue.

Regards,
Mike, AdWords API Team

HK

unread,
Feb 20, 2015, 1:42:23 PM2/20/15
to adwor...@googlegroups.com
Thanks, Mike. From the outside, it seems to me that these new types shouldn't be made available in the AdWords UI until everyone is on a future API version that supports them.

HK

unread,
Mar 2, 2015, 12:33:54 PM3/2/15
to adwor...@googlegroups.com
Hi, Mike

Any updates on this issue or the Product Scope issue?

Thanks,
Hans

Michael Cloonan (AdWords API Team)

unread,
Mar 3, 2015, 9:31:25 AM3/3/15
to adwor...@googlegroups.com
Hello,

I apologize for the delay. We are still looking into this. I will update you as soon as I have information to share.

Regards,
Mike, AdWords API Team

Michael Cloonan (AdWords API Team)

unread,
Mar 11, 2015, 9:03:28 AM3/11/15
to adwor...@googlegroups.com
Hello Hans,

Unfortunately, we are not able to get these into the current version of the API. For now, we have implemented a workaround using forward compatibility maps.

We have added two keys to these maps. ProductScope.channel can have values ONLINE or LOCAL, and ProductScope.exclusivity can have values MULTI_CHANNL or SINGLE_CHANNEL.

Thank you for your report so that we could get this addressed and planned for a future API version. Please let me know if you have any more trouble with this data.

Regards,
Mike, AdWords API Team

HK

unread,
Mar 11, 2015, 2:56:42 PM3/11/15
to adwor...@googlegroups.com
Hi, Mike

Thanks for looking into this. It's unfortunate that we need to deploy code to our production environment and everything that involves to get around this. You guys are normally good at not making breaking changes to an already released API version. Anyway, is this solution available for Product Groups as well and not just Product Scopes?

Thanks,
Hans

Michael Cloonan (AdWords API Team)

unread,
Mar 12, 2015, 2:02:46 PM3/12/15
to adwor...@googlegroups.com
Hello Hans,

Can you provide more details on exactly what wasn't addressed by the forward compatibility map fixes that we added?

Regards,
Mike, AdWords API Team

HK

unread,
Mar 16, 2015, 10:21:46 PM3/16/15
to adwor...@googlegroups.com
Hi, Mike

I'm seeing forwardCompatibilityMap being populated for Product Scopes, but not Product Groups (BiddableAdGroupCriterion) subdivided for example by Channel. In your 3/11 reply, you refer to Product Partitions and I'm wondering when/if this will work for Product Partitions?

Thanks,
Hans

Michael Cloonan (AdWords API Team)

unread,
Mar 17, 2015, 9:25:57 AM3/17/15
to adwor...@googlegroups.com
Hello Hans,

I am still not understanding exactly what the issue is. Are you saying that you are not seeing the forwardCompatibilityMap being populated on BiddableAdGroupCriterion objects? If that's true, where are you seeing it populated?

Or are you saying that there are fields you expect within the forwardCompatibilityMap that aren't there? If so, what exact data is missing from that map that you would expect?

Regards,
Mike, AdWords API Team

HK

unread,
Mar 17, 2015, 11:23:19 AM3/17/15
to adwor...@googlegroups.com
Hi, Mike

Correct, I am not seeing forwardCompatibilityMap being populated on BiddableAdGroupCriterion objects (Product Partitions). However, I am seeing forwardCompatibilityMap on CampaignCriterion objects (Product Scopes). I would expect it to show up on both types of objects so that anyone using v201409 have a chance to get unblocked until they upgrade to v201502.

Hopefully that makes sense. If not, I'll be happy to clarify further.

Hans

HK

unread,
Mar 17, 2015, 11:29:43 AM3/17/15
to adwor...@googlegroups.com
Just to be clear, I'm seeing forwardCompatibilityMap be null on BiddableAdGroupCriterion objects.

Hans

Michael Cloonan (AdWords API Team)

unread,
Mar 17, 2015, 12:23:32 PM3/17/15
to adwor...@googlegroups.com
Thank you Hans. I will forward this information to the team and let you know when I hear back.

Regards,
Mike, AdWords API Team

HK

unread,
Mar 26, 2015, 4:06:03 PM3/26/15
to adwor...@googlegroups.com
Hi, Mike

Just wanted to let you know that this is not a priority for us anymore as we are moving to v201502 sooner than originally planned as we need this resolved quickly. Other might of course still be affected though.

Thanks,
Hans

Josh Radcliff (AdWords API Team)

unread,
Mar 31, 2015, 4:32:43 PM3/31/15
to adwor...@googlegroups.com
Hi Hans,

In case others who are staying on v201409 a bit longer encounter this issue, we have added forwardCompatibilityMap entries to AdGroupCriterion and CampaignCriterion.

For example, using v201409 to retrieve a campaign's ProductScope criterion, you'll get something like this if the scope includes the new ProductChannelExclusivity dimension type (this example is for Channel Exclusivity = Multi channel):

               <campaignId>123456</campaignId>
               <isNegative>false</isNegative>
               <criterion xsi:type="ProductScope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                  <id>78901234</id>
                  <type>PRODUCT_SCOPE</type>
                  <Criterion.Type>ProductScope</Criterion.Type>
               </criterion>
               <forwardCompatibilityMap>
                  <key>ProductScope.channel</key>
                  <value/>
               </forwardCompatibilityMap>
               <forwardCompatibilityMap>
                  <key>ProductScope.exclusivity</key>
                  <value>MULTI_CHANNEL</value>
               </forwardCompatibilityMap>
               <CampaignCriterion.Type>CampaignCriterion</CampaignCriterion.Type>

Similarly, when retrieving product partitions of an ad group using v201409, you'll get the following if a partition uses one of the new ProductDimension types introduced in v201502:

                    <criterionUse>BIDDABLE</criterionUse>
                    <criterion xsi:type="ProductPartition">
                        <id>123456789</id>
                        <type>PRODUCT_PARTITION</type>
                        <Criterion.Type>ProductPartition</Criterion.Type>
                        <partitionType>UNIT</partitionType>
                        <parentCriterionId>60408125302</parentCriterionId>
                    </criterion>
                    <forwardCompatibilityMap>
                        <key>ProductPartition.exclusivity</key>
                        <value>NULL</value>
                    </forwardCompatibilityMap>
                    <forwardCompatibilityMap>
                        <key>ProductPartition.channel</key>
                        <value>LOCAL</value>
                    </forwardCompatibilityMap>

In both cases, the returned forwardCompatibilityMap.value will be one of LOCAL, ONLINE, or ALL.

Cheers,
Josh Radcliff, AdWords API Team

HK

unread,
Mar 31, 2015, 8:41:12 PM3/31/15
to adwor...@googlegroups.com
Thanks, Josh!
Reply all
Reply to author
Forward
0 new messages