criteo Bid Adapter: allow to specify tagid in params

[ptomasroos]

Type of change

• Feature

Description of change

We use the networkId and not zoneId's. But there are still cases where we are constrained by the requirement to have a fully matching adUnitCode to get the tagid set.

All other adapters support to explicit set placement, id, ect I think its extremely useful to be able to continue to use the network id approach but still specify the adUnitCode or tagid which is the internal name for the same mapping

[acomets]

Hi @ptomasroos, why can you not use the adUnitCode that is already mapped to tagid?

If not, we can look into adding tagid, but it may be cleaner to add it via ortb2 with something like

imp.tagid = deepAccess(bidRequest, 'ortb2Imp.tagid') || bidRequest.adUnitCode;

[ptomasroos]

@acomets Thanks for the feedback.

The reason is because the same adUnitCode could have different bidder configurations depending on key values on our side, and reusing them and adding the same adUnitCode over and over again makes it very hard to track which adUnitCode is request later down in the requestBids.

We could have a section where native is enabled, but not on the first the same adUnitCode since they are virtually the same placement but not at runtime. All bidders except criteo supports to explicitly set the placement id which is why I think it makes sense to resolve this issue for us at least.

Moving back to the zone id's feels cumbersome given multi ad size support

[acomets]

Thanks @ptomasroos, and would it be okay for you to use ortb2 to pass us tagid via ortb2Imp.tagid?

[ptomasroos]

@acomets Of course. I see no issues with that!
Do you want me to update the PR?

[ptomasroos]

Friendly reminder @acomets

[acomets]

Hi @ptomasroos, sorry for the delay in response.

Sure if you don't mind feel free to update the PR directly, that would be great!

Thanks

[ptomasroos]

NP, fixed @acomets