Pulse receives URL paths for each page that your users visit on your site. Due to the common use of REST routes or other schemes, duplicate Pages would be created by default for the same view. Using a common forums web application example, the
http://foo.com/thread/2 otherwise show up as two Pages inside Pulse, when really they are two instances of the same Thread view.
By default, Pulse replaces both integer path segments and DateTime strings with the wildcard character
*. Thus, the above two page views would be bucketed beneath the single Page
You can add new rules on the Pulse -> Settings page:
Any new or deleted rules are saved whenever you click 'Add Rule' or the delete button beside a rule.
Any changes to the two rule lists documented below may take up to 15 minutes to be reflected by new pages in the Pulse dashboard.
This allows you to add your own path segment wildcards for your routing scheme, if you have non-integer segments that can change for the same view. For instance, if you add a new row to the Grouping URL rule list containing this:
Page visits for the routes
http://foo.com/forum/bar will show up beneath the same Page in Pulse.
These can be made more specific. This grouping rule:
will turn pages visit to
If you want routes containing integer path segments to appear un-wildcarded, you can disable the default integer wildcarding by adding to the Ungrouping rule list on the Pulse Settings page. For instance:
Visits to the above two routes would show up as two Pages inside Pulse, while a visit to
http://foo.com/thread/3 would show up under
If you want to mass-ungroup segments all URLs that match a rule, you can do so by have an ungrouping rule with a wildcard character:
All pages such as
/thread/2 etc. will appear as their own pages in Pulse.
Subdomains can also be grouped or ungrouped in the same way as the segments above. If you have multiple domains that each serve the same pages, you can set these up to be (un)grouped using rules such as:
The protocol and domain is optional
Don't care about matching by the protocol/domain that your pages have? You can also add rules with just the path, e.g:
Mixing ungrouping with grouping
You can have ungrouping rules coexist alongside grouping rules. Ungrouping rules take precedence over (AKA override) grouping rules. For instance, this ungrouping rule:
Combined with this grouping rule:
Will cause the following two pages:
To appear in Pulse as this one page: