Klaviyo Server-Side Tracking Guide

Here is a detailed guide on how to use Analyzify's server-side tracking for Klaviyo.

Analyzify's Klaviyo Server-Side integration helps you send customer events directly to Klaviyo with richer event data and a simplified setup.

Events reach Klaviyo more reliably, and each one carries additional customer and product properties you can use for segmentation and flows.

This article covers connecting the integration, verifying it's working, and migrating from Analyzify's client-side

Benefits

After connecting the integration, you'll benefit from:

  • Reliable event delivery: events reach Klaviyo even when ad blockers or Safari's tracking restrictions block browser-based tracking.
  • Richer customer and product properties: variant, brand, category, pre-discount price and location arrive with each event, so you can build segments that native data can't support.
  • Additional ecommerce events: including collection page views and email capture, which the native integration doesn't send at all.
  • Simplified setup without GTM: connect with your API keys, no tag containers to maintain.
  • Native integration compatibility: runs alongside Shopify's native Klaviyo integration rather than replacing it.
  • Consent-aware by default: no events are sent for customers who haven't granted marketing consent.

Connect the Integration

To start connecting your integration, navigate to Analyzify > Integrations. Then, click “Connect” next to Klaviyo Server Side Tracking.

Next, enter your Public API Key and Private API Key .

After that, choose your content ID to customize item-level data in your reports and add/remove the events you want to track. Note: The default setup follows the best practice.

Finally, click Save Changes and your integration is now active!

Important: Viewed Product & Active on Site

Most events can safely coexist with Shopify's native Klaviyo integration. The only exceptions are Viewed Product and Active on Site , which require a little extra attention.

The Viewed Product event is generated by Klaviyo's onsite JavaScript. If Shopify's native onsite tracking is enabled while Analyzify is also sending the same event, Klaviyo will record duplicate product views.

To avoid this, open Klaviyo → Integrations → Shopify and review your Onsite Tracking settings. If Add Viewed Product tracking to my site is enabled, we recommend disabling the Viewed Product event in Analyzify’s client-side integration, or turning off Klaviyo's native Viewed Product tracking. Either approach prevents duplicate events.

The Active on Site event is also generated by Klaviyo's onsite JavaScript and should be considered when reviewing your tracking setup.

Verify Your Setup

We recommend verifying your installation before removing any previous implementation.

After connecting:

  • Visit your storefront.
  • Trigger a few ecommerce events (View Product, Add to Cart, etc.).
  • Open Klaviyo → Analytics → Metrics .
  • Confirm new Analyzify metrics begin appearing.

Events will start flowing immediately. Then you can build your flows in Klaviyo for example, a Cart Abandonment flow that triggers when someone adds a product to cart but doesn't complete checkout. Klaviyo will handle the automation; Analyzify handles the data.

Migrating to Klaviyo Server-Side

If you're already using Klaviyo with Analyzify, migrating to the new Server-Side integration only takes a few minutes.

The migration process depends on how you're currently sending Klaviyo events. Whether you're using Analyzify's Client-Side integration or a custom Google Tag Manager (GTM) setup, you'll simply replace your existing implementation with the new Server-Side integration.

Migrating from Analyzify Client-Side

If you're currently using Analyzify's Client-Side Klaviyo integration, migration is straightforward.

Open the Klaviyo Client-Side integration in Analyzify, click the three-dot menu , and select Disconnect . This removes your previous implementation without affecting your Klaviyo account or historical data.

Next, find the Klaviyo Server-Side integration and click Connect .

Next, you should enter your  Public API Key  and  Private API Key  .

To find your  Public API Key  , go to Klaviyo and click your account name (bottom left) > Settings > API Keys.

To find your  Private API Key , click Create Private API Key. Enter a name, choose Custom as the access level, and grant Full Access to Events, Metrics, and Profiles. These are required for server-side tracking. Click Create and copy the key immediately (it starts with “pk_” and can’t be viewed again later). Treat it like a password.

Then, choose your content ID to customize item-level data in your reports and add/remove the events you want to track. Note: The default setup follows the best practice.

Once you click Save Changes , all new events will be sent through the Server-Side integration.

Migrating from Google Tag Manager (GTM)

If you're sending Klaviyo events through Google Tag Manager, you can simplify your setup by moving the event delivery to Analyzify.

First, pause or disable your existing Klaviyo tags in GTM to prevent duplicate events. Then open the Klaviyo Server-Side integration in Analyzify, click Connect , enter your API keys, and save the configuration.

From this point forward, Analyzify will handle event delivery directly, eliminating the need to maintain custom GTM tags.

Using Shopify Native Together with Analyzify

In most cases, you can continue using Shopify's native Klaviyo integration alongside Analyzify.

The two integrations complement each other rather than replace one another. Most events are stored as separate metrics, allowing you to decide which metrics power your Flows, Segments, and automations. Shopify and Analyzify also send different event properties, giving you greater flexibility when building personalized customer experiences.

Only Viewed Product (and, depending on your configuration, Active on Site) requires additional configuration to prevent duplicate tracking.

Frequently Asked Questions

What exactly is Analyzify's Klaviyo Server-Side integration?
It's a way to send customer event data from your Shopify store to Klaviyo using Analyzify's servers instead of relying solely on your browser. Think of it as a backup route that captures customer activity even when ad blockers or Safari's tracking restrictions block the normal path.
Do we have to choose between Shopify's native Klaviyo integration and Analyzify?
No, they can work together. However, you need to be careful about duplicate tracking on two specific events: "Active on Site" and "Viewed Product". If Shopify's native integration sends these AND Analyzify sends them, Klaviyo will see duplicates. Solution: Disable these two events in Analyzify if you're using Shopify's native tracking.
Do we lose any data during migration?
No data loss occurs during the connection. However, you won't see historical events before migration. If you disconnect and reconnect, you're starting fresh (no backfill). New events will be collected under new metric names. If not needed, you can remove old metrics in your Klaviyo account.
What identifiers does Analyzify use to match customers?
Analyzify matches customers using multiple signals to ensure accurate profile recognition. We use email addresses when available, cookies for repeat visitors, and other identifiers for reliability. We're designed to match customers accurately without creating duplicate or ghost profiles in Klaviyo.
How does Analyzify handle GDPR and KVKK consent compliance?
Analyzify respects customer consent and only processes tracking data when the required consent is granted. For Klaviyo tracking, Analyzify reads the consent status from Shopify after your consent management platform (CMP) synchronizes the customer's consent state with Shopify. If the customer has not granted marketing tracking consent, Analyzify does not initialize Klaviyo tracking and does not send any events.
Can we disable specific events?
Yes. In Analyzify's settings, you can toggle events on or off. You can also enable "Consent Mode" in Settings, which means Analyzify only sends events for customers who have explicitly opted into marketing tracking.
Table Of Contents