zoukankan      html  css  js  c++  java
  • Banner推送流程

    Understand the banner delivery process

     
    From: http://www.openxtips.com/2009/04/tip-8-understand-the-banner-delivery-process/

    The banner delivery process

    It does not matter which zone tag type you use, the banner delivery process pretty much follows the same process. After some initial setup of the environment, the OpenX ad server uses the following process to determine which banner to deliver.

    1. Find all of the active banners1 that are linked to the zone.
    2. Are there any active banners linked to the zone that are from Contract (Exclusive) campaigns? If so:
      1. Do any of the linked Contract (Exclusive) campaign banners “fail” delivery limitations?2 If so, discard these banners.
      2. Are any of the linked Contract (Exclusive) campaign banners incompatible with the zone tag type?3 If so, discard these banners.
      3. Are there any banners remaining? If so:
        1. Select one of these banners via the campaign weight/banner weight process (see below).
        2. Log a request, using the selected banner ID and the zone ID.
        3. Display the banner.
        4. Log an impression, using the selected banner ID and the zone ID.
    3. If this point is reached, then there were no banners from Contract (Exclusive) campaigns that could be displayed.
    4. Are there any active banners linked to the zone that are from Contract campaigns? If so:
      1. Do any of the linked Contract campaign banners “fail” delivery limitations? If so, discard these banners.
      2. Are any of the linked Contract campaign banners incompatible with the zone tag type? If so, discard these banners.
      3. Are there any banners remaining? If so:
        1. Possibly select one of these banners via the Contract campaign banner selection process (see below).
        2. If a banner is selected:
          1. Log a request, using the selected banner ID and the zone ID.
          2. Display the banner.
          3. Log an impression, using the selected banner ID and the zone ID.
    5. If this point is reached, then there were no banners from Contract (Exclusive) campaigns that could be displayed, and there were either no banners from Contract campaigns that could be displayed or no banner from a Contract campaign was required to be shown.
    6. Are there any active banners linked to the zone that are from Remnant campaigns? If so:
      1. Do any of the linked Remnant campaign banners “fail” delivery limitations? If so, discard these banners.
      2. Are any of the linked Contract campaign banners incompatible with the zone tag type? If so, discard these banners.
      3. Are there any banners remaining? If so:
        1. Select one of these banners via the campaign weight/banner weight process (see below).
        2. Log a request, using the selected banner ID and the zone ID.
        3. Display the banner.
        4. Log an impression, using the selected banner ID and the zone ID.
    7. If this point is reached, then there were no banners from Contract (Exclusive) campaigns that could be displayed, there were either no banners from Contract campaigns that could be displayed or no banner from a Contract campaign was required to be shown, and there were no banners from Remnant campaigns that could be displayed.
    8. Is the zone set up via zone chaining to be linked to another zone? If so, re-start the process from the first step, using the new zone.
    9. If this point is reached, then there were no banners from Contract (Exclusive) campaigns that could be displayed, there were either no banners from Contract campaigns that could be displayed or no banner from a Contract campaign was required to be shown, there were no banners from Remnant campaigns that could be displayed, and the zone is not set up via zone chaining to be linked to another zone.
    10. Is a default banner configured? If so:
      1. Log a request, using the selected banner ID and the zone ID.
      2. Display the banner.
      3. Log an impression, using the selected banner ID and the zone ID.
    11. If this point is reached, then no banner can be displayed.
    12. Display a “blank” 1×1 .gif pixel.
  • 相关阅读:
    SQL 操作结果集 -并集、差集、交集、结果集排序
    MongoDB系列四:解决secondary的读操作
    org.apache.hadoop.ipc.RemoteException: User: root is not allowed to impersonate root
    hive 中窗口函数row_number,rank,dense_ran,ntile分析函数的用法
    FormData上传文件同时附带其他参数
    Hive删除分区
    Hive日期格式转换用法
    HIVE 不支持group by 别名
    ODS与EDW的区别
    hive数据类型转换、字符串函数、条件判断
  • 原文地址:https://www.cnblogs.com/ldms/p/3066764.html
Copyright © 2011-2022 走看看