Content ingestion migration guide

We are excited to announce some major improvements to content ingestion, which include a much simpler interface for you to ingest video content and manage your content metadata.

Mapping content metadata to inventory key-values is deprecated.

Any new CMS metadata values expected to be available as Ad Manager inventory key-values (as they've been in the past), will no longer be possible in targeting via line items, protections, or ad rules; or in reporting. Details about the new workflow can be found below.

Benefits to content ingestion with the new Ad Manager interface

With the new content ingestion, you can target and filter on CMS metadata after ingestion. You no longer have to manually map metadata to Ad Manager inventory key-values before being able to target. Also, dedicated targeting dimensions now exist specifically for CMS metadata, differentiating them from non-video inventory key-values. Line items targeting one or more CMS metadata sources take up to 24 hours to start delivering impressions.

Video content ingestion

Content ingestion interface changes

Section	Description of changes
Content	View all of your content, or content based on filters in the updated content section. Metadata listed on the content details base displays as it was ingested from your CMS, rather than only the mapped metadata, as in the legacy version. See legacy help content
Content bundles	Create content bundles based on the exact CMS metadata that was ingested, rather than on what you've manually mapped, as in the legacy version. Content can be added or excluded from bundles using rules. As new content is ingested from your CMS, bundles are automatically updated based on your rules. See legacy help content
Metadata	Metadata mapping is no longer required or available. All metadata is available once ingested. You cannot remove unwanted metadata in Ad Manager. CMS metadata is displayed exactly as ingested from your CMS, and is immediately available to target and filter content. Although disabled by default, you have the option to rename or merge outdated keys or values from your feed, directly in the Ad Manager interface.  See legacy help content
Targeting	Rather that targeting custom key-values that were mapped from your ingested metadata, you can directly target based on your ingested CMS metadata. These targeting updates are available in line items, ad rules, and protections. See legacy help content
Reporting	The reporting interface and workflow has not changed. However, reports you run for CMS metadata will no longer include data for custom key-values from your ad tags. Once you've targeted metadata, it becomes available for reporting.

There are no changes to the content sources section of the interface or to the workflow.

Since historical data doesn't exist for newly-ingested metadata, checking inventory and forecasting on this content during the migration period may be inaccurate. As with any forecasting data in Ad Manager, waiting 28 days for the most accurate inventory count is recommended.

 

Fix unsupported metadata prior to deprecation

 

Before you can migrate to the new content ingestion, some legacy issues may need to be corrected. This should be done prior to the deprecation date of March 31, 2019.

Content bundles issues

• Content bundles using the "Any" filter

  These should be updated to either remove that criteria, or edit the rule to filter by "Name" instead. The new content ingestion requires more specific filters, so the "Any" filter will be deprecated.

Metadata mapping issues

• Two CMS metadata keys being mapped to one with different value definitions

  These should be edited to map to the same value (whichever is correct). Instances of this may have been created to address a spelling issue.

  For example, if:

  movie:this_movie is mapped to movie:this_other_movie, and
  movie-name:this_movie is mapped to movie:this_movie

  The movie and movie-name keys are merged, but it is unclear what to do with the this_movie value of that merged key.

  The preferred solution is to update one of those two mappings to match the other.

• More than two mapped keys are being chained to each other

  These should be edited to map to only one master CMS metadata key, and map all subsequents to that key.

  For example, if:

  movie:this_movie is mapped to movie:this_other_movie, and
  movie:this_other_movie is mapped to movie:this_other_movie_chain

  One mapping tells us we want things to be populated with movie:this_other-movie and one mapping tells us we do not want that.

  The preferred solution is to update the former mapping to match the latter. In this case both movie:this_movie and movie:this_other_movie would map to movie:this_other_movie_chain.

• Mismatched data types

  This could happen when a CMS metadata key whose values are strings is mapped to another metadata key whose values are numbers. These should either be deleted or edited to correct the data type or associated value.

  Mismatched data types include mismatched string, numeric, or content owner types, and are most likely the result of a mapping error.

One additional type of mapping issue that may occur, which is not exposed in Ad Manager, is when a CMS metadata key has been mapped to multiple other keys. You may be contacted to determine if these were mapped in error, and to correct the issue.