Other articles by jens

Prenly at B2B Media Days 2026 in Berlin | Digital Publishing Platform

11 May 2026

When Europe’s leading professionals in B2B media, digital publishing, and professional communication gather in Berlin for B2B Media Days 2026, Prenly will be there as part of the conversation shaping the future of the publishing industry.Organized by Deutsche Fachpresse, B2B Media Days is considered one of Europe’s most important events for trade media, publishing innovation, and digital transformation within the B2B sector.For Prenly, attending the event is a natural step in supporting publishers, membership organizations, and media companies with smarter digital publishing solutions and modern subscription experiences. What is B2B Media Days? B2B Media Days is an annual conference in Berlin that brings together publishers, media executives, SaaS providers, editors, strategists, and technology companies from across Europe. The event focuses on topics such as: digital publishing AI in media and publishing subscription business models audience engagement content strategy marketing automation media technology data-driven publishing future revenue models for publishers Each year, the conference attracts industry leaders looking to understand how B2B media is evolving in a rapidly changing digital landscape. The program includes keynote presentations, expert panels, networking sessions, and workshops centered around innovation in publishing and media technology. Prenly joins B2B Media Days 2026 Prenly will attend B2B Media Days 2026 to connect with publishers, partners, and organizations looking to strengthen their digital publishing strategies. Prenly helps companies and membership organizations: create digital magazines and online publications manage subscriptions and premium content distribute content across web and mobile platforms improve reader experiences increase engagement and retention combine print and digital publishing workflows As publishers continue to invest in owned audiences and subscription-based business models, the need for flexible and user-friendly publishing platforms is growing rapidly. Why B2B Media Days matters for the publishing industry The publishing industry is undergoing major transformation driven by artificial intelligence, changing reader behavior, and new monetization strategies. B2B Media Days has become a key meeting place for companies working within: digital media publishing platforms subscription technology media SaaS audience analytics professional content publishing customer retention and engagement For Prenly, participating in the event is about more than visibility. It is about contributing to discussions around the future of professional publishing and helping organizations create sustainable digital media experiences. Berlin as a hub for media innovation Berlin has established itself as one of Europe’s strongest centers for technology, startups, and media innovation. The city provides an ideal setting for conversations around the future of publishing, AI-driven content strategies, and digital transformation. The international profile of B2B Media Days makes it especially valuable for companies operating across the European media and publishing market. Prenly and the future of digital publishing At B2B Media Days 2026, Prenly looks forward to discussing topics including: AI and the future of publishing modern digital magazine experiences subscription and membership growth reader engagement strategies scalable publishing workflows improving digital reading experiences Prenly continues to focus on helping publishers create seamless, scalable, and sustainable digital publishing ecosystems. About B2B Media Days 2026 Event: B2B Media Days by Deutsche Fachpresse Date: May 21, 2026 Location: Kulturbrauerei, Berlin, Germany Organizer: Deutsche Fachpresse Focus Areas: B2B media, publishing innovation, AI, subscriptions, and digital transformationLearn more about the event at the official website: https://www.b2b-media-days.de/ Meet Prenly in Berlin Prenly is part of Textalk Group and powers digital publishing for media companies across the Nordics and beyond – including 100% of Sweden’s daily newspapers.We’re excited to connect with publishers of all sizes – from local newsrooms to national media groups – and share how we’re helping shape the next generation of news. Are you attending B2B Media Days 2026? Let’s meet in Berlin. Ravi Sen GuptaSenior Account Executiveravi@textalkgroup.com LinkedIn -> Esther Dietzsch Account Executiveesther@textalkgroup.comLinkedIn ->

Prenly at INMA World Congress 2026 Berlin

10 Apr 2026

Prenly will be attending the INMA World Congress of News Media 2026 in Berlin (May 4–8) – one of the most important global events for news media leaders, publishers, and digital strategists.As the media industry continues to evolve, INMA World Congress brings together decision-makers from leading media companies across more than 50 countries to discuss the future of journalism, audience growth, and digital revenue. Let’s talk about the future of digital publishing At Prenly, we look forward to meeting publishers, media houses, and industry leaders to discuss how to: Build sustainable digital publishing strategies Grow and engage digital audiences Create modern, accessible reading experiences Unlock new digital revenue streams Streamline workflows across editorial, product, and commercial teams A shared focus on transformation This year’s INMA theme – “From walls to bridges: news media reimagined” – reflects the same challenges and opportunities we see across the industry.From AI-driven newsrooms and subscription growth to cross-functional collaboration and platform strategies, the conversations in Berlin are more relevant than ever. Meet Prenly in Berlin Prenly is part of Textalk Group and powers digital publishing for media companies across the Nordics and beyond – including 100% of Sweden’s daily newspapers.We’re excited to connect with publishers of all sizes – from local newsrooms to national media groups – and share how we’re helping shape the next generation of news. Are you attending INMA World Congress 2026? Let’s meet in Berlin. Ravi Sen GuptaSenior Account Executiveravi@textalkgroup.com LinkedIn -> Esther Dietzsch Account Executiveesther@textalkgroup.comLinkedIn ->

How Local Newspapers Can Build Sustainable Digital Reader Habits | Prenly

27 Mar 2026

Many local newspapers already have an e-paper. That is an important first step, but in practice it often leads to familiar problems: low engagement, weak daily reading habits, and fragmented user experiences. The challenge is no longer just publishing a digital edition. It is building a complete digital newspaper that readers return to every day. For local and county newspapers in the US, that challenge is especially important. Resources are limited, teams are smaller, and most publishers already have systems in place that need to keep working. The question is not whether to go digital. The question is how to create a digital experience that strengthens the relationship with readers over time. Because for many local newspapers, staying digitally relevant is not only about subscriptions or product improvement. It is about remaining a daily part of community life.Why Local Newspapers Face a Different Digital Challenge County papers operate differently from large national publishers. Editorial teams are often leaner, budgets are tighter, and digital decisions need to be practical from day one. Most local publishers are not looking for a large transformation project. They are looking for a way to improve the reader experience, strengthen loyalty, and make digital publishing more valuable without creating extra complexity behind the scenes. That is why success is not only about getting content online. It is about making sure local journalism stays close to readers throughout the day, across the moments when people check in on what is happening in their town, their county, and their community. What local publishers need is a digital publishing platform for local newspapers that supports habit, retention, and long-term growth while still fitting the realities of smaller teams and existing systems. Why Local Publishers Need More Than a Replica Edition A replica edition still has value. It gives loyal readers access to the familiar print layout and offers a straightforward way to publish editions digitally. But reader behavior has changed. Today, people move between devices throughout the day. They check headlines on their phones, return to stories from newsletters, open alerts when something important happens, and expect a fast, clear reading experience whenever they engage. That is why local publishers need more than a static edition. A newspaper that wants to stay relevant in its community needs to create touchpoints between editions, not just at the moment the PDF is published. For many local newspapers, staying digitally relevant is not only about technology. It is about remaining a trusted daily part of community life, staying close to readers, and continuing to matter in the moments when local news is most needed. A stronger digital product helps readers discover stories more easily, follow local developments as they unfold, and build a habit around turning to their local paper first. That is what turns occasional access into a deeper reader relationship. What Builds Sustainable Digital Reader Habits Sustainable digital growth starts with habit. And habit is built through experiences that feel useful, familiar, and easy to return to. A strong mobile experience Readers expect local news to work wherever they are. If the experience feels clumsy on mobile, they are less likely to come back. That is why local publishers need a strong experience across web, iOS, and Android, with the same quality and consistency wherever readers choose to engage. More than one way to read Some readers still prefer the replica edition. Others want an article view that is easier to scan and read on smaller screens. A stronger digital newspaper experience supports both. That flexibility makes local journalism easier to use in more situations, whether someone is reading the full edition in the morning or checking one important story during the day. Engagement between editions For local newspapers, habit is often built between publishing cycles. Features like notifications and reader engagement tools help publishers stay present throughout the week, not only when the next edition is released. That helps local news remain part of daily routines instead of something readers only open occasionally. Accessibility and ease of use Many local newspapers serve broad audiences, including older readers and readers with different accessibility needs. Features like audio and accessible reading modes can improve the experience for a much wider group of people. In practice, better accessibility also makes local journalism easier to reach for the whole community. Consistency that builds trust Readers come back when the experience feels reliable. They know where to find content, how to navigate it, and what kind of value they will get each time they open the app or website. That consistency helps turn digital reading into a habit instead of a one-time visit. What Local Newspapers Should Look For in a Digital Publishing Platform When local publishers evaluate digital solutions, the goal should not be to find the most advanced platform on paper. It should be to find the right fit for their organization, readers, and long-term goals. For county newspapers, the most important factors often include: fast time to launch the ability to keep existing CMS and subscription systems a strong mobile experience across web, iOS, and Android tools that support engagement and retention low total cost of ownership workflows that smaller teams can manage without extra strain This is where the conversation needs to move beyond traditional e-paper language. A platform may be able to publish a digital edition, but that does not automatically mean it can help strengthen reader relationships or support sustainable digital growth. What local publishers need is a digital newspaper platform that connects content, reading experience, and engagement in a way that feels realistic to run and valuable to readers. From E-Paper to Connected Digital Newspaper Many county newspapers already have the foundation they need. They have strong local journalism, an established publishing workflow, and readers who still depend on them for trusted information. The opportunity is to build on that foundation. Instead of treating the e-paper as a standalone product, publishers can create a more connected digital experience around it. That can include article-based reading, mobile apps, alerts, archives, audio, and easier access to content across the channels readers already use. This shift does not need to happen all at once. In many cases, the most sustainable path is gradual modernization. That means improving the reading experience, reducing friction, and giving readers more reasons to return, while keeping the systems and workflows that already work well internally. For local newspapers, that matters for more than digital growth alone. It also helps them stay visible, useful, and familiar in everyday community life. How Prenly Supports Local Newspapers Prenly is built for publishers who want to strengthen digital engagement while keeping the systems and workflows they already rely on. Instead of forcing newspapers to replace everything, Prenly helps local publishers build on their existing setup. That means they can keep their CMS, login, and subscription systems while extending their digital offering across web, iOS, and Android through the Prenly digital publishing platform. With Prenly, publishers can combine the familiar value of the edition with a more modern reader experience. That includes article view, audio features, notifications, and archives that help readers return more often and engage in more ways. Prenly Reader gives your readers the best experience. Prenly also gives teams a central workspace to manage digital publishing efficiently. For local newspapers with limited resources, that matters just as much as the front-end experience. A better reader product needs a workflow that is practical to operate every day, and Prenly Workspace is designed to support that. The result is a more connected digital newspaper experience that helps local publishers improve retention, strengthen engagement, and grow digital subscription value without large technical investments. To explore what that can look like in practice, you can book a demo and see how it works. Sustainable Digital Growth Starts With Habit, Not Just Access Many local newspapers already have digital access in place. But access alone does not create loyalty. Sustainable digital growth comes from becoming part of the reader’s daily routine. That means making local journalism easier to reach, easier to read, and more useful across the moments when people actually engage with news. For local newspapers, that is not only a business question. It is also a community question. When a publication stays part of everyday digital life, it stays closer to the people, places, and conversations that define its role in the community. A replica edition can still be part of that strategy. But on its own, it is rarely enough to support stronger retention and long-term digital value. For county newspapers that want to modernize their offering without losing what already works, the priority is clear: build a digital product that readers return to regularly, not just a digital version of the printed paper. You can learn more about Prenly’s digital publishing platform for county papers if you want to connect this strategy to a practical next step. FAQ What is the difference between an e-paper and a digital newspaper? An e-paper usually refers to a digital replica of the printed edition. A digital newspaper is broader and can include article-based reading, mobile apps, audio, notifications, archives, and other features that support a more dynamic reader experience. Why is reader habit important for local newspapers? Reader habit is closely tied to retention, loyalty, and digital subscription value. When readers return regularly, the newspaper becomes a more consistent part of their daily routine and a stronger part of community life. Can local newspapers improve digital engagement without replacing their existing systems? Yes. Many local publishers want solutions that work with their existing CMS, login, and subscription systems. That makes it possible to improve the digital experience without taking on a full rebuild. What should local newspapers prioritize when going digital? They should prioritize ease of use, mobile experience, reader engagement, and a platform that supports long-term sustainability without creating unnecessary operational complexity.

Uploading archive

12 Feb 2026

Using an FTP client, an archive (of standard PDF files) can be uploaded to us. Here are some simple instructions. Note: If your archive is larger than 100 GB, please contact us before uploading. Naming the files All uploaded PDF files must be named with the title (name or abbreviation of the newspaper) and publication date, if necessary also the part to which the PDF file belongs and the page number. If an issue consists of a merged PDF:title_20190101.pdf If an issue consists of several PDF files, add the page number:title_20190101_001.pdftitle_20190101_002.pdftitle_20190101_003.pdf If a number consists of different parts:title_20190101_partA_001.pdftitle_20190101_partA_002.pdftitle_20190101_partA_003.pdftitle_20190101_partB_001.pdftitle_20190101_partB_002.pdftitle_20190101_partB_003.pdf It is important to be consistent The name structure provided allows the files to be imported. Characters such as underscores and periods are also important. If any of the characters are replaced, the files will not be found during import and therefore not published. Therefore, make sure that the name structure always looks the same. Naming issues using the issue number (optional) By default, an issue will be named after the publication date, for example 2019-01-01.It is also possible to name the issue using its issue number, provided that the number is included in the filename in a structured format.For this to work, each PDF must follow a consistent naming format, for example:title_1_20190101.pdftitle_2_20190201.pdf In this example, we can extract issue numbers 1 and 2 from the filename, as well as the year 2019. If you would like to use this feature, please inform us:- that the issue number should be used in the name- which position in the filename contains the issue number- how the name should be formatted Examples of display format:- No. 1 - 2019- Issue 1 2019

LOGIN | CSV

12 Feb 2026

A common way to lock material behind a login procedure is to use a CSV file. When a reader tries to log in, a check is made against the registry (CSV file) which determines whether access is granted or not. What should the registry contain? A CSV file looks like an Excel file and the desirable information it should contain is:- Names- Email addresses- Customer number/subscription number/ID number Where should the register be saved? The file gets uploaded to us by using an FTP-client. The file gets uploaded to us by using an FTP-client.If you do not have an FTP client, you will need to download one, such as FileZilla.- Download FileZilla for Mac- Download FileZilla for Windows Remember to always name the file the same way every time a new file is created, so that we can always find it when we import.

Practical tips for digital publishing in 2026

9 Jan 2026

Happy New Year! As 2026 begins, many publishing teams are looking for practical ways to work smarter – not by adding more tools or processes, but by making better use of what’s already available.Across publishing workflows, a few clear patterns stand out: publishers want to reduce manual effort, build more consistent routines, and be more intentional about how content is distributed and accessed.Here are practical tips for digital publishing in 2026, focused on automation, smarter distribution, and building trust into everyday workflows. 1. Consistency only works when it’s easy to maintain In theory, most publishers agree on the value of regular communication. In practice, consistency often breaks down when it depends on manual effort. Weekly alerts. New issue notifications. Ongoing campaigns.When every send requires someone to remember, log in, and repeat the same setup, even the best intentions fade over time. That’s why recurring workflows matter. With recurring push notifications already available, consistency no longer has to be recreated every week. Instead, publishers can set up a routine once – and let it run automatically in the background. Tips for 2026:Start using workflows where rhythm is already built in, so consistency becomes reliable rather than fragile. How to get started:Begin by identifying one message that goes out regularly – for example a “new issue available” notification or information about a new podcast episode. Set it up once as a recurring notification, and review it periodically instead of rebuilding it every time. View the setup guide for recurring push notifications -> 2. Publish once, distribute everywhere Publishing rarely happens in just one place. The same content often needs to reach multiple channels – apps, libraries, aggregators, or partner platforms. In 2025, many publishers realised that the biggest drain on time wasn’t publishing itself, but re-publishing: exporting, reformatting, uploading, and double-checking the same content over and over again. Automation here isn’t about doing more, faster. It’s about removing duplicated effort so publishers can focus on editorial quality, audience value, and strategic decisions. With multi-channel publishing already in place, content can be published once and distributed automatically to the channels that need it. Tips for 2026: Take advantage of workflows that remove repeated handoffs between systems, so focus stays on content rather than logistics. How to get started:
Map out where your content is currently published manually. If the same edition is exported or uploaded more than once, that’s a strong candidate for automated distribution. Read more about MCP on Webarch -> Contact us to get started -> 3. Share access to your content Another clear signal from 2025 was how publishers thought about access. Instead of treating content as either fully locked or fully open, more publishers experimented with selective openness: sharing a single issue outside the paywall opening specific editions for a limited time making older publications publicly available This approach recognises an important reality: not all content has the same role. Some editions are designed to convert. Others are meant to introduce new readers, build trust, or re-engage existing audiences. Tips for 2026: Use access intentionally. Decide what each piece of content is meant to achieve and unlock it accordingly. How to get started:Choose one edition with long-term value and test opening it up or sharing it externally. Observe how readers interact with it before deciding what to unlock next. How to share one issue -> How to open a selected issue -> How to make your publications public -> 4. When trust is built into the publishing workflow Trust, transparency, and compliance have always been fundamental in digital publishing. That hasn’t changed. What did become clearer in 2025 is how important it is to make these principles practical and visible in everyday workflows. When privacy policies are easy to create, host, and maintain, compliance stops being something publishers postpone. Instead, it becomes a natural part of publishing operations. Making it easier to do the right thing increases the likelihood that it actually gets done. Tips for 2026: Treat privacy and transparency as part of product quality, not background documentation. How to get started with Privacy policy pages:Create and host your privacy policy page directly in Prenly. Our privacy policy generator helps you with the content: just fill in the template, add how you handle personal data, and your privacy policy is ready to publish. Please note: you’re responsible for making sure the final text matches how your company uses personal data. Create your privacy policy in minutes -> A simple way to start 2026 If you’re looking for a practical takeaway from all of this, start small: remove one manual step from your workflow automate one recurring task and make one intentional decision about access or transparency Small changes compound quickly when they reduce friction. Next-generation digital publishing The strongest signal going into 2026 is how publishing teams want to work. In 2026, successful digital publishing will be less about doing more and more about using what’s already available to work consistently, efficiently, and with greater focus on readers. That’s the direction we’re excited to support and we look forward to continuing the journey together this year.

Apple | Updated agreements

24 Oct 2025

Apple regularly updates their agreements to use its App Store platform. Apple usually updates the agreements several times a year. Each time Apple updates the agreements it will be up to the account holder to review the updated agreement and eventually approve it, as the agreement updates will block Prenly to administrate your iOS app. Reviewing and approving the updated agreement(s) is quick and easy. All you will need is a computer and access to the account holder's AppleID (an e-mail address, password, and two-factor authentication), i.e. the information you use to log in to your Apple Developer account. Step 1. Sign in to your Apple Developer account as the account holder by visiting https://developer.apple.com/account/. You may also visit https://developer.apple.com/ and select Account in the menu. Sign in to Apple Developer. Step 2. At the top of the Apple Developer overview you will see active statuses regarding your membership: • Updated agreements• Apple Developer Program membership active expired/renewal See the section The program license agreement has been updated.In it, you will be able as the account holder to find a link to your agreement page. Click the link to be taken to the agreement page at the Business section. Follow the instructions provided by Apple in this section. Alternatively, you can swipe down to the section Program resources and select the link labeled Business. Step 3. It is time to review and eventually approve the updated agreement. Depending on your app's requirements you might see two agreements, one for the mandatory Free Apps but also one for Paid Apps. Both agreements need to be up-to-date. See the agreement's status in the tabular column Status. If it's Active without further information on new agreements, you are done – else review the new agreement. To view the agreement select View, review the agreement and approve it. Tabular view of an updated "Free Apps" agreement ready to be reviewed and approved.

Apple | Create Developer Account

24 Oct 2025

In order to publish an iOS app on the App Store, you need a company developer account, which requires a DUNS number and an Apple Account. If you do not have this already, it is created via Apple. If you need more detailed instructions than the guide below, click here and scroll down to Enrolling in the Apple Developer Program as an organization.   Start here: Step 1 - Apple Account (Previously referred to as Apple ID) Apple Account is created here: Apple Account Tip! Enter a general email address that several people in your company have access to. In case of illness, vacation, change of position.   Step 2 - D-U-N-S number If you have already received the D-U-N-S number, go directly to step 3. In order to create a developer account with Apple, you need a D-U-N-S number. The D-U-N-S can be described as an international organization number. Go to this link to check/create one. You can also use this page, to have your D-U-N-S number sent to you.   Step 3 - Developer account Click on the link and follow the instructions to create an account. Be sure to enter Company/Organization as the entity type later in the flow. After the application has been submitted, Apple will send further instructions via email within a few days.   Step 4 - Invite Prenly to the developer account, after Apple has approved the application made in Step 3. ▪ Log in Under "Program resources" and "App Store Connect" select "Users and Access". A table view with users appears here. In the menu, click on the plus sign to add a new user. Add Prenly's developer account as "Admin". The name can be set to whatever you want but the email address must be ios-app-manager@textalkmedia.se Make sure the options under Developer/Additional Resources are checked. Save by clicking on Invite. Under "Users and Access" click on "Integration" and select "Request Access". ▪ Read through the request, check the confirmation box and click "Send".   Step 5 - Verify Trader details As of April 2024, all accounts must verify their trader information in order to publish apps. Read more and follow the instructions here.  

Create a GA account

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.

Manage subscribers in Prenly Workspace

24 Oct 2025

There might be several reasons why a subscriber should be deleted, for example, GDPR. Regardless of the reason here is how you can delete an individual subscriber. Requirements. To delete a subscriber you need to have the Subscriber manager team membership role on your team membership account. Step 1. Log in to Prenly Workspace. Step 2. In the left-hand menu select Subscribers and the desired subscriber directory which represents Prenly's version of your subscribers' information from your subscription system of choice. Select the subscriber directory. Step 3. Locate the subscriber you would like to delete from the list of subscribers. You can either find the subscriber in the tabular view or filter the result by selecting the Search field and entering search values. Step 4. Select the subscriber's subscription account from the subscriber overview to enter the detailed subscriber information view allowing you to administer the subscriber. Select the subscriber's subscription account. Step 5. In the top-right corner, towards the right of the Subscriber information, select Delete subscriber. Select "Delete subscriber" to delete the subscriber. Step 6. Confirm the subscriber deletion by selecting Delete. Please note that you cannot undo the deletion of a subscriber once you have selected the Delete button.If you want to abort select Cancel. Confirm the subscription account deletion to delete the subscriber. The subscriber's subscription account has been deleted. Note. If the subscriber directory is associated with an integration or an active import, the subscription account may be automatically recreated based on the import/integration response and information. It is a good idea to verify that the subscriber has been deleted from your subscription system. What about the user's login account? The user's separate login account needs to be deleted by the user. The user initiates the process by appending "/user/delete-account" to the web app's URL. Example. Given the web app is available on https://example.com/ then the user visits https://example.com/user/delete-account to initiate the process to delete their login account.

Create a CMP module

24 Oct 2025

According to new digital laws all web pages and Android / iOS apps must have a consent dialog for the collection of cookies and other personal data. This is easily done using a CMP (Consent Management Platform) module that you create in Prenly Workspace. Here we show you how! You can also use external CMP platforms where we currently support Didomi, Cookiebot, Usercentrics and Sourcepoint. Read more To configure external CMP platforms in Prenly Workspace you will need them to be activated for your application. Please contact our Help desk and ask them to activate the CMP platform you want to use. Please note that you have to be a workspace owner with full rights in order to create these modules and modify the consent dialogs. Create a new CMP module in Settings -> Consent dialogs. Start by logging into Prenly Workspace and going to Settings -> Consent dialogs -> click New. Name and choose the type and language of the new module. A window appears in which the module is to be created. Start by filling out its desired name. Then choose which type of module you want to use. (Prenly CMP is the standard preset, but you can also choose Didomi, Cookiebot or Usercentrics if these are used by your company and have been enabled) Finally you have to choose if you want to generate a new standard dialog text (and also in what language) or if you want to copy the dialog from an already created module. Then click Create to create the module. Configuring the module is as easy as counting to three! When the module is created it ends up in the list of available modules. If we click on a module in this list we can see which clients it's connected to and add new connections.Here we can also edit the module's name and title - and to a large extent configure its contents by scrolling further down on the page. Next to each segment are helpful explanations that we can read by clicking the question mark buttons or the three dot menus further down. Using the three dot menus we also have the option to reset each segment to its default text. If we want to save changes made we click the green Save button in the upper right corner. If we want to delete a module we can find this option when we click the three dot menu next to the Save button.Should the module already be connected to a client when we want to save our changes, the next step will be affected depending on how extensive our changes are. If we try to save major changes, a new consent from the users will be required. If, on the other hand, only a misspelling or similar is corrected, the changes are simply saved in the module without new consent being required. Go to your application -> Consent dialog to connect the app with the new module. To connect the newly created module with an application, we go to Applications -> select an application -> Consent dialog. There we easily connect any client (Android / iOS / Web) with a consent dialog by selecting the module in the respective client's list. Finally, save the new connection using the green Save button in the upper right corner. All done! Please note that the consent dialog will not appear on the mobile applications until they are updated to version 11.0.4 (Android) and 10.0.0 (iOS). For the web app, however, the dialog is displayed immediately. For those who use Google Tag Manager If your e-magazine uses its own Google Tag Manager container to send statistics for the e-magazine, you need to ensure that the user's consent in Prenly CMP is respected. This instruction assumes you are familiar with Google Tag Manager. Step 1. Create a new variable Press “Variables” in the left menu.Go to “User-defined variables” and press “New” Select variable type "Data Layer Variable" Select variable type "Data Layer Variable" Enter “consent.analytical” in the “Data Layer Variable Name” fieldAlso enter “consent.analytical” as the name at the top. Tap the box so it expands and you can select “Format value” Set "Format Value" so that the value “null” is set to “false” and the value “undefined” is set to “true”. Press "Save". You have now created your data store variable. It appears in the list of "user-defined variables". Step 2. Set your “triggers” Now set your triggers to include the variable as a condition. Tap on “Triggers” in the left menu. Open each trigger and add a condition that “consent.analytics” should be set to “true”. This means that the visitor's choice to reject statistics is respected. Add this condition to all your triggers. Save them. Check that all triggers have this condition. Step 3. Preview and publish your container If you have not yet added the Prenly CMP module to Workspace, the statistics will work as usual. Once you have added the Prenly CMP module, statistics will not be sent from the users who chose to reject statistics in their privacy settings. If you use other types of tags, there are also data layer variables for “consent.marketing” and “consent.functional”. The instruction above only applies if you use your own GTM container that you administer yourself. In that case you must configure GTM before activating the CMP module in Prenly Workspace. If you are using Prenly's Google Tag Manager container GTM-5B22TM then this configuration is done by us at Textalk Media. The same applies if your statistics are sent via Firebase for web. In these cases, you only need to activate the CMP module in Workspace.

Edit in Prenly

24 Oct 2025

Do you need to make changes to a digital publication or a publication with article reading mode? You can do that in Prenly editor, but keep in mind that what you change in the article reading mode does not affect the content in your PDF pages.Choose the publication you would like to updateChoose the publication in your selected Prenly title by clicking the publication card either on the cover image or name field. Click on a publication under the menu TitlesYou will enter the Prenly Editor when you have chosen a publication.Prenly EditorMake sure that you are in the tab "Articles".Find your article in the list, you can search for the article headline by the magnifying glass.Each article has a circle to the left in the article list, this shows the status of the article - it's either shown as an empty circle, or filled with a green or red bullet.Green bullet - the article is Approved to be publishedRed bullet - the article is Stopped and will not be able to publish until this bullet has been changedEmpty circle - the article is in Draft and not approved to be published, in this state you are able to edit the articleYou can change the article status, a green bullet or empty circle can be clicked - then it will change between Approved and Draft. A red bullet needs to be handled from the menu in the top right corner. Click in the circle or the menu in the top right corner to update the articled status between Approved, Draft or StoppedWhen an article is in draft you are able to update the content of an article. Here are a few examples of what can be done:1. Update the text, write, add or remove text.Create a new content fragment by selecting the previous content fragment, and tap the ENTER key on your keyboard. You can change levels of the fragments in the drop-down-menu to the left of your content fragment. Here, for example, you can decide whether the fragment should be of the type Body, Ingress, Vignette or a headline of a certain Heading level2. Add hyperlinks.Mark the text that should be clickable, in the bubble that appears you click on the link icon to add a URL or a mail-to-link. Click the link icon to add a hyperlink. The broken link on the right removes an existing link3. Handle the content in a media container.On the icons to the left of your media container you can • add images from your article, publication or from your computer.• add videos by pasting a video URL or embed code.• sort the order of the content in your media container by clicking and dragging them in order.• delete your entire media container.You can also crop and delete single images from a media container by browsing to the image you would like to remove, and click on either of the icons in the lower left corner of the media container.To create a new media container you make a new content fragment by selecting the previous content fragment, and tap the ENTER key on your keyboard, you will then get a camera icon and a play button that you can click on - this can be done anywhere in the article.Approve your changesWhen you are done editing you will need to make sure that the status of the articles you have edited are marked as Approved. Click the circle or the menu in the top right corner to change the articles status to Approved - the circle by the article in the list should be marked with a green bullet to be approved.Don't forget to publish your changesYou can read about how to publish your changes in our guide Re-publish <- click here to get there.Good luck! ?

Add fact boxes to an article

24 Oct 2025

Preparations Start by logging into Prenly Workspace. Select a title in the left menu and click Settings (a gray square or gear icon) in the upper right corner. Now you see a list. Click on Article categories. Settings Click on the button Add Artice Category Give your article part a name (for example "Factbox") and set Article type to Article part. Creating an article part Click Create Create or locate the article to have a fact box Navigate again to the title where you want to create your fact box. Open the issue where this article is to be placed or is placed. The fact box will now be created separately, and then linked to the article where you want it to appear. Create the Fact Box Click on New Content and New Article in the In the Articles-tab. Create the content for your fact box, i.e. write the title, text and/or add media files. At the top right is a menu/drop-down. Click on it and select your new article part (in the example it was named 'Factbox'). Select article part When the fact box is ready, navigate back to the article that will receive the fact box. Make sure the article has a Draft status, if not, change it to this. Draft Then click Linked. Here you can expand the section that you named, for example, "Factbox" and select your newly created factbox by clicking on the + (plus sign). Once that's done, you can close the modal. Linked content In the menu item Linked you should now be able to see a one (1) and when you click on the arrow you can see your fact box. Click on the pen if you want to edit your fact box. Change the status from Draft to Approved and publish the article. Navigate to the article in your application, and when you open the article, you can see your fact box. A factbox!