MetaLocator displays an aggregate monthly page view utilization figure for your account.
This number represents more than visits to your locator: it combines locator page views with API and integration activity recorded during the previous calendar month.
The elements considered a Page View, as measured for the purposes of account utilization, are described here.
This article explains what is included, where to find each component in your Analytics dashboard, and how to understand changes over time.
What is included in monthly utilization?
Your monthly utilization is calculated as the sum of the following events:
Page Views
REST API calls
Zapier API calls
Page Views recorded while browser analytics were disabled
Legacy PaaS API calls
Legacy XMLRPC API calls
Each page view or qualifying event above contributes one unit to the monthly total.
Locator page views
This is the number of page views recorded for your MetaLocator implementation. A page may be viewed more than once during the same visit, so this number is generally slightly higher than the number of visits, unique visitors or unique page views.
API and integration activity
The following Analytics Event Actions are also included:
Analytics Event Actions | Activity represented |
| Requests made through the MetaLocator REST API |
| Requests made through the legacy XMLRPC API |
| Activity generated through MetaLocator’s Zapier integration |
| Activity recorded through supported platform or application integrations |
| Page views recorded when normal browser-based analytics collection was disabled |
These events are added to page views to provide a more complete representation of account usage.
Viewing Utilization in the Analytics Dashboard
Page views are tracked in MetaLocator's internal analytics system. When analytics are disabled via opting out an anonymous page view action is still recorded.
Selecting the correct month in the Analytics Dashboard
Before reviewing the details, confirm that the Analytics Dashboard is displaying the correct website and month.
Open your MetaLocator analytics dashboard.
Open the date selector at the top of the dashboard.
Select Month as the reporting period.
Choose the month you want to review.
For the current month, the Analytics Dashboard displays activity accumulated from the first day of the month through the present day. Previous months represent complete calendar months.
For example, when reviewing July on July 15, the total includes July 1 through July 15. It will continue to increase as additional activity is recorded through July 31.
Finding locator page views
In the Analytics Dashboard, Page Views are represented in various widgets. The Visits Overview report displays them as both a graph over time and a summary.
Use Pageviews, not Visits, Unique Visitors, Unique Pageviews, Entrances, or another engagement metric.
Depending on your dashboard configuration, the overall page-view count may also appear in a Page Titles widget.
Finding API and integration activity
To find the remaining components:
Open Behavior or Actions.
Select Events.
Open the Event Actions report.
Look for the following rows:
RESTXMLRPCZapierPaaSDisabledAnalyticsPageView
Your account may not be generating any or all of these Events, depending on your actual utilization.
Use the Events count for each row. Add these event counts to the Pageviews total to reproduce the monthly utilization displayed by MetaLocator.
Example calculation
Suppose the Analytics Dashboard reports the following activity:
Component | Monthly count |
Pageviews | 42,500 |
REST | 3,200 |
XMLRPC | 400 |
Zapier | 175 |
PaaS | 1,000 |
DisabledAnalyticsPageView | 725 |
Total monthly utilization | 48,000 |
The utilization shown in MetaLocator would be 48,000.
Understanding DisabledAnalyticsPageView
Some implementations disable normal browser-based analytics collection, either through an interface setting or an analytics opt-out option.
These page views are not ordinary browser-tracked page views, they are off-line analytics events triggered specifically when browser analytics are disabled. MetaLocator records them separately as the DisabledAnalyticsPageView event so that account utilization remains accurate even when detailed visitor analytics are unavailable.
To find this activity, open the Event Actions report and locate the DisabledAnalyticsPageView row.
Seeing how utilization changes over time
The current-month figure is cumulative. It normally increases throughout the month as people use your locator and integrations make requests.
To investigate the trend:
Select the current month in the date selector.
Open the relevant page-view or event report.
Change the report graph to a daily view, when available.
Use the row-evolution or historical graph option for an individual page or event action.
Compare the current month with the previous month or the same month in the prior year.
When comparing months, keep in mind that a current partial month should not be directly compared with a completed month without accounting for the number of elapsed days.
For example, 50,000 units recorded halfway through a 30-day month could indicate projected utilization of approximately 100,000 units if activity continues at the same rate.
Investigating an unexpected increase
When utilization increases unexpectedly, review the components separately.
Page Views increased
Check whether:
More visitors are using your locator.
The locator was added to additional pages or websites.
A marketing campaign increased traffic.
Automated traffic or crawlers are repeatedly loading locator pages.
A page is reloading or initializing the locator more often than expected.
REST or XMLRPC activity increased
Check whether:
A new API integration was launched.
An existing integration is polling more frequently.
A scheduled synchronization is processing more records.
Failed requests are being retried repeatedly.
API credentials are being used by more than one application.
Zapier activity increased
Review recently enabled or modified Zaps, especially workflows that run once for every record, lead, location, or scheduled synchronization.
DisabledAnalyticsPageView increased
This can indicate that more page views are being recorded without normal browser analytics. Review recent changes to analytics settings, consent-management rules, opt-out parameters, or embedding configurations.
Why the Analytics Dashboard totals may not match other analytics platforms
MetaLocator utilization should not be expected to match Google Analytics, Adobe Analytics, or another analytics platform exactly.
Differences can occur because:
MetaLocator includes qualifying API and integration events.
Some page views are recorded server-side.
Browser tracking may be blocked by consent settings, privacy tools, or content blockers.
Other platforms may use different definitions for views, sessions, users, and events.
The selected website, timezone, or date range may differ.
For the closest comparison, use the MetaLocator-provided the Analytics Dashboard dashboard, select the same calendar month, and combine page views with the five event actions described above.
Troubleshooting a discrepancy
If your calculation does not match the utilization shown in MetaLocator, verify the following:
You selected the correct the Analytics Dashboard website.
The reporting period is set to Month.
You selected the same calendar month shown in MetaLocator.
You used Page Views, rather than Visits or Unique Pageviews.
You included all five qualifying event actions.
You used the total event count for each action.
No report segment or filter is active in the Analytics Dashboard.
If a discrepancy remains, contact MetaLocator Support and include the month being reviewed, the page-view total, and the counts shown for each qualifying event action.