Subscribe to Our Newsletter

x

Inside the Ad Manager Dashboard

If you rely on ad revenue, the article page is your cash cow. It generates the views and keeps audiences on your site. RebelMouse's Ad Manager dashboard enables you to easily swap out ads, change placement, and experiment as much as you want without relying on tech resources. Enjoy incredible control over your revenue.


Access the Ad Manager Dashboard

Go to Ad Manager in the left-hand navigation menu (☰). Alternatively, you can type "{YourDomain}/core/dashboard/a_manager" in your browser's address bar.

How Ad Manager Is Divided

There are several different placements for your ads:

Header Ad

This will place an ad at the top of your page.

Article Before Body

The Article Before Body section is where you want to add an ad tag in order to serve ads at the beginning of your articles, before the start of any content. This is a common ad placement because it's visible upon first load. You can toggle this ad option on or off.

Here's an example of how it looks on site:

Ads After X Words

Ads after X words allows you to set ads to automatically appear after a certain number of words in your article. This helps ensure that ads appear throughout your article, but not too closely together.

Note: RebelMouse will not cut off a paragraph midway through to place an ad. If you select 150 words as the break point, for instance, RebelMouse will find the closest end of a paragraph after 150 words before placing the ad.

Just like with the Article Before Body section, you can toggle any ad placements on, off, or even delete them if necessary.

You can keep adding as many ads as you want with the + Add Item button at the bottom of the page:

For example, this is how an ad after 60 words looks in an article:

We encourage you to add multiple ad placements this way. You might want ads to appear after 150 words, 500 words, and 1,000 words. The key is to experiment. Also, if an article is shorter than the number of words selected, that ad will not appear.

Ads in Assembler

The Ads in Assembler option is where you can set ads that will automatically appear after a certain number of Assembler items in your article. This number can be set globally in our Layout & Design tool, or on a per-post basis in Assembler's settings. After navigating to the "Ads In Assembler" tab, you'll find expandable and collapsible sections containing different ad placement options in Assembler.

If there is one ad entered into Ad Manager, the ad will be repeated. Example: You have an Assembler with 15 items and you choose to show an ad after every five items. The one ad you have in Ad Manager will be shown three times.

If there is more than one ad entered into Ad Manager, the ads will be displayed in the order they're listed in. Example: You place two ads into Ad Manager, have an Assembler with 20 items, and you choose to show an ad after every five items. The first ad shown will be ad #1 in Ad Manager. The second ad shown will be ad #2. The third and fourth ads shown will be ad #2 again because we repeat the last ad that was entered into Ad Manager instead of cycling through the ads again.

Ads Before Assembler

This option displays an ad before the start of an Assembler.

Ads in Assembler

With this option, ads can be placed between Assembler items if it's in listicle mode, or below an Assembler slideshow if it's in slideshow mode.

Ads in Fullscreen Slideshows

We understand how vital it is to monetize your articles, so we provide you with the tools that will allow you to both make them look beautiful and bring in revenue. When it comes to full-screen slideshows, we have two fixed placements where you can insert ad tags: At the top of the slideshow and on the right rail.

Here's an example of how it looks on site:

Customize Ad Codes by Device

You can add separate ad codes for desktop, mobile, and tablet devices to ensure that your ad placements fit each type of screen correctly.

Note: You can also add Google AMP-compatible ad code for each placement. Learn more about Google AMP + RebelMouse.

Your Ads in Facebook Instant Articles

As you saw above, you have the option of implementing ads into Instant Articles using both the Body Words (an ad every X words) and Ads in Assembler (an ad between X number of Assembler items) methods.

Here are a couple of best practice recommendations:

  • Facebook Instant Articles doesn't support using an ad before the body of a post, so don't place the ad in the Header or Body sections.
  • When using Body Words, we recommend setting up the ad so it displays after no less than 100 words. Otherwise, it could be rejected by Facebook.

How to Add Ads.txt to Your Site

Ads.txt stands for "Authorized Digital Sellers," and is a simple, flexible, and secure method that publishers and distributors can use to publicly declare the companies they authorize to sell their digital inventory. The mission of the ads.txt project is straightforward: increase transparency in the programmatic advertising ecosystem. You can find more information on ads.txt here.

In our Ad Manager dashboard, you can add content from any .txt file digital sellers have sent to you. It's a simple process we've outlined below:

1. Open the left-hand navigation menu (☰) and click on Ad Manager.

2. Click on the Ads.txt tab and copy-paste the content of the .txt file(s) you've received from your ad providers.

3. Click Save.

4. RebelMouse will generate a URL ending in /ads.txt where you can see the list of your authorized digital sellers. Here's an example: https://www.azula.com/ads.txt.

Particle Assembler: Ads in Slideshows Now Supported

You can now insert ads between slides in a slideshow!

Monetizing users' engagement and page views is pivotal to most digital businesses, and our Particle Assembler has been an invaluable tool in helping RebelMouse clients to insert native ads seamlessly into their content. Now we've taken this functionality one step further by introducing support for ads between slides in Assembler's slideshow layout.

Keep reading... Show less

Inside RebelMouse’s Quality Assurance Operations

How We've Perfected Stress-Free Publishing

At RebelMouse, we like to refer to our enterprise publishing platform as "lean tech." Most publishers have a natural inclination to start doubling down on teams of developers who try to build unique experiences to help stand out above the noise. But they should actually be doing the opposite: Lean tech is the preferred way to cut through content saturation. By allowing RebelMouse to obsess over your product, content producers, editors, managers, and everyone in between can focus on creating quality content and taking advantage of opportunities to leverage distributive publishing strategies that create real revenue growth.

One of the major reasons we're able to maintain a lean tech environment is thanks to our approach to quality assurance (QA). We make updates to our platform daily to ensure our clients always have access to the most robust, high-performing, and secure version of our platform. Behind the scenes, this means having a solid QA structure that's efficient, creates less bugs, and catches the ones that do pop up before they go live. It's a system of checks and balances that's hard and costly to replicate on a custom CMS. Here's a glimpse into how it works.

Our Tech Stack Toolbox

  • Cucumber
  • Java
  • Junit
  • Maven
  • Selenium WebDriver
  • TeamCity
  • Zalenium (Selenium Grid)

Our Checks and Balances Workflow

Automated Regression Testing Cycle

The Lifecycle of a Product Update

When an update is first made to RebelMouse, TeamCity immediately triggers the start of automated tests to review integrity.

TeamCity Build

TeamCity Agent

The tests run in parallel on TeamCity's Build Agent. Next, Zalenium creates docker containers with browsers that matches the count of parallel threads. An Allure report is then generated from the test results, which shows the state of the application after the update.

Allure Report Pass

If a test doesn't complete successfully, the testing framework receives a video with a failed test and attaches it to the Allure report.

Allure Report Issue

Based on the report analysis, a QA specialist will create a "bug" ticket in our product management software to address the issue if needed. Then, information about the bug is immediately sent to the project manager and we begin the process of correcting the problem.

The media powerhouses we power can publish with confidence knowing that any product issues that arise are met with a tried-and-true process to fix the problem with little-to-no disturbance to their workflow. If you have any questions about this process, please email support@rebelmouse.com.

Related Articles

Related Posts vs. Posts in Assembler

Here's the difference between Related Posts and Posts in Assembler.

By using Related Posts and Posts in Assembler, you can help your audience stay engaged with your site's content and generate more traffic. Both of these features can be added to any post through Entry Editor.

When creating or editing a post, you can add a Related Posts section to the bottom of it that consists of a selection of existing posts on your site that you choose to surface. Only the main image and content headline are pulled, along with a link to the original post. This is similar to the Around the Web section that also shows up at the end of your post when you enable it from the SEO tab of Entry Editor.

Keep reading... Show less
Subscribe to Our Newsletter