nod.

Connect Klaviyo

Add your Klaviyo API key so nod. can read your Email, SMS, and Push performance.

By nod. product team · Updated July 12, 2026

Connecting Klaviyo brings your Email, SMS, and Push campaign performance into nod., so you can see it next to your ads and your store revenue instead of checking a separate tab.

1. Open the sources grid

Go to Settings → Data sources (/app/performance/settings/integrations). Find the Klaviyo card, under the Email category.

You need the workspace Admin role to connect it. If you're a Member, you can see the card's status but the connect action is disabled — ask an admin to do it.

2. Connect with your Klaviyo API key

Klaviyo is always available to connect; there's no waiting on setup. Two ways in:

  • Paste a private API key — open the card and paste your Klaviyo private API key.
  • OAuth, if your workspace has it enabled — connect through Klaviyo's login instead of pasting a key.

Either way, nod. checks the credential against the live Klaviyo Accounts API before saving. A bad key never lands as a connection — you'll get an error instead of a card that looks connected but isn't. Once verified, the card label switches to your Klaviyo account name and the pill changes to Connected.

What flows in

Klaviyo is read-only: nod. pulls your Email, SMS, and Push campaign performance in, and never writes anything back to Klaviyo.

The aggregate campaign and flow values shown in Performance are daily send-date data in the reporting window. nod. does not fill missing hours with estimates. Hourly flow detail is a separate Klaviyo flow-series lane; campaign and mixed-channel totals remain explicitly source-daily only.

That performance data is what shows up in the nod. Performance agent when you ask about email — it reads your campaigns, ranked by revenue.

What happens next

Once connected, ask the agent about your email performance and it'll pull from Klaviyo directly. There's no separate backfill step to wait on the way there is for Shopify.

Common pitfalls

  • Connect is disabled or missing. You need Admin, not Member, to connect a source. Ask a workspace admin.
  • Key gets rejected. nod. verifies the key live against Klaviyo before saving — if it's rejected, double-check you copied the private API key correctly and that it hasn't been revoked in Klaviyo.