Content.ad Plugin
Display popular content to your users from your own site and/or from our sponsored partners, increasing visitor engagement and revenue.
Content.ad is a content recommendation platform that helps site owners generate more time-on-site and monetize their content easily and unobtrusively. Content.ad serves billions of impressions across thousands of sites every month. The WordPress plugin is the quickest and easiest way to get Content.ad up and running on your site.
Key Features
Simple Setup – Our 3-step guided installation gets you creating your first widget in minutes.
Flexible Styling – Our widget creation wizard makes customizing the look and feel of the widget simple and straightforward.
Performance Driven – Our state-of-the-art algorithms learn what content is most popular with your users, lowering bounce rates and increasing overall site revenue. Also, since optimization takes place on Content.ad servers and the widget is loaded asynchronously, the plugin doesn’t slow down your site.
Powerful Options – Free enterprise-level features let you control how the widget integrates into your site and what kind of content appears in it, all without leaving your WordPress admin.
Rich Reporting – Use our robust reporting and graphing options to see exactly how well your widgets perform down to the hour.
Personalized Support – Our US-based support staff is available to help you properly set up and optimize Content.ad to meet your needs.
To learn more about Content.ad, visit our publisher FAQ or visit our website.
Installation
Requirements
- PHP 5.2.4 or higher.
- WordPress v3.0.x or higher.
- Multisite is not currently supported.
- You must register with Content.ad. The account is 100% free.
Install Via Plugin Repository
- Log into WordPress admin for your site
- Go to ‘Plugins -> Add New’ and choose ‘Search’
- Search for Content.ad and click ‘Install Now’
- Activate the plugin through the ‘Plugins’ menu
- Go to ‘Settings -> Content.ad’ and click ‘Register your plugin’
- Enjoy!
Screenshots
Easy signup and integration without leaving your WordPress blog.
Multiple styling and configuration options to fit any site.
Placement settings - Create multiple widgets and show them in different places throughout your site.
Advanced analytics shows you how the widget is performing.
FAQ
How quickly does it start working?
The Content.ad Widget will start to work immediately; however, part of the optimization process involves learning which of your content performs the best. A certain number of impressions must be served before the widget is able to fully optimize and display the most effective content.
Does Content.ad work on web sites in any language?
Currently, the tool will only work properly on English language websites.
Will the widget slow down my site?
No. The Content.ad widget is designed to load “asynchronously”. This means your page will load independently of the widget script.
I have sponsored content on my site with clicks but don’t see any revenue.
Revenue is based on actions not clicks. Sponsored content served through the system won’t generate revenue unless the user performs a particular action on the advertisers site (ex. Signs up for a service or purchases something). When this happens the payout is generally much better than what you expect to see from a pay-per-click advertisement. This means that you might need to let the widget run for a while to start seeing revenue.
I’ve configured my widget to display sponsored content but don’t see them in the widget.
Content.ad only displays sponsored content on approved domains. This means new sites could take 24 to 48 hours before sponsored content starts getting served. Once your site has been reviewed you will be notified.
How do I control ad placement?
On the Content.ad plugin widget settings page, hover over a widget name and you will an option for “placement”. Selecting this option will open a placement configuration page. Options include, showing the widget above your content, below your content, in a WordPress widget (sidebar, footer etc.) and only showing it on certain types of pages like the homepage, category page or post pages.
Can I display Content.ad content in a sidebar or footer?
Yes. Set the placement for a Content.ad widget to “widget”. In your WordPress widget settings drag the Content.ad widget into your sidebar or footer area.
Does the Content.ad plugin work with Multisite?
Not at this time. Let Us Know if Multisite support is important to you.
Changelog
1.3.7
- Added call type to widget request to improve reporting
1.3.6
- Fixed JS error by replacing deprecated .live() with .on()
- Fixed active/paused bug
1.3.5
- Fixed content.ad login bug for Chrome
1.3.4
- Updated for WordPress 5.0
- Resolved conflict with plugins that append noticies containing h1 or h2 tags to the plugin
1.3.3
- Updated for WordPress 4.9.8
- Updated Settings WordPress Key button text to clarify which API key you should use
1.3.2
- Updated for WordPress 4.9.4
1.3.1
- Updated for WordPress 4.9
- Added notification link to review our plugin
- Bug Fixes
- Updated “Departure Page” widget placement label to “Exit Pop”
- Removed “Installation Instructions” button since all widgets can be placed with the plugin
- Fixed “Last Edited” date display bug in Firefox and IE
- Fixed Widget List button style conflict bug
1.2.12
- Bug Fixes
- Modal close button is now displayed on non-mobile devices less than 768px high
- Replaced hard coded path to plugin folder with WP hook
1.2.11
- Bug Fix: WordPress notifications will no longer cause the Content.ad logo to appear multiple times on the Widget List page
1.2.10
- Added support for popup widgets
- Added ability to use multiple template tags
- Added shortcode to allow placement inside a post or page
- Fixed conflict with other plugins to make sure modal is centered in the browser
1.1.18
- New widget code to improve reliability and security.
1.1.17
- You can now add new WordPress Tags using “Content.ad > Widgets > Placement > Exclude widget from tags”
- Updated placement labels to include “widget” for clarity
1.1.16
- Added Loading Indicator (Spinner)
- Made thickbox responsive
- Code clean-up
1.1.15
- Bug fixes
- Updated old links
- Fixed settings breakpoints
- Standardized variable names
- Fixed bug where Excluded Tags would not save
1.1.14
- Added Widget delete confirmation dialog box
- Changed Active/Paused Widget icons to plain text labels
1.1.13
- Updated Content.ad Widget Installation Instructions
- Clarified Popup or Mobile Slideup instructions (especially near placement options)
1.1.12
- Updated WordPress Key label in Settings page
- Added margin to iframe close icon
1.1.11
- Updated Content.ad logo & colors
1.1.10
- Updated for WordPress 4.4
- Removed extraneous <p> tags that wrapped Content.ad JS files
- Moved Content.ad JS to WordPress footer
1.1.9
- Updated for WordPress 4.3
- Fixed issues with the widget options:
- Missing buttons on plugin Widgets page
- Widget Placement settings bug
1.1.8
- Fixed: Plugin activation bug for new installations
1.1.7
- Updated for WordPress 4.1 compatibility
- Updated descriptions, documentation, plugin image, etc.
- Utilizing latest Content.ad widget call URL (widget.js -> widget.aspx)
1.1.6
- Updated for WordPress 4.0
1.1.5
- Updated for WordPress 3.9
1.1.4
- Fixed CSS for WP 3.8.1
- Update misc. URL links & dates
1.1.3
- Fixed issues with the widget options:
- Option to add/remove Content.ad from Home and Category pages
- Widget Placement settings bug
- Fixed modal resizing
1.1.2
- Added the ability to display ads using do_action(‘contentad’) within a theme file.
- Update misc. links and formatting
1.1.1
- Fixed issue where the featured image wasn’t being displayed in Content.ad widgets if set.
1.1.0
- Added support for pausing and activating Content.ad widgets.
- Added different Content.ad units in different WordPress widgets.
- Added options for showing on home and category pages.
- Added cron job to remove deleted widgets from the page.
1.0.3
- Moved banner to correct directory to enable it to display on wordpress.org.
1.0.2
- Added banner image for wordpress.org/extend/plugins.
1.0.1
- Fixed version number (was 1.0.0 dev instead of 1.0.0).
1.0.0