<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic 19 August 2024 What's new in SAS® 360 Match in SAS 360 Match</title>
    <link>https://communities.sas.com/t5/SAS-360-Match/19-August-2024-What-s-new-in-SAS-360-Match/m-p/939980#M247</link>
    <description>&lt;P&gt;In the latest update of SAS 360 Match, you can specify a primary size and additional sizes in a placement. When you specify multiple sizes, the bid request creates a bid from the intersection of the sizes in the ad request and the &lt;STRONG&gt;Size&lt;/STRONG&gt; and &lt;STRONG&gt;Other sizes&lt;/STRONG&gt; fields in a placement. For example, an ad request that specifies sizes A, B, and C and a placement with &lt;STRONG&gt;Size&lt;/STRONG&gt; set to B and &lt;STRONG&gt;Other sizes&lt;/STRONG&gt; set to C, D, and E will only use sizes B and C in bid requests and only those sizes are mapped for the network.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Contact SAS Technical Support to enable the option to reduce bid sizes to those that are in both the ad request and placement. By default, SAS 360 Match uses all request sizes with network size mappings only.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Aug 2024 19:10:56 GMT</pubDate>
    <dc:creator>GregAtSAS</dc:creator>
    <dc:date>2024-08-20T19:10:56Z</dc:date>
    <item>
      <title>19 August 2024 What's new in SAS® 360 Match</title>
      <link>https://communities.sas.com/t5/SAS-360-Match/19-August-2024-What-s-new-in-SAS-360-Match/m-p/939980#M247</link>
      <description>&lt;P&gt;In the latest update of SAS 360 Match, you can specify a primary size and additional sizes in a placement. When you specify multiple sizes, the bid request creates a bid from the intersection of the sizes in the ad request and the &lt;STRONG&gt;Size&lt;/STRONG&gt; and &lt;STRONG&gt;Other sizes&lt;/STRONG&gt; fields in a placement. For example, an ad request that specifies sizes A, B, and C and a placement with &lt;STRONG&gt;Size&lt;/STRONG&gt; set to B and &lt;STRONG&gt;Other sizes&lt;/STRONG&gt; set to C, D, and E will only use sizes B and C in bid requests and only those sizes are mapped for the network.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Contact SAS Technical Support to enable the option to reduce bid sizes to those that are in both the ad request and placement. By default, SAS 360 Match uses all request sizes with network size mappings only.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Aug 2024 19:10:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-360-Match/19-August-2024-What-s-new-in-SAS-360-Match/m-p/939980#M247</guid>
      <dc:creator>GregAtSAS</dc:creator>
      <dc:date>2024-08-20T19:10:56Z</dc:date>
    </item>
  </channel>
</rss>

