AMP tracking, crawler, and tracking rules upgrades
We’ve rolled out three critical infrastructure improvements to make your Marfeel setup more accurate, efficient, and reliable.
- First, AMP page tracking is now more robust thanks to a multi-CDN architecture powering our AMP SDK.
- Second, our crawler infrastructure has been rebuilt for faster indexing and fewer hits to your servers.
- And third, new Tracking Rules let you filter out noise from internal traffic and bad actors directly from your settings.
AMP SDK: More reliable tracking, less data loss
Section titled “AMP SDK: More reliable tracking, less data loss”We’ve 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
Section titled “What you need to do”Just two quick steps:
- Update the endpoint in your AMP analytics config: from
events.newsroom.bitosdk.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">
- Redeploy your AMP pages. No other changes needed.
Full implementation details: Google AMP instrumentation for Marfeel analytics tracking
New Marfeel crawlers: Smarter, faster, lighter
Section titled “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. For full details on Marfeel crawler user agents and IP whitelisting, see the SDK integrations documentation.
What you need to do
Section titled “What you need to do”- Allow the new crawler IPs in your firewall → crawler-ips.json
- In Organization > Crawler Settings select Europe (new) or America (new)
- Remove the old crawler IPs:
162.55.235.182,162.55.235.186,167.114.119.97
🚨 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
Section titled “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.
What changed with the Marfeel AMP SDK?
The AMP SDK now runs on a Tier-1 global CDN, delivering faster load times, lower latency, and improved tracking reliability. Publishers need to update the endpoint from events.newsroom.bi to sdk.newsroom.bi and redeploy their AMP pages. See the full Google AMP instrumentation guide for implementation details.
How do I switch to the new Marfeel crawlers?
Allow the new crawler IPs from crawler-ips.json in your firewall, select Europe (new) or America (new) in Organization > Crawler Settings, and remove the old crawler IPs. Old crawlers shut down on October 1, 2025.
What are Marfeel tracking rules?
Tracking rules let you filter out irrelevant traffic from your analytics using IP Address Block (to exclude specific IPs via CIDR notation) and Domain Block (to exclude entire domains such as internal dev platforms or proxy services).