All 20 Countdown Timer sections
Where it shows
Placement takes any combination of:
- Product pages — under the price, above the add-to-cart button.
- Shop and category listings — under each product's price in the grid, drawn small so it cannot push the layout about. On a block theme it sits under the price block and takes the price's alignment, so in a centred card it is centred too, and it keeps counting when the shopper moves to the next page of the grid without a page load.
- Bar across the top of the site — the highest campaign in the list with this placement, and only one, because two bars fight for the same strip.
- Above post and page content — everything that is not a product. It goes once, above the text of the post or page being read. Excerpts, the post's embed card, the other posts a page or template lists, and a content block a shortcode puts inside the article are left without it.
Apply to narrows it to a category, a tag or particular products, chosen by name rather than by ID. A parent category covers everything inside it. Exclude products always wins. Narrowed to categories, tags or products with nothing chosen, a campaign covers no product at all, and the Campaigns list says No products chosen rather than Live.
Which campaign wins#
When two campaigns could show in the same place — two covering one product, or two with the bar — the one higher in the Campaigns list is the one that shows. Use the up and down arrows in the list's Order column to move a campaign, so an offer for one category sits above the one for the whole shop.
Duplicate, at the foot of a campaign, copies it as last saved into the row below, named "(copy)" and switched off, so it can be changed before it shows anywhere.
And which pages#
Placements say where on a page a timer goes; page rules say which pages it is allowed on at all. Leave Pages set to Everywhere on the site and a campaign is limited only by its placements. Choose Only what I choose below and you get three lists, all built from your own site:
- Places — the front page, the blog index, search results, the 404, and, with WooCommerce, the shop, the cart, the checkout and the account pages.
- Post types — any single product, post or page, including any post type of your own.
- Archives — product categories, tags, and any taxonomy of your own.
Common exclusions ticks the places most often left out — the cart, the checkout, the account pages. A place chosen above, or chosen for you by a preset, cannot be ruled out here: it greys out rather than cancelling itself.
Excluded pages always wins, and is the quickest way to say the thing most shops want: a sale bar everywhere except the checkout.
Excluded addresses takes one address per line, written as the part after your domain name, with standing for anything — the same shape you already know from redirects. /account/ keeps it off every page under /account/. It is matched against the path only, so it works whatever your domain is, and it is not a regular expression: a mistyped one is a rule that matches nothing rather than a rule that matches the site.
You can paste an address straight from the browser, letters from other alphabets included. Earlier versions saved such an address as // (the front page), //* (every page) or /, or with letters missing; a line saved like that keeps doing what it did, so if the box holds one you did not mean, delete it and paste the address again.
And who sees it#
Devices limits a campaign to desktop, tablet or mobile. Leave all three clear for every size. It is decided by the width of the window rather than by guessing from the browser, so a narrow desktop window counts as narrow and the answer survives page caching.
Login status limits it to people who are signed in or signed out. Tick Signed in and User roles appears underneath — the role list is your own site's. A role is something only a signed-in visitor has, so the question is not asked until it can be answered.
There is no schedule here: a campaign already has its own dates, and a second set beside them would only be a way to contradict the first.
Still stuck? Ask the developers who wrote it. We aim to reply within one business day.