Advanced Ads enables you to schedule ads using the start and expiry date or show them on specific days of the week only.
Table of Contents
Start & expiry date
You find both settings in the top right corner of your ad edit screen, right where you would publish your ad.
The start or publish date is automatically set to the time you published the ad. By clicking on “Edit” you can also change this date into the past or future.
To set an expiry date you first have to enable the “Set expiry date“ checkbox. You can now set the expiry date.
The expiry date is the first day when the ad will not be visible in the frontend anymore.
If you let ads expire and don’t want to use them again you should move them to the trash later. This is not necessary but will remove it from all queries and condition checks in the frontend and therefore bring a slight performance bonus.
Show ad by day of the week
Advanced Ads Pro allows you to show ads only on specific days of the week.
This option is also available in the Publish meta box. Enable it and choose the days. You can select multiple days holding down the CTRL button on Windows, or Command on Mac while selecting the days.
What else you need to know
The dates are compared against the blog time and not the user’s local time. For example, if your blog uses UTC+0 and your expiry date is January 28th, visitors in UTC-2 will still see it on Januar 28th at 2 am (their local time), and visitors in UTC+2 won’t see it after January 27th 10 pm.
Depending on your localization, the order of the input fields might vary.
The start time is technically the post date of the ad, so any plugin that somehow interferes with the post date might also affect the start date. This means that ads are scheduled using WP Cron. If your ads are not scheduled then make sure that WP Cron is working properly.
The expiry date is checked before an ad is displayed and therefore updated in real time. If the ad does not expire at the right time, make sure that you have the correct time zone set up and your cache is either disabled or you are using cache-busting.