When someone visits a site that uses Marfeel information about their behavior is sent at regular intervals back to Compass.
In this article, you will find a detailed description of all the information Compass sends.
You can use this information to debug your Compass integration if you don’t see what you expect in your dashboard.
events.newsroom.bi as the endpoint for data collection:
https://events.newsroom.bi/ingest.phpcollects information about the page view. You could see more detailed information about what the code is sending here
https://events.newsroom.bi/multimedia.phpcollects information about the multimedia elements of the page (loaded videos, plays, mute/unmute, play length… ). It could be enabled or disabled following this guide
https://events.newsroom.bi/recirculation.phpcollects information about links on the page, viewability, and CTR of those links. You won’t see any call to that endpoint unless you tag some modules to be measured using data-mrf-recirculation=“Module Name” or via the no-code experience
In the Network tab of your browser dev tools, you can find all those requests at once by filtering for “ingest”.
If you click on one of them, you will find all the information sent to Compass:
All the variables prefixed with a “p” relate to the page performance: they are a detailed breakdown of the page loading speed.
All the values are in milliseconds and, except for the first one, are calculated only once per pageview.
|pt||The delay between CompassJS starting tracking and when it is ready to send information.||All browsers|
|pdns||How long the Domain Name lookup took for the page, in milliseconds||Only modern browsers|
|pcon||How long it took the browser to establish a connection to the server to retrieve the page.||Only modern browsers|
|pfet||The time elapsed between starting to fetch the page and receiving its last byte.||Only modern browsers|
|pnet||The time elapsed between right before the browser requested the page and the moment it received its last byte.||Only modern browsers|
|pttf||The time elapsed between the first byte of HTML received and the last one.||Only modern browsers|
|pint||How long it took to parse the DOM, from start to until the page is interactive.||All browsers|
|pdcl||The time elapsed between the beginning of DOM parsing and when all the scripts have been executed.||All browsers|
|pdclf||The time elapsed between when the DOM parsing started and when the DOM is entirely ready.||All browsers|
You can read more on any of the variables used to calculate those values with Mozilla Developer Documentation.
Compass audits your site’s real performance thanks to those values, rather than using lab data like Google Lighthouse does.
Core Web Vitals are a Google-led initiative to unify essential metrics related to page speed and user experience.
They impact Google results ranking, so they must be taken seriously.
Rather than waiting for a month for Google Search Console to update their reading of your site’s Core Vitals, Marfeel Compass provides real-time information.
Every tracking request contains the Core Vitals for that reader on that page.
|wv||1 if web vitals were calculated, 0 otherwise.|
|lcp||Largest Contentful Paint||Under 2500|
|fid||First Input Delay||Under 100|
|cls||Cumulative Layout Shift score||Under 0.1|
|fcp||First Contentful Paint||Under 2000|
You can find this data in your Compas dashboard as a breakdown tab named “Validations” for every article detail page.
In addition to the performance-related values, every Compass request includes information about the user and their current session.
Not all values are sent with all requests.
Here’s the detailed breakdown of all the other key-value pairs sent to Compass:
|ac||Your Compass account ID.|
|t||The time when the user started navigating on your site.|
|r||The referrer URL that brought the user to your site.|
|url||The current page URL.|
|urcl||The current page’s canonical URL.|
|pp||The current pageview’s referrer URL.|
|u||The user’s unique permanent ID, to recognize them from one session to the next on the same browser. Defined by Compass.|
|s||The session’s unique identifier. Defined by Compass.|
|a||The number of Compass polling already sent for this page and user: 0 for the first one, 1 for the next one, etc.|
|n||The current timestamp.|
|l||The number of seconds the user has been on the current page so far.|
|ps||The timestamp when the user arrived on the page.|
|v||The current Compass tracker version.|
|ut||The type of user as you have defined it:
|sui||The user’s unique identifier as you have defined it.|
|uc||Indicates whether the user has consented to cookies for Compass.|
|sc||Scroll percent: how far down on the page the reader is, at the time of this request.|
|fv||The timestamp marking the user’s first visit to the site.|
|uvar||An array of all the user variables you and Compass have defined.|
|svar||An array of all the session variables you and Compass have defined.|
|pvar||An array of all the page variables you and Compass have defined.|
|ads||A Marfeel-only value tracking how many Marfeel ads are rendered.|
|conv||New Conversions that happened since the last request. You define conversions according to your goals.|
|rs||The recirculation source (HTML module) that brought the user to the current page, if any.|
|rfv||The reader’s RFV score, if it exists.|
|pageType||An identifier to distinguish between Standard Web and Facebook Instant Articles.|