TreStack Follow the build

Docs, Performance and themes

Running several timers at once

How many timers one page shows, which timer wins when several match, how app blocks add more, and how several timers share the monthly views.

All docsAsk a person
Category
Reference
Updated
26 September 2026
Applies to
TreStack Timer, every plan

What one page shows

In automatic positions, a page shows at most one bar, one product timer, one landing timer, and one cart timer. Timers in app blocks come on top of that, one per block. A timer that an app block already shows on a page is skipped at its automatic spot, so the same timer never appears twice.

When several product timers match a page, a tag timer beats a chosen products timer, which beats a collections timer, which beats an all products timer, and the older timer wins a tie. For landing timers, chosen collections beat all collections. Several product timers in automatic positions on one product page is planned, not built.

Countries

A timer targeted at chosen countries replaces a timer of the same type and placement set to all the world, for visitors in those countries. That is how to run one sale for most of the world and a different one for one market, without either showing twice.

Views are shared

A view is one timer seen by one visitor in a browser session, and the monthly views of a plan are counted per store across all timers. Reloads and other pages in the same session do not count again, but two different timers seen by one visitor count two views, so each extra timer adds to the allowance used. The app Home warns you at 80 percent of the month.

Auditing your timers, in four steps.

In order. Each step assumes the one before it is finished, so skipping one is how the last step fails for a reason that looks unrelated.

  1. Step one

    List what is published

    The timer list in the app, by type. Note the placement of each one.

  2. Step two

    Check for overlap

    Two product timers matching the same product means only one shows. Narrow one of them.

  3. Step three

    Use blocks for the extras

    A second timer on a page goes in an app block with a custom position.

  4. Step four

    Watch the views

    The app Home warns at 80 percent of the month. Unpublish timers that are not earning their place.

Settings reference

The controls this page touches, with what each one does and the default the app ships where there is one.

Bars per page
One in an automatic position.
Product timers per page
One in an automatic position, chosen by priority. More only through app blocks.
Landing timers per page
One in an automatic position. Chosen collections beat all collections.
Cart timers
One shows at a time, on the cart page and in the drawer.
App blocks
One timer per block. A timer shown in a block is skipped at its automatic spot on that page.
Views
Counted per store per calendar month, across all timers.

If this does not work

The failures most likely on this procedure, with the check that resolves each one. If none of them fit, we would rather have the store URL than a guess.

Send us the store URL
A published timer never shows

Another timer of the same type probably wins on those pages. Check the priority order above, then narrow the placement of the one that wins or move the other into an app block.

The views warning came early in the month

Every timer on every page view counts. Look at which timers sit on your busiest pages, unpublish the ones you can spare, or move to a plan with more views.

Keep reading

Performance and themes has 3 pages. The rest of the docs index is one click away.