MetaLocator charges for services in proportion to our customer's utilization of our services. This is often expressed as the total number of "page views" incurred. This most accurately reflects our costs to deliver service and is an important measure when sizing the infrastructure dedicated to your account. The meaning of a "page views" can vary in certain contexts. This document defines those contexts.
In general, a "page view" is incurred when MetaLocator queries the database based on a user action and delivers those results to the user.
For example, a single page view is incurred in each of the following example scenarios:
A user visits your Web site and our locator is displayed.
A user searches your locator and we present the results.
A user clicks to display a Location Landing Page.
The Nearby Widget displays the nearest locations.
A call to our PaaS API is executed.
A call to our Data Management API is executed
A call to our Analytics API is executed
A text message is delivered by MetaLocator that includes location results.
An email is delivered by MetaLocator that includes location results.
A user drags the map to display additional search results.
One user can generate multiple page views by performing multiple searches in some configurations, however most user sessions generate a one or two page views. Our internal use of cache avoids incurring repeated page views in various scenarios where one user performs the same query twice in the same session.
Page views are not incurred in these scenarios:
We render a "Where to Buy" button on your Web site.
A search form is displayed on your Web site as described here.
A mobile app that uses our API is loaded, but no queries are sent to our API.
A text message is received by MetaLocator.
A complete reporting of your page views can be found under in the MetaLocator dashboard under Account Usage. Questions regarding your account, or your page views can be directed to our helpdesk.