Hi @Geit, and sorry that this is happening!
For some context on what is happening: Klaviyo attempts to make API calls to your WooCommerce store during the integration setup. WooCommerce stores require authorization credentials, which is like an added layer of security when making API calls to your store. An example of a call that Klaviyo makes is:
curl https://STORE_URL/wp-json/wc/v3/orders \
-u CONSUMER_KEY:CONSUMER_SECRET
This is a generic WooCommerce REST API endpoint that should be available for all WooCommerce stores: https://woocommerce.github.io/woocommerce-rest-api-docs/#list-all-orders
If you have a web developer, they can test an API call to this endpoint in an app like Postman (make sure you are using the store URL that is auto-populating within the “Connection Details” when setting up the Klaviyo integration - see more on that below ). If Klaviyo cannot make this type of call when setting up the integration, then an error message will result. You (or your dev team) can make this exact call outside of Klaviyo, using the credentials generated for Klaviyo (found within WordPress > WooCommerce > Settings > Advanced > REST API). You may need to generate a new set of REST API keys with read/write permissions to obtain the full consumer key and consumer secret. This will give you some insight into what might be blocking Klaviyo’s call.
This can happen for different reasons, to name a few common ones:
- A firewall on your server is blocking Klaviyo’s requests (in this case, we recommend allowlisting our user agent, Klaviyo/1.0 and our IPs (instructions on how to do this here)
- Your website does not meet standard SSL requirements.
- 3rd party cacheing plugins are conflicting with the Klaviyo plugin. Do you have any plugins like WP Rocket or WP Total Cache? If so, we recommend disabling them to allow Klaviyo to connect.
- The Klaviyo API credentials generated not having both read and write permissions.
- Web browser privacy extensions. In this case, you’d want to ensure these extensions were disabled during setup.
I know this is a lot of information and may be a bit tricky to follow. I’m happy to explain further, or answer any additional questions, to help get to the bottom of this, if needed!