How often (scopes)

Every event on a page has a “how often” setting. It answers the question most tracking setups never ask: when this condition is true again, should the event fire again?

How oftenReload re-firesComing back re-firesKeyed onTypical use
Every time alwaysyesyesnothingRare. Clicks that are genuinely repeatable actions.
Once per page view pageviewyesyesthis page loadDefault for clicks and submits.
Once per visit revisitnoyesthe previous pageDefault for page loads. A step viewed, reloaded, viewed again counts once until the visitor leaves and comes back.
Once per session sessionnonothe browser tab sessionInitiateCheckout on the first funnel step.
Once per visitor visitornonothe visitorLead / CompleteRegistration on the final step.
Once per thing entitynonothe visitor + a valueViewContent once per product, plan or vehicle id.

“Once per visit” and the previous page

revisit remembers which page the visitor was on before this one. A reload, or arriving again from the same page, does not re-fire; arriving from somewhere else does. That is why each funnel step must be its own page: two steps sharing one page share one key, and moving from one to the other looks like a reload.

“Once per thing”

entity keys on the visitor plus a value you choose — for example {{url:product_id}} from the query string or {{attr:data-product-id}} from the element that triggered the event. Each distinct value fires once.

Event parameters

ValueReads from
{{url:name}}the query string
{{attr:data-name}}the element that triggered the event, or the first match on the page
anything elseused literally

Parameter names ending in _ids are sent as a list.

Triggers

  • When the page loads.
  • When something is clicked or when a form is submitted, by CSS selector.
  • When the site signals it — from a binding, or from your own code with StepCount.emit('Lead') (the plugin's JavaScript API keeps its original name, StepCount).