Though TownNews.com representatives often participate in discussions, this is not a customer service site. For immediate help, call 800-293-9576 or submit a support request via our online ticketing system.
Starting as early as January 1st, 2018, sites with programmatic advertising inventory that’s less than 70 percent viewable will see a dramatic drop in fill rate and eCPMs. At our December customer webinar, we’ll talk about why viewability matters to digital advertising and what you can do to increase your score and impact your bottom line.
Topics will include:
- How advertiser expectations, the IAB and the Better Ad Standards are affecting the industry.
- How to find out your current viewability score to see where you stand.
- Simple ways to improve and optimize your site’s viewability.
- New BLOX CMS features and enhancements to help boost your viewability score.
- . . . and much more!
Want to take in the webinar on your own time? Register now and we’ll send you a link to the webinar recording once it’s ready.
It makes sense to me is to closely tie adblocker detection with subscription / membership recruitment.
So - for example - if an adblocker is detected, BLOX should notify the reader and encourage them to whitelist the site AND allow publishers to direct the reader to support our work through a membership / subscription.
Publishers should be able to easily modify the message the reader sees to make it fit within the corporate "voice" of the organization.
Publishers could also be given the option to allow an ad-free experience to readers who become subscribers / members.
It could work something like this:
Reader: I hate ads and use an ad blocker.
Us: We get it, but if you want to view our content for free, we need you to tolerate the ads. They are the price of admission. But, if you become a member / subscriber, we can offer you and ad-free experience. Sound good?
Reader choice 1: Totally! I want to become a subscriber today!
Us response 1: Great! Here's a link to become a subscriber.
Reader choice 2: No thanks, but I'll white list you so the ads come through.
Us response 2: Thanks! If you ever want to become a subscriber, here's how.
Reader choice 3: No way, you suck. I'm keeping my ad blocker and not paying you a dime.
Us response 3: We're sorry to hear that. But since we have to pay our bills and the news is not free to report, we'll have to say goodbye for now.
I would like for the ability to customize the Metering Messages within the Community > Subscription settings, the same location that I can customize the emails to customers that have bought a subscription.
Otherwise, I am looking to see what file can be edited to changed the Metering Message when a user has 9 out of 10 free stories to view. Is this CSS or UTL even customizable by the customer?
We're working on an easier module that will allow these to be customized in the admin UI. However, we did implement the code in a way that makes it easy to override these messages at a custom UTL level.
Here is a page with details on the specific macros you can override.
If you don't have access to edit the UTL as described, please contact our Customer Support and they should be able to help.
Is there any way to prevent an empty section from creating unwanted space?
As shown in the screenshots below: masthead-full-top is creating a space in the header that I can't seem to get rid of. Using the inspect element tool in Chrome I can't find CSS to remove the issue, and the section isn't editable itself.
Any help would be greatly appreciated!
Just wondering if that's a planned feature or not.
Safari and Apple's mobile devices have what's known as "Reader View." It's a nice, clean way to read articles online. We just launched our FLEX site and I see I can use Reader View but when I try it only shows the headline, in-story ads and tagline. I've checked other FLEX sites and they seem to work fine.
What could be preventing it from working on my site?
Idea: Revise how the 'buy now' button logic interacts with AP photos ... either add more commonly used AP byline phrases or find a way to better auto detect AP photos moving from Merlin to BLOX
1. What problem(s) does this idea solve? AP, from best we can tell, doesn't have a standardized way of formatting bylines. Some say "Name/AP Photo," some say, "Associated Press file photo," some say XXX "via AP." The "buy now" rule for BLOX stipulates the byline must be 'associated press' or 'ap photo' for the button to disable.
2. Why do you need this idea implemented? Provide as many problems or use cases as possible. We're having too many wire photos go on our site that are for sale that we're not licensed to sell.
3. How often would you use this feature? Daily
4.How many people in your organization would use this feature? The entire company, 200+ people
I am usually very optimistic when we get new updates in Blox. But I have 3 issues with this format.
- First, as pictured, the navigation buttons cover up content. Sure, I figured out how to remove the buttons, but my users won't be able to. The deprecated white navigation buttons in the red bar were the way to go. I'd like this to be a Per-Site choice to make.
- Second, under the hamburger menu, there are no descriptions as to what each button does.
- Third, because of the update, I have a random gray bar at the top that I now have to fix.
- Forth, I do admire the fact that swiping pages left to right now takes a split second. Finally, the swiping has been improved.
Here's my quandary:
We're trying to make our calendar utilization more robust, in part by making calendar categories more easily navigable and by hiding some of the breadth of the calendar categories from users by curating the presentation of certain categories.
To that end, I'd like to use an autonav block to direct users to specific calendar pages, though not necessarily all the subcategories of /calendar/, and possibly even to pages outside the /calendar/ directory.
So, to wit: One of the requested features was a page where users can see text listings of a large number of upcoming events — say for the next month. If I create an associated URL (/upcoming_events/) in the /calendar/ directory, it will show up in the autonav block configured to call /calendar/, but it will also show up in the user submission form for calendar events on the dashboard. I don't want users to be able to submit an event as an upcoming event, but I do want them to be able to utilize the autonav to navigate to /upcoming_events/. If I create /upcoming_events/ outside the /calendar/ directory, it will not appear in the dashboard submission form, but it will also not appear in the autonav.
Similarly, we would like users to be able to make submissions under certain categories that are not necessarily presented to all users in the autonav. This is because we have a number of calendar categories which are not extensively populated (dance, car shows) but could be presented together in a broader category (say, entertainment). If /dance/ and /car_shows/ exist under /calendar/, they'll appear in the dashboard submission form, but also in the autonav. We do not want this because we'd rather direct users to fewer, more populated pages instead of many sparsely populated pages. I can use a card block to pull in /dance/ and /car_shows/ submissions to an /entertainment/ page, but the /entertainment/ page will not show up in the autonav unless it is also under /calendar/ — and thus it will show up in the dashboard submission form, which we do not want because "Entertainment" is a broad enough designation that it becomes meaningless unless curated on the front end.
If I've got it right, this is because the autonav and the dashboard submission form both call /calendar/. After racking my brain, the most efficient solution I can think of for this is a block that looks and functions (for the user) like the autonav, but which can be configured in the CMS to display only selected directories. Is there a block that does this? Is it possible? Am I missing an obvious answer?
Any insights are appreciated.
Citrus County Chronicle
So let me pose this scenario:
We've got a story on our the site. Let's say the New Orleans Saints are making roster cuts on deadline day. Our guys are updating their story w/ new player names every couple of minutes. The story tells readers to 'check back frequently' or 'reload the page' for the latest info. How can we best display this info in BLOX so that people who visit a page frequently during a breaking story actually see the most up-to-date info?
Here is the doc which discusses how you can use flags to reduce caching times for important articles:
As the doc says, there are a few limitations, but in general you'll get updates about every minute or so.
However! Note that this does not affect the users' local browser cache. That is still subject to a 5-minute cache. (You could, if you could find the right words, tell users to force reload the page. It is different in different browsers though, so I'm not sure if there could be an elegant way to say this.)
So this doesn't really work for "live blogging" - but it should address the needs of corrections and story updates and breaking news that you want to push to the front page.
We did have a discussion internally today about some enhancements we can make to bring us closer to having some kind of live blogging environment... I will look into that as a possible future feature.
Does anybody have a quick/easy solution to get something like JuxtaposeJS working on a Flex site?
EDIT: Looks like I might be able to just embed the code though... (and I admit I posted before even trying but figured if somebody already has a system like this that is TownNews friendly it will save me some time).
Would like to learn more about why there's a 5-10 minute delay in newsletters from the moment you click 'send' to the moment they're delivered to subscribers' inboxes. In breaking news situations, that delay puts us well behind our competition. Anything we can do differently?
In breaking news situations, eliminating steps is always a nice thing.
It'd be awesome if BLOX allowed, in users' profiles, to set what section tags their new assets would default to.
For example: I'm Kyle Whitfield. I cover the New Orleans Saints. It'd be great if every asset I created automatically populated new_orleans/sports/saints like it populates my byline and author field.
What problems would this solve? See above
Why do you need this idea? See above
How often would you use this feature? Daily
How many people would this affect in our news org? 100+
We run into problems sometimes where 2 editors are simultaneously in a block, rearranging pins and then accidentally just saving over one another. It'd be nice for blocks to be locked when someone is in one, much like assets would be locked.
We run into situations, especially in breaking news, where 2 people might have our homepage top stories block open. Both are pinning and re-arranging stories -- but they're accidentally saving over each other's work without knowing it.
What problem(s) does this solve? See above
Why do you need this idea? See above.
How often would you use this feature? Daily
How many people would this affect in our news org? 100+
Customer support service by UserEcho