Infrastructure Upgrades: More Reliable AMP Tracking and Faster Crawling

What's new
,
1

We’ve rolled out three critical infrastructure improvements to make your Marfeel setup more accurate, efficient, and reliable.

  1. First, AMP page tracking is now more robust thanks to a multi-CDN architecture powering our AMP SDK.
  2. Second, our crawler infrastructure has been rebuilt for faster indexing and fewer hits to your servers.
  3. And third, new Tracking Rules let you filter out noise from internal traffic and bad actors directly from your settings.
🚨 These upgrades require quick updates on your end. These changes directly impact your tracking accuracy, data quality, and indexing performance. Take action now.

AMP SDK: More Reliable Tracking, Less Data Loss

We’ve just upgraded the AMP SDK to a Tier-1 global CDN bringing you faster load times, lower latency, and improved reliability across the board.

What you need to do

Just two quick steps:

  1. Update the endpoint in your AMP analytics config: from events.newsroom.bi to sdk.newsroom.bi. From:

<amp-analytics config="https://events.newsroom.bi/amp.v1.json" data-credentials="include">

To ➜

<amp-analytics config="https://sdk.newsroom.bi/amp.v1.json" data-credentials="include">

  1. Redeploy your AMP pages. No other changes needed.

Full implementation details: Google AMP instrumentation

New Marfeel Crawlers: Smarter, Faster, Lighter

Switch by October 1, 2025

We’ve rolled out a new crawler infrastructure that indexes your content faster, using fewer requests and putting less strain on your servers.

What you need to do

  1. Allow the new crawler IPs in your firewall → crawler-ips.json
  2. In Organization > Crawler Settings select Europe (new) or America (new)
  3. Remove the old crawler IPs: 162.55.235.182, 162.55.235.186, 167.114.119.97

:rotating_light: Old crawlers shut down on October 1, 2025. Switch now to stay up to speed.

Tracking Rules: Keep Internal and Noisy Traffic Out of Your Data

Marfeel now gives you more control over your analytics with Tracking Rules, letting you filter out irrelevant traffic sources using IPs and domains.

With IP Address Block, you can exclude specific users from analytics by filtering their IPs using CIDR notation. For example, this allows you to remove internal visits, such as those from your own team, for more accurate data.

With Domain Block, you can exclude full domains being tracked, for example your internal dev platform or some proxy services.