{"id":9071,"date":"2026-08-24T21:57:45","date_gmt":"2026-08-24T21:57:45","guid":{"rendered":"https:\/\/metaphaze.com\/gazettebuilder\/?page_id=9071"},"modified":"2026-08-24T22:01:10","modified_gmt":"2026-08-24T22:01:10","slug":"feature-reader-metrics","status":"publish","type":"page","link":"https:\/\/metaphaze.com\/gazettebuilder\/feature-reader-metrics\/","title":{"rendered":"Feature: Reader Metrics"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Sequential Stories create a useful question for a worldbuilder: are readers actually moving through them?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder can record simple aggregate progression events from Story activity without creating individual reader profiles or maintaining a server-side history of what each visitor has read.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The goal is not general website analytics. It is to provide a focused view of how sequential material is being used.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Story Progress as Aggregate Events<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder can count progression events such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Story Started<\/strong><\/li>\n\n\n\n<li><strong>Entry Reached<\/strong><\/li>\n\n\n\n<li><strong>Entry Completed<\/strong><\/li>\n\n\n\n<li><strong>Story Completed<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These are aggregate counts rather than individual reader records.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a Story might show:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Story Started: 148Entry 1 Completed: 132Entry 2 Completed: 117Entry 3 Completed: 103Story Completed: 91<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That gives the author a useful picture of where readers continue, where participation drops off, and how many progression events reach the end of the sequence.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Metrics Follow Story Actions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Reader Metrics are tied to meaningful Story progression rather than ordinary page loading.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Refreshing an Entry, following a bookmark, or revisiting a page should not automatically count as new progress.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, metrics can be recorded when the reader performs actions that advance the Story, such as starting the sequence or using its Continue or Next controls.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This keeps the numbers focused on progression rather than raw traffic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">No Individual Reader Profiles<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder does not need to know who a reader is in order to count Story activity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The metrics system records aggregate events such as:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">EXP-01Story Started: 52Position 1 Reached: 49Position 1 Completed: 43Position 2 Reached: 41Story Completed: 28<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">It does not need to store a server-side record such as:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Reader 3847Read Entry 1Read Entry 2Stopped at Entry 3Returned three days later<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That distinction is intentional.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Reader Progress helps an individual browser remember where it left off. Reader Metrics tell the site owner how Stories are being used overall.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding Where Readers Continue<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aggregate progression becomes particularly useful across a multi-step Story.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Suppose a Story contains six sequential Entries:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Story Started       200Entry 1 Completed   184Entry 2 Completed   171Entry 3 Completed   165Entry 4 Completed   121Entry 5 Completed   116Story Completed     108<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The noticeable decline between Entries 3 and 4 may be worth investigating.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Perhaps Entry 3 is unusually long. Perhaps the navigation is unclear. Perhaps Entry 4 marks the point at which the Story asks readers to wait for a future release.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder supplies the progression counts; interpreting why readers behave that way remains with the author.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Continuing Stories<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Metrics can also be useful for serialized material that has not yet reached its ending.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A continuing Story may currently contain five released installments even though more are planned.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder can still report how far progression has reached among the material currently available.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When another installment is released, new progression events simply become part of the same Story\u2019s aggregate history.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A Story does not have to be finished before its readership becomes useful to understand.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Finite Story Completion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a finite Story, the terminal sequence Entry provides another useful event:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Story Completed<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This allows the author to distinguish between readers who begin a sequence and progression events that reach its intended ending.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A completed Story might therefore summarize:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Started: 320Reached final Entry: 241Completed Story: 226<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The figures describe progression activity rather than unique human readers.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Counts Are Events, Not Unique People<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder\u2019s Reader Metrics should be interpreted as <strong>event counts<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">They are not intended to answer questions such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How many unique people read this Story?<\/li>\n\n\n\n<li>How many times did one particular visitor return?<\/li>\n\n\n\n<li>What else did a specific reader view?<\/li>\n\n\n\n<li>Which individual reader stopped at a particular Entry?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Answering those questions would require a much broader analytics and identity system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder deliberately avoids that.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its metrics answer simpler questions:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Is this Story being started?<\/li>\n\n\n\n<li>How far is progression reaching?<\/li>\n\n\n\n<li>Which Entries are being completed?<\/li>\n\n\n\n<li>Are readers reaching the ending?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Reader Progress and Reader Metrics Are Separate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The two features work together but serve different purposes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Reader Progress<\/strong> is local to the reader\u2019s browser. It remembers where that browser left off so the Story can offer Continue and Restart controls.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Reader Metrics<\/strong> are aggregate information for the Gazette owner. They count progression activity without needing the browser\u2019s complete reading history to be stored on the server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A reader can therefore receive useful Story navigation while the author receives useful Story-level feedback, without GazetteBuilder building detailed individual profiles.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Focused Metrics for Sequential Content<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GazetteBuilder is not intended to replace a full analytics package.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">General analytics tools are better suited to questions about page views, traffic sources, devices, geographic regions, sessions, referrals, and visitor demographics.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Reader Metrics have a much narrower purpose:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>show how readers progress through GazetteBuilder Stories.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That narrower scope keeps the information directly relevant to authors using sequential material while avoiding unnecessary tracking complexity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a worldbuilder, that can be enough to answer the question that matters most:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Are readers starting the Story, and how far are they getting?<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sequential Stories create a useful question for a worldbuilder: are readers actually moving through them? GazetteBuilder can record simple aggregate progression events from Story activity without creating individual reader profiles or maintaining a server-side history of what each visitor has read. The goal is not general website analytics. It is to provide a focused view [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-9071","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages\/9071","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/comments?post=9071"}],"version-history":[{"count":3,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages\/9071\/revisions"}],"predecessor-version":[{"id":9074,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages\/9071\/revisions\/9074"}],"wp:attachment":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/media?parent=9071"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}