(custom properties) verifiedcriticalWritten by the Hub
Our own fields
Properties MailerQ does not recognise are carried through untouched and returned in the result.
In detail
The cheapest integration point in the whole product. A campaign id, a warm-up plan number, a customer reference — anything Hub puts into the job comes back in the result Hub already collects, with no extra call, no lookup and no correlation by timestamp. Two things to establish before relying on it. Whether such a property can also be addressed in a log format — the templates use paths like {$email.recipient}, so {$email.campaign} ought to work, and that is an inference rather than an observation. And whether size matters: the property travels with every copy of the message through the broker.
What happens if you get it wrong
A property name colliding with one MailerQ uses.The engine interprets it as its own, and behaviour changes in a way that looks unrelated to the field that was added.inference · inference