Thank you for the response Kevin.
I posted in the community forum, but no one responded to me (link in the original post). The "iu" query string seems exactly equivalent to the adUnitCodes separated by "/". Every example I checked has this and I've never seen a counter example. I just used the API to examine the ad units directly and I can confirm that under a single network address, I see 2 ad units with different ad unit ids but the EXACT SAME adUnitCode, which is counter to what the API doc states.
Below are the 2 ad units I examine, I replaced the sensitive information, but kept the relationship entact. You can see that both have the the same adUnitCode of "desktop".
Cheers,
Ostap
---
Device targeting ad unit 1
{
'id': '104',
'parentId': '103',
'hasChildren': False,
'parentPath': [
{
'id': '101',
'name': '1111',
'adUnitCode': '1111'
},
{
'id': '102',
'name': 'ad_unit_grand_parent_1',
'adUnitCode': 'ad_unit_grand_parent_1'
},
{
'id': '103',
'name': 'ad_unit_parent_1',
'adUnitCode': 'ad_unit_parent_1'
}
],
'name': 'desktop',
'description': None,
'targetWindow': 'BLANK',
'status': 'ACTIVE',
'adUnitCode': 'desktop', // original adUnitCode in the ad unit
...
}
---
Device targeting ad unit 2
{
'id': '204',
'parentId': '203',
'hasChildren': False,
'parentPath': [
{
'id': '101',
'name': '1111',
'adUnitCode': '1111'
},
{
'id': '202',
'name': 'ad_unit_grand_parent_2',
'adUnitCode': 'ad_unit_grand_parent_2'
},
{
'id': '203',
'name': 'ad_unit_parent_2',
'adUnitCode': 'ad-ad_unit_parent_2'
}
],
'name': 'desktop',
'description': None,
'targetWindow': 'BLANK',
'status': 'ACTIVE',
'adUnitCode': 'desktop', // original adUnitCode in the ad unit
...