Importing ESP performance data

Your ESP knows what happened to your campaigns: sends, opens, clicks, unsubscribes. Inbox Decay knows what your infrastructure looked like while they happened. Imports connect the two, so a dip in opens can be read next to the infrastructure state of the exact route those campaigns traveled.

Imports live at /app/imports and are available on every plan.

How an import works

You import either a snapshot (one campaign's or one period's numbers) or a historical bulk export from your ESP. Each import is mapped to one sending path, because performance belongs to a route: your Klaviyo numbers describe your Klaviyo path, not your domain in general. Within an import you can group by list, segment, campaign or source, and link individual campaigns.

Imported numbers appear on the mapped path's report, beside its check history.

The append-only rule

Imports are immutable, dated snapshots. Re-importing the same period doesn't overwrite anything; it appends to the historical record. The only thing you can edit afterwards is the mapping (which path the import belongs to), and deleting is a soft archive, recoverable rather than gone.

This is stricter than a spreadsheet, on purpose. Performance history is evidence. The value of "opens fell the same week the path's IP got blocklisted" depends on neither side of that sentence being editable after the fact.

What to import first

If you're new, don't backfill everything. Import the last two or three months for your main newsletter path and let monitoring run. The useful pattern emerges on its own: infrastructure events on one axis, engagement on the other, same route, same dates.

More in Monitoring & fixing

• Monitoring, alerts and what decay means
• Fix actions and the Action Items list
• Allowances, limits and what happens over them