AdSanity plugin review and common issues

AdSanity date-based ads should automatically stop displaying after their end date. If expired ads continue: (1) verify the ad type is set to “Date Based” (not “Infinite”) in the ad settings; (2) check that the WordPress timezone setting (Settings → General → Timezone) matches your expected time — a mismatch between server time and configured timezone can cause ads to expire at unexpected times; (3) clear all page and object caches — cached pages continue showing ads that have expired until the cache is rebuilt; (4) verify the end date is saved correctly by reopening the ad and checking the stored date.

AdSanity click tracking uses an AJAX call when an ad is clicked. If tracking is not working: (1) check if an ad blocker is intercepting the tracking AJAX call — test in incognito without browser extensions; (2) verify the WordPress AJAX URL is accessible — go to AdSanity → Settings and check the configured AJAX URL; (3) a security plugin may be blocking the AJAX tracking request — check for “blocked POST request” entries in security plugin logs; (4) test on the same device as the claimed clicks to verify the click tracking fires in your own browser environment.

A blank shortcode output indicates: (1) the ad ID is incorrect — verify the ID in AdSanity → All Ads matches the shortcode ID; (2) the ad is expired (past its end date) or not yet active; (3) the ad has no image/HTML content — open the ad edit screen and verify content is saved; (4) a plugin conflict is stripping shortcode output — test on a default WordPress theme with other plugins deactivated; (5) the ad is set to display in certain locations but the post type is excluded. Use [adsanity id=X show_if_expired=false] to verify display with explicit settings.

Go to AdSanity → Add New Ad. Upload the advertiser’s banner image or paste their ad code in the HTML field. Set Ad Type to “Date Based.” Configure the Start Date (campaign start) and End Date (30 days later). Add the ad to the desired widget area, or copy the shortcode [adsanity id=X] and place it in the post or page where the ad should appear. The ad automatically displays starting on the Start Date and stops appearing after the End Date — no manual intervention needed to pause the campaign at expiry.

Ad rotation in AdSanity requires the Ad Groups add-on. After installing: go to AdSanity → Ad Groups → Add New Group. Name the group and add the ads to include in the rotation. Each time the group’s placement is displayed, one ad from the group is shown based on the configured rotation method (random or sequential). Use the group shortcode [adsanity_group id=X] to place the rotation wherever needed. Rotation groups are useful for A/B testing different advertiser creatives or rotating multiple advertisers in a single ad slot.

AdSanity’s campaign management workflow (date-based scheduling, per-ad statistics, clean advertiser-focused reporting) is more purpose-built for direct ad sales than Advanced Ads, which is more oriented toward programmatic network ad management. For a local news site with 5-20 direct advertising clients, AdSanity’s simplified ad management and built-in campaign scheduling is a better workflow fit. For a site running primarily AdSense, Media.net, or other network ads with complex targeting, Advanced Ads’ network integration and visitor targeting are more valuable.

AdSanity supports Google AdSense through a dedicated add-on (AdSense add-on) that allows connecting an AdSense account and placing AdSense ad units within AdSanity’s management interface. Without the add-on, AdSense code can still be manually pasted into AdSanity’s HTML ad field as a custom HTML ad — but auto-optimization features and AdSense-specific formatting require the dedicated add-on.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.