Fixing Cloudflare 520 Errors Caused by Hebrew URLs and Large Cookies

Some PixelYourSite users have reported a frustrating issue: Cloudflare 520 errors when users arrive on their site via Facebook ads. The root cause wasn’t immediately obvious—but once uncovered, the fix was simple and effective.

The easy solution: disable landing page tracking inside PixelYourSite Professional. On the plugin’s main page, open “Control the Global Parameters”, disable “Landing page”, and save.

Here’s what happened, why it happens, and how you can solve it if you run into the same thing.

The Problem

A client using PixelYourSite PRO and the Super Pack noticed that visitors coming from Facebook ads would sometimes hit a blank page or see Cloudflare’s 520 error. This only happened for some users—specifically, those landing on pages with Hebrew URLs.

After some digging, we found the issue:

Cookies set by the plugin became too large, exceeding Cloudflare’s limit of around 8 KB.

PixelYourSite stores the full landing page URL in a cookie called last_pys_landing_page. This helps with UTM tracking and source attribution. However, if your landing page includes non-Latin characters (like Hebrew), the URL gets percent-encoded and can balloon in size.

Example Comparison

URL TypeExampleApprox. Cookie Size
Hebrew/דרושים/יועצי-ות-מכירה~150–300 bytes
Latin/jobs/sales-advisors~30–50 bytes

When combined with other tracking cookies and UTM parameters, the total cookie size can easily exceed 8 KB, causing Cloudflare to block the request and return a 520 or 400 error.

The Fix: Use Short, Latin-Based URLs

The solution is easy to implement:

Replace Hebrew (or other non-Latin) URLs with shorter, Latin-based alternatives.

For example:

  • From: /דרושים/יועצי-ות-מכירה
  • To: /jobs/sales-advisors

This simple change can reduce cookie size by up to 80%, avoiding Cloudflare errors and improving the reliability of analytics, AJAX, and tracking.

Why It Matters

This fix is especially important if:

  • You run ad campaigns (e.g., Facebook, Google) with UTM parameters.
  • You use Cloudflare’s free or basic plans with strict cookie limits.
  • Your site includes non-Latin URLs (Hebrew, Arabic, Cyrillic, etc.).

In Summary

  • Problem: Long, encoded Hebrew URLs + UTM tracking = oversized cookies.
  • Effect: Cloudflare returns 520 errors or breaks site functionality.
  • Solution: Use Latin-based, shorter URLs for landing pages, OR disable landing page tracking.
  • Result: Fewer errors, more stable tracking, better performance.

Get expert tracking tips in your inbox

Join 65,000+ marketers and site owners who already get our best guides:

Don’t stop here!

Subscribe to get more tips on tracking, analytics, and GDPR.

We’ll send you practical guides on Meta Pixel, CAPI, GA4, Google Ads, TikTok, Pinterest, GDPR compliance, and more, right to your inbox.

* We don’t spam, and all our emails have an “Unsubscribe” link that works. 

Leave a Reply

Your email address will not be published. Required fields are marked *

Find out when we have the next BIG OFFER!

Over 70 000 business-owners have access to our BIG DISCOUNTS. Don't miss the next one: