1. What exactly does it mean when the plugin says it increases Google AdSense API calls? Does this directly translate to higher earnings for my website, or does it simply mean I can manage more ads or updates?
2. What are the key differences between using AdSense’s built-in automatic ad placement and using Ad Commander as a middleman? What specific advantages would my website gain by implementing Ad Commander instead of relying solely on AdSense’s automatic option?
Hi, I’m currently using Advanced Ads. It works well, it’s very easy to use, very logical, but it’s a bit bloated. How does your tool stack up compared to Advanced Ads in terms of ease-of-use, feature set and load speeds?
A: Thanks for the question. We have some overlap with Advanced Ads and similar plugins. The general idea is the same, and the data structure is similar (ads, groups, automatic placements).
Ad Commander's overall interface is a little more WordPress-y. You'll use a regular classic post interface and regular taxonomy interface for managing your ads.
A: It would really depend on how the headless website is made. Ad Commander does not have REST API at this time, but I suppose the headless website could render the HTML from the ads. It would also have to load the Javascript from the plugin.
I just meant that the plugin has its own Javascript, which is automatically loaded on a normal WordPress site, so the developer would need to make sure to load the plugins' Javascript. But this is all beyond the scope of the plugin, and I am unsure if it would work or not.
It is unlikely. This is strictly a WordPress plugin - meaning frontend and backend. If you are using a different frontend it is possible a developer could find a way to make it work with that unique frontend, but it is not something we would be able to provide support for.
Q: Presale question
1. What exactly does it mean when the plugin says it increases Google AdSense API calls? Does this directly translate to higher earnings for my website, or does it simply mean I can manage more ads or updates?
2. What are the key differences between using AdSense’s built-in automatic ad placement and using Ad Commander as a middleman? What specific advantages would my website gain by implementing Ad Commander instead of relying solely on AdSense’s automatic option?
Share Ad Commander
Q: Any plans to add FluentCommunity?
110442266921555066618
May 23, 2025A: Not as of now, but we'll take a look at what would be involved.
Share Ad Commander
Q: This versus Advanced Ads
Hi, I’m currently using Advanced Ads.
It works well, it’s very easy to use, very logical, but it’s a bit bloated. How does your tool stack up compared to Advanced Ads in terms of ease-of-use, feature set and load speeds?
110442266921555066618
May 18, 2025A: Thanks for the question. We have some overlap with Advanced Ads and similar plugins. The general idea is the same, and the data structure is similar (ads, groups, automatic placements).
Ad Commander's overall interface is a little more WordPress-y. You'll use a regular classic post interface and regular taxonomy interface for managing your ads.
There are a few of the higher-end features...
Share Ad Commander
Q: Does it work with bbPress and BuddyPress?
Does Ad Commander work with bbPress and BuddyPress?
110442266921555066618
Edited May 20, 2025A: bbPress and BuddyPress integrations are now available in Ad Commander Pro 1.1.10.
Share Ad Commander
This integration has now been released.
Q: Is there a way to use this on a headless website?
110442266921555066618
Apr 27, 2025A: It would really depend on how the headless website is made. Ad Commander does not have REST API at this time, but I suppose the headless website could render the HTML from the ads. It would also have to load the Javascript from the plugin.
Share Ad Commander
You're saying that HTML embedding alone won't work, so we need to add the JavaScript as well, right? Do you provide the code for that JavaScript?
I just meant that the plugin has its own Javascript, which is automatically loaded on a normal WordPress site, so the developer would need to make sure to load the plugins' Javascript. But this is all beyond the scope of the plugin, and I am unsure if it would work or not.
I am planning to move away from WordPress as a front-end for a headless CMS, so I would like to know if you plan to support this.
It is unlikely. This is strictly a WordPress plugin - meaning frontend and backend. If you are using a different frontend it is possible a developer could find a way to make it work with that unique frontend, but it is not something we would be able to provide support for.
ok, thank you!