How ZEN Master Objects correspond to ESNI Schedule

zen master channel ext id these are advanced options when editing a channel in zen master media in the 224 media element, the channel ext id corresponds to the source parameter within the \<media> tag and/or \<mediapoint> tags in this context, the channel ext id denotes the channel that will be monitored for scte messages in a matchsignal mediapoint example \<media xmlns="http //www scte org/schemas/224" lastupdated="{{$isotimestamp}}" description="media without resident" id="customer/media/esni demo main" source="esni demo main"> viewingpolicy in the 224 viewingpolicy element, the channel ext id corresponds to the \<content> tag value in this context, the channel ext id denotes the source that will be switched to the desired audience when that viewingpolicy is active example \<content xmlns="urn\ scte 224\ action">esni demo main\</content> zen master target ext id these are advanced options when editing a target in zen master audience in the 224 audience, the target ext id corresponds to either (in priority order) a tag (such as \<vird> ) with the urn\ scte 224\ audience namespace if no namespace exists , the id parameter within the \<audience> tag this indicates the target that will be switched when that audience is referenced example \<audience id="ibc/audience/demo/trg1" lastupdated="2024 11 08t17 42 42 475z" description="europe news and sports" xmlns="http //www scte org/schemas/224" match="any"> &#x9;\<vird xmlns="urn\ scte 224\ audience">target 1\</vird> \</audience> as zixi delivers unicast, linear feeds, by default the esni decisioning service does not make use of zip or homezip tags accordingly, overlapping audiences are out of scope we recommend having an audience per target identified using the audience id or one of the designated vird or dma tags available per the schema if tags other than vird or dma are required, contact your zixi account rep