Skip to main content
Partner
Dec 7, 2023 4:35 AM UTC
Solved

Klaviyo x WooCommerce Integration - Non 200 Response Received Error

 Hi there, 

I faced similar issues when I was trying to integrate Klaviyo with my WooCommerce Store. It returns the error as showing below. 

 

I’ve checked with my developers that the user agent for Klaviyo is allowed on the server, but it still not working for me. 

 

It will be much appreciated if someone could help me sort it out. 

 

Thanks. 

 

 

    This topic has been closed for replies.
    Partner
    Feb 8, 2024 10:20 PM UTC

    Hey @Brian Turcotte, 

     

    Thanks for getting back to me. 

     

    The issue has been resolved after communicating with the support team. Following the instructions, our developers found that the Klaviyo plugin was in conflict with another plugin we were using (which has no connection with Klaviyo). 

     

    Therefore, we removed that plugin and installed another one with similar functionality and then the issue was resolved. 

    3 replies

    Brian Turcotte
    Klaviyo Alum
    Dec 8, 2023 5:39 PM UTC

    Hi @MLK Marketing!

    I’m going to check on this with Engineering and I’ll update the thread ASAP!

     

    Best,

    Brian

    Brian Turcotte
    Klaviyo Alum
    Feb 8, 2024 7:18 PM UTC

    Hi @MLK Marketing!

    My apologies for the delay here!

    Are you using any other 3rd-party plug-ins on your WooCommerce store? Sometimes this can interfere with the integration, so I’d recommend turning any other plug-ins off and re-trying.

     

    Best,

    Brian

    MLK MarketingAuthorAnswer
    Partner
    Feb 8, 2024 10:20 PM UTC

    Hey @Brian Turcotte, 

     

    Thanks for getting back to me. 

     

    The issue has been resolved after communicating with the support team. Following the instructions, our developers found that the Klaviyo plugin was in conflict with another plugin we were using (which has no connection with Klaviyo). 

     

    Therefore, we removed that plugin and installed another one with similar functionality and then the issue was resolved.