klaviyo has been telling me our
gmail complaint rate is 0.
not low. zero. every account,
every month, for years.
it is zero because gmail sends
complaint data to no esp at all.
there is nothing for klaviyo
to report. never.
google has the real number and
publishes it daily.
it will not tell you which send
caused it.
so every week i exported both,
lined the dates up in a sheet,
squinted, and guessed.
then again for the next brand.
i have run email since 2014,
now for 10+ dtc and digital app
brands doing $75m a year combined,
and this is genuinely how
i spent my mondays.
so i built the join.
it names the campaign behind the
spike day and tells you how
confident it is. exact match,
likely, or possible. never
dressed up.
$189 once. never a subscription.
i am tired of those too.
demo runs on fake data.
no signup, no card.
link below.
litmus published 100+ black friday and cyber monday subject lines.
100+ examples of what got sent.
zero context on what worked.
still worth bookmarking.
just know what it is:
a swipe file.
not a test plan.
every line comes without the audience, offer, sender reputation, mailbox mix, placement, revenue, or complaint rate that gave it meaning.
you see the copy.
not the conditions.
and open rate cannot fill in the blanks.
apple MPP, machine activity, and mailbox differences make opens a directional signal at best, and only in a like for like comparison.
before you borrow a line, open your own holiday send history.
compare similar audiences and offers.
then put the subject next to clicks, conversions, revenue per recipient, unsubscribes, complaints, and placement by mailbox provider.
the list is the menu.
your data is the bill.
nobody publishes both.
i built a tool because i was tired.
no, not another general one.
it does one thing.
it tells you which klaviyo campaign or flow
was behind a gmail spam spike.
for twelve years my week went like this.
postmaster goes red.
i export postmaster.
i export klaviyo.
i line the dates up in a spreadsheet
and i squint until something looks
like it might be the one.
then the next brand.
ten of them a week.
i was guessing, and i knew it.
and it is not a klaviyo problem.
gmail does not send per-message
complaints to any esp.
nothing comes back at all.
so the complaint rate you read in klaviyo
is every provider except gmail.
and gmail is most of your list.
google's own line is 0.10%,
and never 0.30%.
their words for what comes after are
"increased spam classification".
and nothing bounces when you cross it.
gmail takes the mail
and then decides where to put it,
while klaviyo writes down delivered.
somebody always says
postmaster has a feedback loop tab.
it does. i lived in that tab.
what is in it is identifiers.
a 26-character one is a campaign id
and you can match that.
a 6-character one looks like a flow id,
so you export your flows, match it,
and get nothing back. every time.
it is not a flow id.
it is the id of one message inside the flow.
so that is what i built.
spamspike reads postmaster and klaviyo,
read-only, and turns those identifiers
back into names you recognise,
labelled identified, likely or possible.
on a day google named nothing,
it tells you that
instead of picking something.
the other half is the part i never had.
you gate a flow on monday
and by friday the 90-day average
has barely twitched,
so the client asks if it worked
and you say give it time,
which is what we all say
when we don't know.
0.07% for 86 days
and 0.00% for 4
still averages 0.067%.
honest, and no use to you.
so it counts from the day
you mark the fix done.
too early, not measurable,
then improved, worse or unchanged.
and since this week you can just ask it:
claude, chatgpt, gemini, cursor, codex.
paste one url,
ask which send sat behind the spike on aug 27
and it answers from your own postmaster
with the source on every number.
read-only, revoke in one click,
no extra charge.
one more thing i cannot explain yet.
on every account i have pointed this at,
the top row of that feedback loop tab
is not a send.
not a campaign, not a flow.
if you own one brand:
the flow behind the spike by name,
and a warning before the next send goes out.
if you run ten:
all of them on one screen
against google's line,
checked every six hours.
one licence covers ten klaviyo accounts
and your team.
klaviyo first because that's where the market is
but i am not limiting this.
other esps are coming on the same licence.
two licences sold so far.
two more than i expected.
one payment, no subscription
because this community needs value
not another sub in pocket.
if something here is wrong, tell me.
i'll fix it, or say so publicly.
link in the comments.
@InstantlyAI@InstantlyAI how you're dealing with Validity new release? This looks major for tools like instantly for robotic warmup etc. https://t.co/bs4KqYUkkJ