Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Marfeel is a publisher analytics and audience platform that tracks reader engagement and loyalty through a JavaScript SDK, building visitor profiles to help publishers grow audiences and revenue.
Marfeel is a content intelligence and audience analytics platform built for digital publishers. Through a JavaScript SDK embedded on the publisher site, it measures how readers engage with content, tracks loyalty and journey stage, and turns that data into insights that help publishers grow their audience and advertising revenue. It is an adtech and analytics tool, so tracking individual reader behaviour is central to how it works.
The Marfeel SDK sets first party cookies including _nrbi, which stores persistent visitor data such as a unique identifier, first and previous visit times and original referrer, and _nrbic, which holds current session data. This information can also live in local and session storage. Marfeel additionally sets a third party cookie on the domain events.newsroom.bi to reconcile the same user across several of the publisher''s root domains, and may set further cookies such as compass identifiers for analytics.
Because Marfeel stores identifiers and builds persistent reader profiles, it processes personal data under the GDPR and falls squarely within the ePrivacy rules on storing and accessing information on a device. These are non essential analytics and audience cookies, so prior consent is required before the SDK writes them. The cross domain reconciliation through events.newsroom.bi raises the sensitivity further, as it links a reader across multiple sites.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Marfeel is designed to use storage only when the reader gives consent through the publisher''s consent management platform, and it integrates with the IAB Transparency and Consent Framework. Publishers must therefore wire Marfeel to fire only after an affirmative opt in. Marfeel is headquartered in the EU, but cloud infrastructure and sub processors may operate in the United States, so confirm whether transfers rely on the EU US Data Privacy Framework or standard contractual clauses.
Place Marfeel behind your consent management platform so it loads only after analytics consent, map the _nrbi, _nrbic and events.newsroom.bi cookies in your cookie policy, and define retention periods. Sign a data processing agreement, confirm any US sub processors and the transfer mechanism, and run a DPIA given the scale of behavioural profiling. Provide a clear opt out and honour rejection signals from the consent framework.
Websites using Marfeel must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is recommended. Marfeel performs systematic monitoring of reader behaviour and builds persistent visitor profiles segmented by loyalty, journey stage and consent status, which is large scale behavioural processing. Assess the persistent _nrbi identifier, the cross domain reconciliation cookie on events.newsroom.bi, retention periods, any US sub processors, and ensure the SDK only stores data after the reader consents through your CMP.
Sample consent text
We use Marfeel to understand how readers engage with our content and to grow our audience. With your consent, Marfeel stores first party and cross domain cookies and identifiers to recognise returning readers and measure loyalty. You can accept or reject this analytics tracking and change your choice at any time in our cookie settings.
Third-party domains contacted
newsroom.bievents.newsroom.bimarfeel.commarfeelcache.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| _nrbi | Analytics | 1 year | Persistent first party visitor identifier storing unique id, first and previous visit times and original referrer. |
| _nrbic | Analytics | Session | Stores current session browsing data such as visit start time, referrer domain and landing page. |
| events.newsroom.bi | Analytics | 1 year | Third party cookie used to reconcile the same user across the publisher root domains within one account. |
| compass_uid | Analytics | 1 year | Compass analytics identifier used to recognise returning visitors for audience reporting. |
| compass_sid | Analytics | Session | Compass analytics session identifier for the current browsing session. |
Marfeel collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Marfeel sets first party cookies including _nrbi for persistent visitor data and _nrbic for the current session, plus compass identifiers for analytics. It also sets a third party cookie on events.newsroom.bi to reconcile the same reader across the publisher domains. This data may also be mirrored in local and session storage.
Yes. These are non essential analytics and audience cookies that store identifiers and build reader profiles, so prior consent is required under the ePrivacy Directive. Marfeel is designed to store data only after the reader opts in through the publisher consent management platform.
The lawful basis is consent. Because the processing involves persistent identifiers and behavioural profiling rather than strictly necessary functions, legitimate interest is not a safe basis, and the consent must be specific, informed and freely given.
Possibly. Marfeel is headquartered in the EU, but its cloud infrastructure and sub processors may operate in the United States. Confirm in the data processing agreement whether any US transfers rely on the EU US Data Privacy Framework or standard contractual clauses.
Yes, a DPIA is recommended. Marfeel carries out systematic, large scale monitoring of reader behaviour with persistent profiles and cross domain reconciliation, which are classic triggers for a mandatory impact assessment under the GDPR.
Load Marfeel only after analytics consent is given, integrate it with your IAB consent framework, and honour rejections. Document the cookies and retention in your policy, sign a data processing agreement, confirm transfer mechanisms, and complete a DPIA before launch.
Privacy first analytics such as Plausible, Matomo with anonymisation, or Fathom collect far less personal data and avoid cross domain profiling. They suit publishers who want audience insight without building persistent identifier based reader profiles.
List the _nrbi, _nrbic, compass and events.newsroom.bi cookies with their purpose, type and duration, and classify them as analytics requiring consent. Disclose the cross domain reconciliation and any US sub processors, and keep the policy synchronised with your consent banner.