AppNexus Meta Data

[Slind14]

@jaiminpanchal27 @jsnellbaker @sumit116

Would you be so good to add the additional data which is already sent in the bid response to meta?

See: #3115

[jsnellbaker]

I'll take a look at this request and follow-up.

[jsnellbaker]

@Slind14 just to clarify the request here and what's listed on #3115, would you want the following fields from the bid to be set inside the meta field as:

advertiser_id      --> buyerId
buyer_member_id    --> networkId
brand_category_id  --> brandId

I'm not entirely clear on the mapping given we have terms like 'buyer' and 'advertiser', but they're pointing to the same singular field called buyerId in the #3115 issue.

Please let me know your thoughts on this point. Thanks!

[Slind14]

If buyer_member_id is the DSP, then yes.

Did you have a look at the example at the bottom of the first post in that issue?
#3115

[jsnellbaker]

buyer_member_id is the seat code/id used within the adserver for whoever served the bid (ie it's like the buyer's account). So it sounds like it shouldn't be used here since it's not an exact match to that (or any) field?

I did look through that list, but I wasn't sure where this field would exactly fit in the scheme of things.

[Slind14]

It looks like your seat code stretches across both DSP and buyer, that makes it tricky. With other exchanges it is clearly separated.

There are multiple seats with the same DSP and different buyer. So I would treat this as buyer. If there is another id for just the DSP that would be nice.

[jsnellbaker]

I'm not sure there's a value for the DSP specifically.

If we then treat the buyer_member_id as the buyerId, where you do think the advertiser_id should go then (since it's ear-marked to the same field in the list)?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.