How do you know if your blog has the best AdSense configuration?
The AmpedSense plugin allows you to split test ads to find the most profitable AdSense setup.
- Optimize ad placement – Do you know if it’s better to place your ads above or below your content? In the sidebar? What about embedded within your articles? Test various standard positions as well as custom positions with our widget.
- Optimize ad size – There are 18 different ad sizes (that’s a lot!). Does bigger get you more revenue?
- Optimize ad type – Display ads vs text ads vs link units? Which give you the most earnings?
- Optimize ad colors – Stick with Google’s default, or try to match the color scheme of your own site?
- Easy to use – No need to insert code or modify any html files. Just upload the plugin and everything’s done through a simple settings panel in wordpress.
- Integrated reporting – Easily view stats within wordpress (we’ll pull the essential analytics from AdSense automatically), or go direct to AdSense and run custom reports.
- Test unproven AdSense ads – Google just released a new ad type? Test beta ad units (such as their new ‘responsive ads’) before they’re proven.
- Multiple tests for different content – Want to run some ads on pages, and another set on posts? No problem. Want to place specific ads on your homepage vs the rest of your site? Simple.
- Exclude specific pages/posts – No one wants ads on their contact page. Easily choose which pages or posts to exclude from receiving ads.
- Desktop vs Mobile – Do responsive ads work better on mobile than on desktop? Segment different ads to run on your mobile traffic.
Learn more at http://www.ampedsense.com/
Take a tour
Read some success stories
Optimization tips on the AmpedSense blog
AmpedSense follows standard plugin procedures:
- Install automatically through the wordpress plugin directory, or manually by uploading amped-sense.zip to the
- Active o plugin no menu Plugins
- Click on the AmpedSense menu item in your left sidebar menu
- Before anything can be done, AmpedSense must know about your AdSense account. It will ask you to authenticate using the Google account AdSense is set up under. This grants read-only permission so that ads can be credited to your account and click, rpm, and earnings stats can be shown for your split tests.
- A walkthrough of creating your first split test can be found here: http://www.ampedsense.com/creating-adsense-split-test-in-wordpress/
AmpedSense is compatible with almost all themes and plugins. A few exceptions noted:
- Placing ads within content does not work when a theme is using its own editor, such as with Thrive Visual Editor and OptimizePress.
- Who is this for?
Anyone who wants better earnings from their wordpress site with Google AdSense.
Many people are disappointed by how little they earn when they first place Adsense on their blog. I felt the same way. But if you’re willing to try a few configurations and have a little bit of patience, I promise you’ll be surprised.
Have a blog or wordpress site? Check. Have an AdSense account? You’re in.
- Do I have to be technical?
No! AmpedSense requires no code or html experience. If you can use WordPress and run your blog, you can run AmpedSense.
- How long does it take to find the optimal AdSense configuration?
Test length depends on your traffic and number of variants you’re testing. A simple test between 2 positions can be run in a matter of days. Larger tests may take weeks, but the more traffic you have the quicker you’ll complete the split test.
- Will it make my site ugly by adding lots of ads?
Unlike other ad testing platforms, you are in complete control of what you choose to test. You decide what you want to test, and you can easily preview every configuration before they go live. Only add as many ads as you’re comfortable with (In fact, you’ll probably find out that after a certain number additional ads don’t earn you more).
Contribuidores e programadores
“AmpedSense – AdSense Split Tester” é software de código aberto. As seguintes pessoas contribuíram para este plugin:Contribuidores
Interessado no desenvolvimento?
Registo de alterações
- Fixing calendar bug (year 2022)
- Minor bugfix for Shortcode D/E
- Support for HTTPS
- Fixed Shortcode D, E, F rendering
- Cleared up Publisher ID confusion
- Compatible with WordPress 4.6
- Increased from 6 to 10 ad units per recipe (premium users)
- Fix color bug in Admin area
- Added ability to notate recipes
- Increased support for PHP 5.2
- Fixed bug in category detection (Thanks Dan!)
- New AmpedSense forums
- Media query mobile detection
- Fix ‘ADEND’ bug on empty articles
- PHP tag bug fix
- Better mobile detection again
- Support for older versions of PHP (<5.3)
- More accurate mobile detection
- Default date for reporting adjusted
- Better explanation of ad recipe
- Minor bug fix for cloning recipes
- Minor bug fix when no recipes in segment in client-mode
- Cache friendly mode officially stable (with mobile detection based on screen resolution instead of browser)
- More consistent injection within content
- 3 more widget positions
- 3 more shortcode positions
- Cache friendly hints
- Fixed rare login issue on settings page
- Better reporting on extremely large sites
- More efficient Google API calls
- Fixed error when creating segments on sites with more than 5,000 posts
- Client side render mode option (BETA) – Cache friendly!
- New segment types – Category Lists and Specific Category List
- Bug fixes: segment naming, date picker
- Premium features unlocked
- Added better Google login handling
- Fixed issue with editing segments creates a new one
- See updated status of your actions
- Added ‘every url’ as segment option
- switched to wp’s internal wp_get_file_contents
- fixed ‘segment deleted’ message when toggling segment
- updated status message background color
- Clone recipe (into other segments as well)
- Shortcode without additional shortcode plugin
- Both Padding and Margin can be specified (previously just padding)
- 6 new ad sizes (including responsive!)
- Better mobile detection (phone vs tablet), plus more mobile segments
- Hide segments not being used
- Various bug and security fixes
- Introduced segments
- Easier authentication
- Initial version