We have a cloud fare security layer on our website as hackers are always attempting to take us down (damn witches ha ha).
I've noticed if customers are shopping from their phones (which MOST people do) and they don't have their phone OS and/or browser OS up-to-date, cloud fare won't verify that they are a "person" and the verification box spins and spins.
Also- if I send customers to a direct page link AND they haven't gone through the cloud fare verification they get a 404 page not found.
We're spending quite a bit of money on Meta advertisements and it's QUITE frustrating to answer comment after comment of links not working.
I'm at my wits end with this and need some help. Anyone else have cloud fare?
By the way- Square has the Cloud fare on our site- that's already been verified.
Hello Dina,
I truly understand how frustrating these new internet security protocols can be. I have come about some information recently that may be able to assist you in your website development. As of late, there are new rules being rolled out across the internet as a whole and these changes may affect your website performance and client acquisition process. Unfortunately these changes do not apply only to Cloud Fare and Square websites, but the internet as a whole. There are parameters in place now that monitor the age of the site visitor to mitigate sales to minors within the digital economy. You have the option of adding KYC (know your client) technology to your website that would allow anyone to enter but prompt them to enter their personal information, create a Square account with your business, or verify their age through biometrics. These choices are made available to the public so they can personally manage viewing your website upon entry and allows it to pass Cloud Fare security verification. The public currently has the choice of upgrading their device performance by opting into age verification provided by their personal device (Apple settings, Android settings) that allows the websites they encounter to verify that they are of age to view or participate in your website. If there is any way that I can assist you more please feel free to reach out. I hope this information helps you in your business flow and website traffic.
Hey @DinaLRosenberg , I use Cloudflare for pretty much everything I develop. The earlier reply about KYC, age verification, and biometrics doesn’t fit what you’re seeing. I don’t see how adding any of that would help with this bot check.
Cloudflare does mention older browsers, blocked scripts, and browsers inside apps as reasons these checks can fail. The Facebook and Instagram browsers are worth checking, since you’re running Meta ads. Someone clicks your ad, your store opens inside the app, and that browser might struggle with the Cloudflare check.
I’d try opening the same link on the same phone, first inside Facebook or Instagram, then directly in Safari or Chrome. If you know someone with an older phone, try it on theirs too.
If it works in Safari or Chrome but gets stuck inside the app, that gives you something concrete to show Square. You can also tell affected customers to open the link in their phone’s browser as a temporary workaround.
Since you mentioned Square manages the Cloudflare protection, I’d send them an example once you can recreate it. Give them the link, when it happened and your time zone, plus the phone model, operating system, and browser version.
If it keeps failing, grab any error codes and the Cloudflare Ray ID at the bottom of the verification page. There’s already one in your screenshot. That can help Square track down what happened to that request.
Hi @DinaLRosenberg, I'm sorry this is still happening, especially with ad spend behind it.
A quick clarification on one reply above: this check is Cloudflare's bot verification. It's part of Square Online's platform security and isn't related to age verification or KYC, so there's no need to add anything like that. @Manny_SelSq's suggestion is spot on. When someone taps your ad, your site opens inside the Facebook/Instagram browser, which can struggle with this check. As a workaround for now, customers can tap the ••• menu and choose "Open in browser" (Safari/Chrome).
To get our ECOM team investigating the spinning check and the 404s, we need details from just one or two affected visits:
If you'd rather not post customer details publicly, feel free to send them to me in a private message.
I'm not sure how I'm suppose to get this information- these are potential customers clicking the link in response to a reel I've boosted on Meta.... the link 404's and they think my site is broken.. they then leave a comment. So I'm not aware in real time.
Surely engineers have a phone that isn't updated that they can attempt to replicate the issue as this has been an ongoing issue for about 1/2 a year now
Just checking with our team again, and we can definitely try to investigate if you can share the following information instead of the live details @DinaLRosenberg :
Square Community