Skip to content


Dimensions of statistics

Time and count of visits will be grouped and aggregated by unique domain and date. It means that date and domain constitutes the smallest statistical granularity.

And this tool supports you to merge basic records according to your own needs.

As above, this data is aggregated by domain. For example, and are counted as 2 records. If you want to see aggregated data from the two sites, you'll need to merge them manually.

Most data display pages support merge queries. And you can customize merge rules on the backend page.

What's rules look like?

The rule consists of two parts, the source part and the target part. The source part declares which sites hit the rule, and the target part defines how those sites are merged. For example, >>> is a common rule, the left is the source part, and the right is the target part.

How to define the source part?

The source part can be a specific domain name or an Ant expression. Below are some examples.

Source partExamples of hit sites can hit this rule*

How to define the target part?

The target part can be a specific domain name, a positive integer, or be left blank. They will be introduced one by one in conjunction with the source part in the table below.

Source partTarget partLookRemark** >>> google.comSites hitting* will be merged into the specific >>> Not won't be merged cause of blank target part
**.*.google.com3**.* >>> Keep Level 3Sites hitting **.* will be merged into the last 3 level domain names

The following table is some merge examples after setting the above rules together.

Original siteHit rulesMerged site and remark* >>>* >>>* >>> >>> Not Merge (1)**.* >>> Keep Level**.* >>> Keep Level (2)


(1) When multiple rules are hit, the source part takes precedence for a specific domain name

(2) Merge to the before level of Public Suffix List when no rules are hit