Skip to main content

November 20, 2026

Multiple Klaviyo metrics named "Placed Order"

Centra order mail stalled when Klaviyo held two Placed Order metrics. I match API integration, seed backfill metrics, and skip flows instead of failing sync.

Sander Korf4 min read

A Centra fashion storefront sends order confirmation, cancellation, and refund mail through Klaviyo. A Klaviyo flow is an automation: something happens on a profile, Klaviyo runs the steps you drew. The flow trigger is usually a metric, Klaviyo's name for an event type such as Placed Order. On staging Monday morning a QA tester placed an order and waited for the receipt. The inbox stayed quiet. By late afternoon GitHub Actions printed Multiple Klaviyo metrics named "Placed Order" (2). Resolve duplicates before syncing flows. for both staging and production. I had been wiring flows from code. The name on the trigger card looked right. The integration behind that name did not.

I wrote an earlier note on copying Centra plugin metric names exactly. Spelling Placed Order with the same capitals is still necessary. It is not sufficient. Klaviyo can show one label on two different metrics. Shopify, MCP connectors, sample events, and the real Centra stream can all register the same display name. Only the Centra path uses the API integration. A flow listens to one metric id at creation time. Klaviyo's docs say you cannot change that trigger afterward; you clone or delete and rebuild.

When the sync treated the name as the id

The repo ships flow definitions from YAML through a script that runs in CI for staging and production. On 6 November the script resolved every metric name up front. One duplicate anywhere aborted the whole job. That is how staging and production both died on the same error string while QA was already missing mail.

My first patch narrowed lookups to flows that were missing in the account and preferred the newest metric whose integration is API. If Klaviyo returned exactly one row for the name, I used it even when the integration was not API. Bugbot on the pull request noticed dry-run skipped the same lookup path, so a plan could say "create" while production would still choke on duplicates.

Worse landed minutes later. Production sync created draft Order Cancelled and Order Refunded flows before any API metric existed for those names. Klaviyo bound the drafts to a non-API metric (MCP or sample, I never pinned which row). My note that evening said the trigger had drifted from an API trigger to something that would never see Centra traffic, so the automation stayed dead while the UI looked configured.

API integration, skip, seed

Same-name metrics are normal. Centra's API metric often appears only after the first real order event of that type. Creating a flow early attaches the trigger to whichever duplicate wins the name lottery.

The second patch was stricter. API integration only, always. No "only match, so use Shopify." Missing API metric means skip that flow for this run, not fail the pipeline. We also taught the script to ignore Klaviyo's Account is not eligible for transactional messages. Wrong trigger meant delete the flow and recreate; the bad drafts were gone the same evening. Shoppers on production did not miss mail from that mistake: production only received draft flows, and drafts do not send. The gap stayed on staging QA until we fixed the trigger wiring.

The third piece was a metrics:seed step that posts backfill events so API metrics exist before flow creation. The first API call failed with Your API key is missing required scopes: events:write. After the scope landed, production registered four metrics and four draft flows without starting automations. Klaviyo's developer docs state backfill events are stored for reporting but do not trigger flows, which is exactly what I wanted for seeding.

Simulation

Which metric does your flow listen to?

Fake Klaviyo account: same display name, different metric sources. Pick a lookup rule, create a flow, then fire order events or seed backfill.

Metrics named “Placed Order”

  • m-mcpMCP

No flow yet.

One MCP Placed Order metric. No Centra API metric until you fire an order or seed backfill.

Metric lookup rule

Try creating a flow under the prefer-API fallback rule, fire a Centra order, and watch the automation stay silent; then reset, switch to API only, and compare.

Display name is not identity. Bind flows to the integration source you trust, refuse sole-match fallbacks on ambiguous names, skip a flow instead of failing an entire deploy, and seed missing metrics with backfill so CI can run before the first shopper checks out. I still grep metrics by name when debugging. I no longer treat that string as unique.

Happy coding! Sander