This page is a guide for people who cannot log into Book Report. Specifically, it is for people who:
- Are using the bookmarklet to launch Book Report, not the browser extension.
- Attempt to log in, but are sent straight back to the log in page.
- Use either Safari or Firefox as their browser. This issue does not appear to currently affect Chrome users.
The first thing to note is that our browser extension is completely unaffected by this issue, and is our recommended method for running Book Report. You can install it from this link. The bookmarklet is much more issue-prone than the extension, which is why we recommend the extension over the bookmarklet.
But some people have been using the bookmarklet for years and prefer that system. If that describes you then you can follow these troubleshooting steps to get logged into your account while using the bookmarklet. You shouldn't need to follow them all -- just go down the list until you are logged in.
- Log in directly on our site, instead of through KDP and the bookmark. Visit https://app.getbookreport.com and log in, then go back to KDP and click the bookmark.
- Enable third-party cookies. In Safari Preferences go to the "Privacy" section and turn off "Prevent cross-site tracking"; In Firefox Preferences go to the "Privacy and Security", choose Custom, and then uncheck "Cookies".
- Try fully logging out of Amazon, then logging into Book Report.
- Disable any security or privacy browser extensions you're using.
- Disable any security, privacy, or firewall software you are running on your computer.
- Add the domains www.getbookreport.com and app.getbookreport.com to any whitelists you can find in your security settings.
If all of those steps fail, free free to write in to our customer support. email@example.com
Why is this happening? Why don't you fix this bug?
Over the past couple years, browsers have started to add new features to prevent tracking. And this is a good thing! Creepy ad companies tracking people around the web is a bad thing. The trouble is, Book Report's bookmarklet relied on some of the same technologies as these ad trackers. Essentially, Book Report has to run code on Amazon's website, which to browsers looks a lot like an ad tracker running code on a blog. The browsers have been implementing new policies aimed at blocking ad trackers that essentially boils down to blocking one website from running certain code on a different website.
They work by blocking "third-party cookies", which means that only the domain you are currently on can set cookies - that's the only domain allowed to remember who you are. So when you run Book Report from kdp.amazon.com, we can't set any cookies, and cookies are how our login system works. This is why we think #1 above will cover almost all cases - it lets us set the cookie on our own domain, and then you can return to KDP with your cookies already set.
Unfortunately, the cause of this issue is unrelated to any code we at Book Report have written. If there was some programming we could do to make this article unnecessary, we would do that instead.
Thank you for understanding!