How a timer trigger works
You set an interval, measured in milliseconds, and a limit on how many times it may run. When a visitor lands on a page that matches the trigger’s conditions, the clock starts. Each time the interval elapses, the trigger fires and any attached tags send their event, until the limit is reached or the visitor leaves.
Conditions decide where the clock runs at all, and they matter more here than with most triggers. Left unrestricted, a timer runs on every page in the site, including ones where time spent means nothing — a thank-you page, a login screen, a directory listing someone is scanning.
Why it matters
Time is the crudest available proxy for interest, and sometimes it is the only one you have. On a long guide with no form and no clicks, a visitor who stays is behaving differently from one who bounces straight back to the results page, and a timer is a simple way to separate them.
It is also useful for things that are meant to happen after a pause rather than after an action: showing a chat prompt to somebody still reading the pricing page, or holding a remarketing tag back so it only picks up people who lingered instead of everyone who glanced.
Where timer triggers go wrong
A timer measures elapsed time, not attention. A tab left open in the background while somebody makes tea keeps counting, and a phone put in a pocket mid-page counts too. Set the interval short and repeat it freely and you will manufacture an engaged audience out of abandoned tabs.
The second problem is duplication. GA4 already measures engaged sessions and engagement time in its own way, so adding a homemade timer usually produces a second, conflicting set of numbers with no clear owner. Whoever reads the report a few months later will not know which one to believe. Repeating timers also generate a great deal of event volume for very little insight.
How to use it well
Reach for a timer only when you have a specific job for it, and prefer GA4’s own engaged session measurement for ordinary reporting. Where you do use one, restrict it to the pages that justify it, choose a single interval long enough that a distracted tab is unlikely to qualify, and cap the repetitions rather than letting it run indefinitely.
Test it the way a visitor would behave rather than the way you behave, including on a phone with the screen locking, and check what the extra events do to your GA4 reports before publishing. If a timer event ever needs to influence spend, be honest that it represents patience and nothing more — keep it out of the conversion actions in your analytics and tracking setup that automated bidding learns from.