When are custom thresholds worth it for Subject line fits the inbox?
When are custom thresholds warranted?
Override `maxSubjectLength` when you know your audience's clients better than a general default can. A sender whose analytics show overwhelmingly mobile opens might tighten it to forty, which is the honest limit for those apps and produces subjects that never truncate for the people actually reading. A team with desktop-heavy business readership might raise it toward seventy, accepting mobile truncation as a considered choice rather than an accident.
When should you stay on Standard?
Stay on sixty when you do not have reliable client mix data, because it is the value that is least wrong across a mixed audience. Keep the default when several teams or brands share the check and you want their results comparable. If you are tempted to raise the limit to make a specific subject pass, that is a signal to edit the subject rather than the threshold — the inbox does not read your configuration.
What do you trade away?
Tightening to a mobile-honest number produces far more failures and real editorial constraint, which is the point but also the cost: copywriters have to work inside it, and a limit nobody accepts gets ignored. Raising the value quietly reintroduces the failure it was meant to catch, since a passing verdict then means "fits some inboxes" rather than most. Because the measurement is characters rather than rendered width, a very tight custom limit still cannot promise a specific client's exact cut point.
Community Standard vs org Custom
The Standard sixty is a conservative reading of published client behaviour, chosen so a pass means something without configuration. A Custom limit is a claim about your own audience and should be sourced from your open data, with a note of when it was measured — client mix shifts, and a limit set from three-year-old analytics is a guess wearing evidence's clothing. Keep it with the rest of your campaign standards so copywriters see it before they write, not after they fail.
Worked override examples
A consumer brand whose opens are 80% mobile sets `maxSubjectLength` to `40`, forcing front-loaded subjects that survive the smallest window its real audience uses. A B2B sender with desktop-heavy readership raises it to `70`, matching desktop Gmail and accepting truncation on phones as a deliberate trade. A team running heavy personalisation keeps `60` but measures with the longest realistic token value, so the limit is tested against the worst case rather than the average recipient.
How does an agent call it with parameters?
{
"type": "email",
"validations": [
{
"id": "email-subject-line-length",
"parameters": {
"maxSubjectLength": 60
}
}
]
}