Pageviews, also known as visual views, track usage of the platform as part of your Builder subscription.
Pageviews tell you how many views you're getting on your site or app that contains visual content—content from a Page or Section model—created in Builder.
You can access Pageviews in Account Settings under the Subscriptions tab.
In some cases, specific elements and actions within Builder are exempt from counting toward your Pageviews, offering cost savings and flexibility.
Generating code
Generating code in the Visual Editor does not count toward your Pageviews. For information on how to generate code from your Pages and Sections, visit Generating Code with Visual Copilot.
Content from Data models
Content from Data models does not count toward your Pageviews, and are effectively free in this regard. For Data models, Builder only uses bandwidth metering.
Content from Page or Section models
Using visual models; that is Page or Section models with Builder's Visual CMS, which includes using the Builder SDKs and APIs.
Pageviews are tracked when you use a Page or Section model with Builder's Visual CMS and integrate with Builder's SDKs, the HTML API, or Qwik API.
Pageviews are recorded when a tiny (1x1) hidden image, called a tracking pixel, is rendered upon someone visiting your site or app.
If a single Page contains multiple content entries from Builder—such as two symbols—Builder ensures that these pixels are only counted once to avoid double counting by using a cache period in which the pixel request is cached in the user’s browser.
In this way, multiple pixel requests on the same Page from different Builder content entries only result in one tracking pixel request.
Technically, this method can result in undercounting Pageviews if a site visitor is navigating pages very quickly, but in most cases, this technique yields an accurate representation of Pageviews.
Consider an example of a Page that features three Builder Sections. When a user visits that Page, it counts as just one Pageview.
Builder ensures that the tracking pixel, used to record Pageviews, is only counted once even if there are multiple content entries—in this case, Builder Section models—from Builder on the same Page.
This is done to avoid double counting and multiple pixel requests from different Builder content entries on the same page result in only one tracking pixel request. In this way, it is considered as one Pageview regardless of the number of Builder Section models on that Page.
Builder Pageviews are similar to Pageviews in Google Analytics (GA). One visitor to one Page is one Pageview. The same visitor visiting two Pages on your site with Builder content equals two Pageviews.
Viewing or previewing your own content in the Builder app does not count as a Pageview.
If you aggregate all of your content in Builder by Page URL and compare Pageviews for those URLs in Google Analytics, the counts will be close. However, there could be differences for the following reasons:
- Google Analytics' tracking with JavaScript and Builder’s Pageview pixel are different mechanisms where tracking is invoked at different times.
- Depending on ad blockers or other browser extensions a user has, Google Analytics or Builder (or both) could fail to track a visit.
- Builder sets a long pixel cache time to make sure Pageviews are not overcounted. Depending on visitor behavior, this could lead to Builder undercounting total Pageviews.
For more information, read Understanding Impressions and then Impressions Compared to Page Views.
