Skip to main content
Pixel is a fingerprinting request the browser makes in addition to the sensor. Passing it earns a cookie named ak_bmsc.
Most Akamai sites include the pixel request, but very few enforce it. Skip this page until you have a valid _abck and the protected request is still refused. If it goes through without ak_bmsc, you do not need Pixel.

​
How to recognize it

The page contains an inline script that assigns a number to bazadebezolkohpepadr:
The same page loads a second Akamai script, the pixel script. In your powhttp recording, find the request the browser makes right after it loads, a POST to the pixel endpoint on the same site. That is where you will post.

​
The flow

1

Read the two values

Take the number assigned to bazadebezolkohpepadr from the page. Then fetch the pixel script through your session and take the hash: the u value from the first array in the script. It is a short quoted string.
2

Generate the payload

Call /pixel with the number, the hash and your User-Agent. The response body is the payload itself, already URL-encoded as a form.
3

Post it to the site

Post the payload, unchanged, to the pixel endpoint you found in the recording, through the same session, with application/x-www-form-urlencoded as the content type and the page as referer. Do not encode it again. The response sets ak_bmsc.
4

Continue with the sensor

Run the normal sensor flow. With both ak_bmsc and a valid _abck in the jar, make the protected request.

​
Request fields

​
Troubleshooting

The site does not use Pixel. If you are still blocked with a valid _abck, look for SBSD or Sec-CPT instead.