Morning,
We’re trying to enable the fraud0 integration on our account for the 30 day trial period to evaluate whether to use the tool moving forwards.
We ideally need this activated today so we can get a full months worth of data in April.
I go through the signup process and when I get to the final submit screen I get ‘An error occurred during communication with server. Please try again later.’
Any ideas?
Hi @B_Shimm, thank you for reaching out. The integration is currently limited to a small group of customers and is being released as an early preview. At this time, it is not functioning properly and is undergoing final tests and fixes, which unfortunately will not be completed before April. I will contact early adopters once the integration is ready for testing.
Hi @Jarek
Thanks for responding.
We did sign up for the early access when the option was originally there so are we on this small group of customers?
If not then I’d ask why the option of activating the trial is even available in our interface? If it’s still undergoing final tests and fixes, this should not be made available for users to interact/sign up with.
It would have been helpful if this had been communicated clearer as we have already commented to the business internally that we would be exploring a new bot protection tool and will now have to revoke that statement.
Hi @B_Shimm, thanks for the additional context — and I’m sorry for the confusion this has caused, especially given your timeline for April.
You’re right to call this out: if the activation option is visible, it should be communicated more clearly that the Fraud0 integration is still in early preview and not yet stable for general use. The “communication with server” error you’re seeing is a known symptom of this current rollout state.
Regarding your question about early access: yes, you are on the early-adopter list and were invited to participate (invitation sent in December 2025).
In the meantime, I appreciate the feedback on the UI/communication — I’m passing this along internally so we can either hide the activation entry point for non-enabled accounts or add clearer messaging to set expectations.