System requirements for Magento and Klaviyo integration

Do you have a Magento webshop and want to synchronize it with Klaviyo? Then you’ve come to the right article. Here, we’ll walk you through the system requirements for optimal synchronization with Magento 1 or 2.
‍

Configuring API User Permissions

First, the administrator of your Magento store is responsible for the system specifications and configuration. The integration will only run smoothly if the system you’re using is set up to work with Klaviyo.
When integrating your Magento store with Klaviyo, create a new SOAP (for Magento 1) or REST (for Magento 2) role with full resource access. You will also assign a new user to this role. Make sure to set ‘Resource Access’ to ‘All’. Without the required permissions for this API user, Klaviyo cannot correctly interact with your Magento store’s APIs, meaning the integration won’t be able to retrieve data. Make sure this API user has the necessary permissions.

‍

Enabling Access to API Endpoints

Klaviyo also pulls data from specific endpoints. Your system configurations need to allow access to these endpoints. Consider the impact of security checks or URL redirection logic on the accessibility of these endpoints for Klaviyo. If you use whitelisting, be aware that Klaviyo’s IPs can change. Instead, whitelist Klaviyo’s user agent: Klaviyo/1.0 is the user agent request Klaviyo sends in all outgoing requests. If Klaviyo doesn’t have access to the expected API endpoints, some or all Magento data will fail to sync, resulting in error messages.

‍

Synchronizing API Requests

When you activate the integration, Klaviyo automatically queues API requests to sync historical data, including customer data, order data, and product catalogs. Klaviyo does this as quickly as possible so that marketers can promptly use this data in their accounts. Klaviyo tries to do this responsibly by managing concurrency and handling retries carefully. If your store has a large amount of historical data, limited resource capacity, or other applications making significant API requests, consult with your Magento administrator to ensure your infrastructure can handle the historical data synchronization. Your administrator might consider temporarily increasing resources, using auto-scaling, or asking Klaviyo to throttle the requests.

If you’re concerned about the amount of historical data or your server’s capacity to handle a temporary increase in API requests, consider temporarily scaling server resources or asking Klaviyo to throttle requests via a support request.

‍

Verifying SSL Certificate Validity

An SSL certificate is important. It digitally verifies a website's identity and enables an encrypted connection between a web browser and a web server. Your website’s original server hosts the SSL certificate, which is essential for securely accepting payments, protecting password logins, and securing web forms. Use this tool to check the SSL certificate of a website.

Magento integrations may be disabled if your website's SSL certification expires. In such cases, update your domain and intermediary certificates with your hosting provider. If you're unsure where your certifications are, contact your host provider for assistance.

‍

Ensuring Sufficient Server Memory Allocation

The amount of disk space an e-commerce website needs depends on various factors, including the number of products, the number of images per product, the quality of the images, the number of emails stored by the server, and the number of pages with static content. We recommend allocating more than 1GB of memory for your Klaviyo integration, with 512MB being the minimum requirement.

If your server cannot allocate enough resources to respond to Klaviyo’s requests, integration errors will occur. The Klaviyo-Magento integration begins with synchronizing historical data. Therefore, we recommend checking memory settings in Magento and your server before activating the integration. The default Magento PHP memory setting is 128MB, which you can adjust in the php.ini file by changing the value of the ‘memory_limit’ variable to the recommended 1024MB.

‍

Setting UTC Time Zone

Lastly, Coordinated Universal Time (UTC) has been the primary time standard since the 1960s. Klaviyo relies on UTC to schedule synchronization of your most recent data.

If your Magento setup uses a different time zone, it becomes harder for Klaviyo to determine which data is the most recent. This also complicates Klaviyo’s ability to decide which data should be synced. You should update your time zone to UTC in both your Magento backend and in the app/Mage.php and app/code/local/Mage/Core/Model/Locale.php files.

Find the original article here.