Getting started with statistics

• Visualize Google Analytics Data with Looker Studio

  Created 27 Jul 2026

  Looker Studio is Google’s reporting tool for creating interactive dashboards and visual reports. By connecting it to Google Analytics, you can turn raw analytics data into easy-to-understand charts and reports that help you understand how readers interact with your content. You can create and maintain your own Looker Studio dashboard, or Prenly can set it up for you as a paid service.   What is it used for? Google Analytics collects a large amount of data, but finding the right information can be time-consuming. Looker Studio presents your analytics in a visual dashboard, making it easier to monitor trends, share insights, and understand how your publication is performing. A typical Prenly dashboard includes insights such as: App opens and unique readers Reading time and reader engagement Most viewed pages and articles Reader activity throughout the day Devices and operating systems Geographic distribution of readers Push notification performance Advertisement impressions and clicks (if applicable) These insights can help you better understand your audience, improve your content strategy, and provide valuable data to advertisers and stakeholders.   How is it implemented? Before a Looker Studio dashboard can be created, Google Analytics must already be configured for your Prenly application. Here is how it works → If you choose Prenly’s setup service, we ask you to: Invite dev@prenly.com to your Google Analytics property. Let us know who should receive the dashboard template.   We will then: Configure the dashboard template. Connect the required metrics and visualizations. Share the template with you.   To ensure that you remain the owner of the report, you will then: Create your own copy of the shared template. Connect the correct Google Analytics property (if you have more than one). Grant dev@prenly.com administrator access to your copied report so we can complete the configuration.   Note: Only the owner of a Looker Studio report can connect a data source. Creating your own copy ensures that you retain full ownership of the dashboard while still allowing us to configure it for you.   Technical details Looker Studio requires an existing Google Analytics property as its data source. Without Google Analytics, no data can be displayed in the dashboard. The standard Prenly dashboard includes statistics from your iOS app, Android app, and web reader.   If you would like us to set up a Looker Studio dashboard for your publication, have questions about the setup process, or would like pricing information, please contact hello@prenly.com.

• User vs Session in Google Analytics

  Created 31 Mar 2026

  A visitor (user) who uses the e-paper 100 times on the same device should be counted as one user, but 100 sessions. A user is thus a unique visitor per device. A user can be a returning visitor and thus a recurrent user (as long as the user can be traced back over several dates). A session is a traceable use (i.e. a traceable viewing of a "screen" in the app (in the web app "screen" is called "page")) of the e-paper within a fixed activity, where a new session is started due to inactivity (usually 30 minutes per default), where there is no upper limit on how long an active session can last. It is thus an activity that the user performs during a specific date. Whatever a user does in the app is always collected as part of a session, regardless of whether the user is reading in article or replica reading mode or just looking at other parts of the app (e.g. the home page or the archive).

• 

  Configure Analytics – Custom Definitions

  Created 30 Mar 2026

  The statistics provided via Prenly are event-based. To see what events are available, see https://wiki.prenly.com/en/user-analytics/eventsEach event contains additional data in the form of event parameters. An event can be seen as something that happened, but if you want more information, you need to look at the event parameters. For example, if you are interested in the exposure of articles in article reading mode, you can look at the event data. On the other hand, if you are interested in seeing which articles have been exposed, you need to look at the event parameters associated with the event to get the answer. Google Analytics will by default list the available events. If you want to see the event parameter data, you will need to configure your Analytics, where it will take Google Analytics up to 48 hours to make the change take effect. By configuring Analytics to show the event parameters associated with an event, you can filter the data and view aggregated graphs per event parameter. To configure Google Analytics to expose event parameters, you must configure custom definitions and custom metrics. Configuring custom definitions Step 1. Select the Google Analytics property to configure. Step 2. In the menu on the left, select Admin (the cog). Step 3. Select Custom definitions in the property column. Step 4. Select Create custom dimensions to create a new custom dimension. Step 5. Dimension name: Enter the name you want. This will be displayed in the report data Scope: Must be set to "Event" Description: Optional: Optional. You can add a description for the event parameter. Event parameter: The parameter must be identical to the dimension of the event parameter, e.g. "article_slug". Once the above has been set, save the settings by selecting "Save". You can find the dimension of the event parameter by selecting an event on https://wiki.prenly.com/en/user-analytics/events, e.g. select the event article_open(https://wiki.prenly.com/en/user-analytics/events/article_open) and look in the column "dimension". You can also find the description for the event parameter by viewing the "description" column. Repeat steps four and five for each event parameter you want to configure. Below you can see an example of a setup for your Analytics. Once you have configured your Analytics, it will take Google up to 48 hours for the change to take effect. Please note that some event parameters ("time_spent" and "played_duration") need to be defined as "Custom metric" rather than "Custom dimensions". This is important to ensure that their values are aggregated. Additional bonus An added bonus after configuring your Analytics to expose the event parameters is that you can create a custom report via Looker Studio. By creating a custom report through Looker Studio, you have more control over what data you want to expose and can customize where and how you want to display the data.

• 

  Configure Analytics – Enhanced measurement

  Created 30 Mar 2026

  If you are interested in tracking data via Google Analytic's "page_view'" concept then we highly recommend you enable the enhanced measurement on the web app's Analytics property.The web app is using the History API web API to present the reader within the replica reading mode and article reading mode, a technology which Analytics does not per default enable to track as a page view. This means that on default the page view tracked data will potentially miss a lot of page view event hits as your users engage with the web app. The Prenly-specific reading events are not affected by this.To enable Analytic's enhanced measurement for web apps is easy! In this guide, we will guide you on how.Activate enhanced measurement Step 1. Complete Get started with statistics.Step 2. Log in to Google Analytics and select the correct Analytics account and Analytics property.Step 3. In the left menu, select Admin. In the main view under the Property menu, select Data Streams.Step 4. In the Data Streams menu, select the Web panel. Select the web app data stream to enable enhanced measurement. Step 5. Activate(toggle) Enhanced measurement.Step 6. Once enhanced measurement is enabled, you are done.You can, if you wish, configure enhanced measurement; however, the enhanced page view tracking is enabled by default and cannot be turned off.

• 

  Export statistical data

  Created 24 Oct 2025

  Do you want to export statistical data for your selected e-paper solution from Prenly? There are few steps but this guide will guide you through the process. Preparation The very first thing you will have to do is to sign in to your Google Analytics account. If you have more than one Analytic property then you will need to select the correct property you want to extract data from. If you are not currently in the Reports view, please select "Reports" in the left-most side menu. Google Analytics will automatically minimise this sidebar so you might need to expand the sidebar to select "Reports". Select Reports in the left sidebar menu. Export statistical data per selected report Select which Analytics report you would like to extract the available data. There are several categories and subcategories of reports. Below you can find an illustration of the general report setup. Analytics general report categories overview. 1. Select the "Share this report"-icon located in the top-right corner of the report. Follow-up by selecting "Download file". 2a. Select "Download PDF" to download the currently selected report view as a PDF. 2b. Select "Download CSV" to download the available data for the currently selected report. Select the icon "Share this report". Select "Download file". Select "Download CSV" to download the report data. Select "Download PDF" to download a PDF-version of the report.

• Handle date ranges

  Created 24 Oct 2025

  The date range selector is at the top right of every report except the Real-Time reports. Click the arrow next to the existing date range to open the controls. Select one of the following from the Date Range menu: Custom: Data for your custom date range. (See instructions, below.) Today: Data available for the current calendar date up until the time of your selection Yesterday: Data for the previous calendar date Last Week: Data for Sunday through Saturday of the previous calendar week Last Month: Data for the first to last day of the previous calendar month Last 7 days Last 30 days Click Apply. Custom date range To set your own dates, select Custom from the Date Range menu, then follow the instructions below.To select a single date:Click twice on any date on the calendar OR Enter a single date in both Date Range fields.To select a specific week:Click the first and last days of the week on the calendar OREnter the beginning and end dates in the Date Range fields.To select a range of dates:In the calendar, click the desired start date, then click the end date. The selected days are highlighted. OR Enter start and end dates in the Date Range fields.To compare two different date ranges:Select the Compare to checkbox, then select Custom, Previous Period, or Previous Year. Use the controls to set the second date range.Click Apply.

• 

  Google Analytics - Get started with statistics

  Created 24 Oct 2025

  Before you start To start collecting statistical data you will need a Google Analytics account. 1. Create a Google Analytics account via google.com/analytics. 2. Select Get started today to create an account or to sign in to your current account. Get started  1. Notify hello@prenly.com that activation of GA can begin, include this information: If you have more than one e-paper, state which ones you wish to collect data from. Which individual(s) you would like to represent the owner of your data in the underlying Firebase project. Please note you will need an e-mail address associated with a Google Account that has edit rights to your chosen Google Analytics account. 2. The customer service team will invite you as an owner of the underlying Firebase project and you will receive an e-mail from Firebase. After you have received the invitation you are ready to continue with the below. Activate statistical data gathering 1. Log in to Firebase Console 2. If you are prompted to select a project, select the e-paper project you would like to enable statistic gathering for. 3. Select Project settings in the cogwheel menu. Select "Project settings" on your Firebase project to enable statistics. 4. Select the sub-menu item Integration 5. Select Enable on the card Google Analytics Select "Enable" on Google Analytics integration card to enable statistics. 6. Select a Google Analytics account within the drop-down menu to host your statistical data on the page Configure Google AnalyticsIf you are unable to select an Analytics account, then you do not have edit rights to your Analytics account. 7. Select Enabling Google Analytics to create a new Analytics property on your Analytics account, where statistical data will be gathered and aggregated by the created property. 8. Select the link for the newly created Analytics property within Firebase. You will be taken to Analytics. Select Property Settings; configure your new property by setting industry (most likely "News"), the correct reporting time zone, and currency for your e-paper. 9. Set a name for the new property in order to easier find the property in the future. 10. Send an e-mail to hello@prenly.com stating you have finished the setup for your e-paper by including which e-paper you have activated the statistics for. 11. Once Prenly's customer service has received your e-mail, they will activate your web app and notify you that it has been activated. 12. You are now done and ready to view your new statistical data within your Analytics account by selecting the created Analytics property. How long will it take till I see my data? Once the statistics have been activated, Google will usually take 12-24 hours to allow Analytics to start aggregating your statistical data.  Why don't I see any data even though I have waited over 24 hours? In order for Prenly to transfer the data to Analytics the readers must have given consent for user analysis.  You can enable your readers to give consent to be tracked by creating a consent dialog in Prenly Workspace and associating it with your e-paper application.

• Create a GA account

  Created 24 Oct 2025

  To start collecting basic data from a website: Create or sign in to your Analytics account: google.com/analytics Do one of the following:- To create an account, click Start for free.- To sign in to your account, Click Sign in to Analytics. Set up a property in your Analytics account. A property represents your website or app and is the collection point in Analytics for the data from your site or app. Set up a reporting view on your property. Views let you create filtered perspectives of your data; for example, all data except from your company’s internal IP addresses, or all data associated with a specific sales region.Follow the instructions to add the tracking code to your website so you can collect data in your Analytics property.Google Analytics: First Steps Next steps Configure your account, properties, and views to determine access to your data and which data is available. For example, you can: ● Grant permissions to make configuration changes and to interact with data. Learn more about user management. ● Link your Google Ads and Analytics accounts so you can share data between them and develop a more comprehensive understanding of how your marketing efforts drive user behaviour on your sites or apps. Learn more about linking your accounts. ● Set up reporting views so you can align Analytics users and relevant data. Learn more about views. ● Set up goals to identify the actions you want users to take on your site or app, and to give a monetary value to those actions. Learn more about setting up goals. ● Browse the Solutions Gallery for dashboards, custom reports, and segments that you can use in your Analytics account. ● Modify your tracking code to collect additional data such as:User interactions with links, buttons, video controls, and other dynamic elements of your site or app. Learn more about event tracking. ● Check e-commerce activity like user engagement with product lists and internal promotions, and how successfully users moved through your purchase funnel and checkout process. ● Learn more about e-commerce and enhanced e-commerce data collection and reporting. Download the Analytics app Once you have installed the tracking code on your site or app, and have configured your Analytics account, download the Analytics app from Google Play so you can take Analytics reporting with you anywhere (well, anywhere you have a connection). Learn more about the Analytics app here.

• How the link structure works in a Prenly

  Created 24 Oct 2025

  Understanding how a URL is structured can help editors, developers and analysts alike to quickly identify the type, origin and structure of content. In this article, we break down two typical URLs from Prenly: - One pointing to a page in a publication- One pointing to an article.We anonymize parts of the links to focus on the structure rather than the content. Example 1: Page in a publication https://[domännamn]/p/[slug]/2025-01-01/r/3/4-5/1234/123456 What each part means: https://[domain name] The server where the content resides /p/ Stands for publication, and is used as the entry point to the entire system for issues and articles [slug] A specific name for the title, e.g. My magazine becomes my-magazine. This slug is configured in the system administration interface per title. 2025-01-01 Name of the publication. By default this is a date, but it is also possible to change this in Prenly admin to a text. /r/ Stands for replica, i.e. reading in standard/PDF mode 3/ An internal sorting parameter for spreads, where each number represents a pair of pages. For example:1 = pages 12 = pages 2-33 = pages 4-5 4-5/ The actual page range of the spread. 1234 Title ID in Prenly 123456 Issue ID, i.e. the specific numbering of that particular publication. Example 2: Article https://[domännamn]/p/[slug]/2025-01-01/a/[artikel-slugg]/1234/123456/555666777 What each part means: https://[domain name] Same as above: domain of the publishing platform. /p/ Publication [slug] Name of the publication (title) 2025-01-01 Same as above, name of the publication. /a/ Stands for article [article-slug] A search engine friendly variant of the article title, e.g. this-is-the-title-name 1234 Title ID (same as above) 123456 Issue ID (same as above) 555666777 Article ID - a unique ID for the specific article. Summary These links are systematically designed to combine readability with functionality. They make it easy to: - Identify which publication the content belongs to- See the publication date- Know whether it is a whole page/page break or a single articleFor systems that use this approach - such as editorial platforms like Prenly - it provides an efficient and predictable way to link content, automate processes and create metadata for sharing, analysis and indexing.

• 

  Matomo for statistics

  Created 24 Oct 2025

  To get started with Matomo for the web version of Prenly, simply send us the server address and site ID of your Matomo installation. Server address is the URL address on which you have installed Matomo. Can be something like https://matomo.domain.com, i.e. unique to your setup. Site IDMatomo lets you measure multiple websites with a single server. Each website you add gets a unique site-id (website-id).Click on Measurables(or Websites) > Manage page. There you will find a list of all websites. The Website ID can be found on the left in the table of all the web pages you have set up. You will also need to define a number of custom dimensions for your site to capture the extra data we send with each event. We recommend that you create a separate "site" for Matomo so that you do not mix traffic from the e-magazine with traffic from web sites. But you can use the same site for all three platforms of the e-paper. If you want to combine traffic from multiple sites, you can use Matomo's "roll-up" tool. To send traffic to Matomo from the iOS and Android apps, your apps need to be updated with an SDK and resubmitted to Apple and Google. Contact our customer service for price information if you want to use Matomo with Prenly. Matomo in detail We currently send our three standard events  ("replica_page_open", "article_open" and "external_url_clicked") to Matomo enriched with a number of customised dimensions.Documentation of our events can be found on our wiki. Update: from Android version 11.13.0 and iOS 11.8.0 additional events are sent to Matomo.• "prenly_push_notification_open", "prenly_app_open" to track push notifications.• "title_overview_open" and "title_open" for those using title pages• "favorite_title_add" and "favorite_title_remove" for those using favorites Here are the custom dimensions that you need to define. 1: application_slug2: title_slug3: title_uid4: publication_slug5: publication_uid6: publication_date7: page_number8: part_slug9: article_slug10: article_uid11: article_name12: article_external_id13: section_slug14: external_url15: push_notifications_enabled16: push_notification_uid17: push_notification_sent_at18: message_title19: message_body This list of custom dimensions will be expanded as we add new events. The most up-to-date list of our dimensions and events can be found on our wiki:https://wiki.prenly.com/en/user-analytics/exporting-data/matomo-analyticshttps://wiki.prenly.com/en/user-analytics/events It is important that you define the custom dimensions with exactly the numbers listed above. All must be defined as "action dimensions", not "visit dimensions". Matomo only offers five dimensions in the basic version, so you must follow Matomo's instructions to increase the number of dimensions. Matomo and consent If you use Prenly CMP as a consent dialog, you can decide what level of data to send from the web and app users. The default setting is that no data at all is sent from the web and app when the user has not given their consent. However, if you want all data to be sent for later filtering in your own system or Matomo, you can set the data to be sent even from those users who have not given consent. In these cases, you can choose to send data completely anonymously or including user-id. You are then responsible for filtering the data later in accordance with the law. If you use Matomo cloud, this should be avoided. This setting is made in Prenly Workspace, in the Prenly CMP module. If under "Basic tracking with Matomo" you select "Do not require consent", the data will be sent anonymously - without user-id - for those users who have not given consent to be analysed. If under "Individual tracking with Matomo" you select "Do not require consent", all data including user-id will be sent also for those users who have not consented to be analysed. This allows you to receive all the data to your own data warehouse for filtering. Other supported CMP modules (Didomi, Cookiebot, Usercentrics) have similar settings for the consent requirement.