Key-Value targeting - Content metadata changes

[Matias Vega]

Hey Ad Manager Team,

I know there are upcoming changes related to content metadata and the way we do custom targeting at the line item level:

"You can no longer map key-values to content metadata.

Beginning March 1, 2022, the targeting picker will not allow you to save content key-values (mapped metadata) from the "Custom targeting" type menu."

Regarding this, please help with some clarifications, since we are currently using the API to do custom key-value targeting, and these values are mapped to content metadata.

1. What will happen with the old key-values mapped to content metadata? will they be deactivated or removed from the UI? What about the API?
2. If we set a line item with custom targeting with these old key values via API, what will happen?
3. Will the CmsMetadataService give us the keys and values directly to be imported?
4. What is the difference between regular key-values and content key-values (mapped to content metadata), and how can they be distinguished at the UI level?

Just FYI, we are currently using v202111 Java API.

[Ad Manager API Forum Advisor]

Hi Matias,

 

Thanks for contacting the Ad Manager API team, this is Yasmin.

 

For your queries regarding the UI, I would ask for you to direct them to our Community forum. The product specialists should be able to address your concerns better.

 

For the API, allow me to raise this to the team in order to be further investigated. Rest assured that one of our colleagues will reach out to you soon.

 

Regards,

 

Yasmin Gabrielle Padua Ad Manager API Team

ref:_00D1U1174p._5004Q2W4zIx:ref

[ADvendio]

Hello Yasmin,

I'm a colleagues of Matias at ADvendio. Since he is currently off I wanted to follow up on this. For now we haven't received any answers yet and are still wondering how the migration will be handled via API. Same with the posted question in the UI community. Can you please provide us an update if there is something to share?

Best Regards,

Pascal Clausen

[Ad Manager API Forum Advisor]

Hi everyone,

The new CMS Metadata targeting is still a part of custom targeting, but now has a new subtype in the CustomCriteriaSet: CmsMetadataCriteria. In the UI, this appears as a new "CMS metadata" dropdown in the "Custom targeting" section of the targeting picker.

The existing mapped key values have been migrated to new entities with new IDs in the CmsMetadataService. There is no available mapping between these IDs other than mapping their name strings. The existing mapped key values were not deactivated by default and should still be accessible via the API. 

Hope that answers everything, let me know if you need more details.

Thanks,

Chris Seeley Ad Manager API Team

 

ref:_00D1U1174p._5004Q2W4zIx:ref