Skip to content

docs: Document Visits specific URL Point Action options and cumulative time behavior - #854

Draft
promptless-for-oss wants to merge 1 commit into
mautic:7.2from
Promptless:promptless/pr-16606-visits-url-point-action
Draft

docs: Document Visits specific URL Point Action options and cumulative time behavior#854
promptless-for-oss wants to merge 1 commit into
mautic:7.2from
Promptless:promptless/pr-16606-visits-url-point-action

Conversation

@promptless-for-oss

Copy link
Copy Markdown
Contributor

Open this suggestion in Promptless to view citations and reasoning process

Adds a 'Visits specific URL' subsection to the Points page documenting the action's options (Page URL, Total time spent, Page hits, First visit only, Returns within/after). Clarifies that 'Total time spent' and 'Page hits' are cumulative across the Contact's visit history and award Points on the next tracked hit once the threshold is crossed — no revisit of the specific URL required — reflecting the fix in mautic/mautic PR #16606.

Trigger Events


Tip: Filter the Dashboard by labels or assignees to focus on what matters to you 🔎

Comment thread docs/points/points.rst

* **Returns within** and **Returns after** - Award Points when the Contact returns to the matching URL within, or after, the time period you set.

'Total time spent' and 'Page hits' measure cumulative activity on the matching URL. Mautic evaluates them against the Contact's full visit history for that URL, so it awards the Points on the next tracked hit after the Contact crosses the threshold. The Contact doesn't need to revisit the specific URL. Because Mautic measures time spent from the tracking script, the Contact has to load another tracked URL before the most recent visit's time counts.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documented the cumulative behavior of 'Total time spent' (accumulative_time) and 'Page hits' (page_hits) from PR #16606, which rewrote validateUrlHit in PointActionHelper.php to evaluate these dwell-time conditions against the Contact's historical visit stats even when the current hit URL doesn't match — so Points are awarded on the next tracked hit after the threshold is crossed, without requiring a revisit of the specific URL.

Source: mautic/mautic#16606

Comment thread docs/points/points.rst

'Total time spent' and 'Page hits' measure cumulative activity on the matching URL. Mautic evaluates them against the Contact's full visit history for that URL, so it awards the Points on the next tracked hit after the Contact crosses the threshold. The Contact doesn't need to revisit the specific URL. Because Mautic measures time spent from the tracking script, the Contact has to load another tracked URL before the most recent visit's time counts.

The remaining options describe a single visit, so Mautic applies them only when the Contact's current hit matches the 'Page URL'.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documented that 'First visit only' (first_time), 'Returns within' (returns_within), and 'Returns after' (returns_after) still require the current page hit to match the configured URL. In the reworked validateUrlHit, these current-visit conditions remain gated behind the fnmatch($limitToUrl, $url) URL check, whereas the dwell-time conditions were moved outside that gate.

Source: https://github.com/mautic/mautic/pull/16606/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants