<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01068nam a22001457a 4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">521180</subfield>
    <subfield code="d">521180</subfield>
  </datafield>
  <controlfield tag="008">221226b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Mensch, Jeffrey </subfield>
    <subfield code="9">36392</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Screening inattentive buyers</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">The American Economic Review  </subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">112(6), Jun, 2022: p.1949-1984</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Information plays a crucial role in mechanism design problems. A potential complication is that buyers may be inattentive, and so their information may endogenously and flexibly depend on the offered mechanism. I show that it is without loss of generality to consider contour mechanisms, which comprise triplets of allocation probabilities, prices, and beliefs, and are uniquely determined by a single such point. The mechanism design problem then reduces to Bayesian persuasion along the optimal contour. This reduction has significant implications for both the implementation of the optimal mechanism and the revenues that can be achieved. &#x2013; Reproduced </subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="a">The American Economic Review  </subfield>
  </datafield>
  <datafield tag="906" ind1=" " ind2=" ">
    <subfield code="a">INFORMATION TECHNOLOGY</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">AR</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">395230</subfield>
    <subfield code="a">IIPA</subfield>
    <subfield code="b">IIPA</subfield>
    <subfield code="d">2022-12-26</subfield>
    <subfield code="h">112(6), Jun, 2022: p.1949-1984</subfield>
    <subfield code="p">AR127736</subfield>
    <subfield code="r">2022-12-26</subfield>
    <subfield code="y">AR</subfield>
  </datafield>
</record>
