Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
promptless-for-oss wants to merge 1 commit into
base: 7.2
Choose a base branch
from
Draft

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/points/points.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,25 @@

4. Click **Save** or **Save & Close**.

Visits specific URL
===================

The 'Visits specific URL' action awards Points when a Contact visits a URL that matches an address you specify. When you choose this action from 'Actions taken by User', Mautic displays these fields:

* **Page URL** - The web address to track. Enter the full URL, including ``http://`` or ``https://``. Use ``*`` as a wildcard to match part of the address - for example, ``https://example.com/pricing*`` matches the pricing URL with any query string.

Check warning on line 48 in docs/points/points.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.

Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.", "location": {"path": "docs/points/points.rst", "range": {"start": {"line": 48, "column": 5}}}, "severity": "INFO"}

* **Total time spent** - Awards Points once the Contact has spent at least this much time on the matching URL across all their visits.

* **Page hits** - Awards Points once the Contact has visited the matching URL at least this many times.

Check warning on line 52 in docs/points/points.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.

Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.", "location": {"path": "docs/points/points.rst", "range": {"start": {"line": 52, "column": 5}}}, "severity": "INFO"}

* **First visit only** - Awards Points only on the Contact's first visit to the matching URL.

* **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.

Check warning on line 58 in docs/points/points.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.

Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.", "location": {"path": "docs/points/points.rst", "range": {"start": {"line": 58, "column": 25}}}, "severity": "INFO"}

@promptless-for-oss promptless-for-oss Jul 17, 2026

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


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

Check warning on line 60 in docs/points/points.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.

Raw Output:
{"message": "[Mautic.FeatureList] Is this referring to a Mautic feature? If so, use 'Landing Page' instead of 'Page'.", "location": {"path": "docs/points/points.rst", "range": {"start": {"line": 60, "column": 120}}}, "severity": "INFO"}

@promptless-for-oss promptless-for-oss Jul 17, 2026

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


.. vale off

Point Triggers
Expand Down
Loading