As a Worldnow Client on Mobile Responsive, I would like to see a minimum of (1) and up to (10) mobile 300 x 250 ads as my users scroll down on stories, categories, and home pages across all breakpoints based on standardized story paragraph and/or listicle items logic. User may see multiple per mobile web page load depending on length of story text and/or listicle content. This is IN ADDITION TO any existing ad units.

Requirements:

This feature will be able to be turned on/off through the Site Management section of the Producer.

  • Story page for all breakpoints below 800 :
    • When a user opens a story that is less than 4 paragraphs long, the user will see a 300x250 ad placed between the last paragraph and the copyright information of the story.
    • When a user opens a story that is more than 4 paragraphs long, the user will see a 300x250 ad placed two paragraphs before the 6th paragraph,and between every opportunity thereafter following the same logic of: two paragraphs before the 6th paragraph. Example: If 15 paragraphs, logic will be that 300x250 ad unit will appear between 4th and 5th, 9th and 10th and 14 and 15th, respectively. If story ends at 13 paragraphs, ads will appear between 4th and 5th, 9th and 10th with the logic then ending. This logic inserts the ad at least once with it repeatable up to 9 times with unique key values.
  • Category page for all breakpoints below 800:
    • When a user opens a category page, each section is treated uniquely. If a section has a "+More", then the ad will be placed directly after the "+more" button.
    • When a user opens a category page, each section is treated uniquely. If a section does not have a "+More", then the ad will be placed one story before the 7th story and between every opportunity thereafter following the same logic of: one story before the 6th story. This logic inserts the ad at least once with it repeatable up to 9 times with unique key values.
    • If a unique section does not have teaser text, but includes a "+More" there will be no ad served unless there is a second consecutive section with no teaser text. The ad will then be placed after the second section.
    • If a unique section does not have teaser text, and does not include a "+More", an ad will be served one story before the 13th story.
    • When a user browses a category page, and a single column transitions into a multiple column an ad is served after the 3rd pair of stories.
    • When a user browses a category page, and multiple columns revert to a single column an ad is served after the last pair of stories, and before the start of the single column.
    • When a user browses a category page, and there is less than three unique sections with ten or less total stories on the page there will be no 300x250 served.
  • Home page for all breakpoints below 800:
    • When a user opens a home page, each section is treated uniquely. If a section has a "+More", then the ad will be placed directly after the "+more" button.
    • When a user opens a home page, each section is treated uniquely. If a section does not have a "+More", then the ad will be placed one story before the 7th story and between every opportunity thereafter following the same logic of: one story before the 6th story. This logic inserts the ad at least once with it repeatable up to 9 times with unique key values.
    • If a unique section does not have teaser text, but includes a "+More" there will be no ad served unless there is a second consecutive section with no teaser text. The ad will then be placed after the second section.
    • If a unique section does not have teaser text, and does not include a "+More", an ad will be served one story before the 13th story.
    • When a user browses a home page, and a single column transitions into a multiple column an ad is served after the last single column story, and before the start of the multiple column.
    • When a user browses a home page, and multiple columns revert to a single column an ad is served after the last pair of stories, and before the start of the single column.
    • When a user browses a category page, and there is less than three unique sections with ten or less total stories on the page there will be no 300x250 served.
  • Story page for all breakpoints 800 and above:
    • When a user browses a story page, there will be a 300x250/300x600 flex unit served in column 4 after the last unique section.
  • Category page for all breakpoints 800 and above:
    • When a user browses a category page, there will be a 300x250/300x600 flex unit served in column 4 after the last unique section.
  • Home page for all breakpoints 800 and above:
    • When a user browses a home page, there will be a 300x250/300x600 flex unit served in column 4 after the last unique section.

Developer notes:

  • Custom ads will load AFTER page load in order to satisfy conditional placement logic.
  • Story ad logic will REQUIRE authors to use

    tags in order for the ad unit to find the correct place to attach itself. If p tags are not present it will appear at the bottom of the story.

  • For 980 breakpoint, the right rail will be referred to an column 4.
  • For 980 breakpoint on story page, the ad unit will appear FIRST in column 4.
  • For 980 breakpoint on category and home page, the ad unit will appear after the 5th assigned story in column 4, regardless of which display sizes assigned.
  • For 980 breakpoint on category and home page, the ad unit will appear last in column 4 if less than 5 stories are assigned to column 4 regardless of display size.
  • Gray box used for advertisement slug around 300x250 would be preferable to have the gray box end at the edge of the creative width.
  • The ad unit will honor the initial screen size and not change/disappear based off window resizing.
  • 300x250 appearing in story paragraph logic or category homepage logic will start at the next open numerical reference in the database after wnsz=106. Up to (10) 300x250s can be programmed based on story, category, or home ad injection logic. This will be a NEW ad unit/wnsz(s).Mobile 300x250 should be configurable in the Producer for standard ad unit functionality (on/off, splits recognition,etc).
  • refer to : https://support.google.com/dfp_premium/answer/1697712?hl=en for stories for 800 and above