Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog
D
e
m
o
Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog
D
e
m
o
Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog
Home
Knowledge base
Knowledge base
PMTA knowledge base
›
Scenario
Tracking infrastructure
entries in this scenario: 11
html-edit-error-mode
<signals>
Directive
Refuse delivery or send as is when HTML parsing failed; the default is to refuse.
custom-message-id-header
<signals>
Directive
The name of the header with your message identifier; the service uses it to link opens and clicks with the other events.
engagement-tracking
<signals>
Directive
Three values: do not collect, send the events yourself or let the engine insert links and pixels; the default is not to collect.
tracking-domain
<signals>
Directive
The domain that inserted links and pixels point to; the default is the vendor’s domain.
enable-bottom-open-pixel
<signals>
Directive
The switch for one of three kinds of insertion; works only with tracking done by the engine, on by default.
enable-click-tracking
<signals>
Directive
The switch for one of three kinds of insertion; works only with tracking done by the engine, on by default.
enable-top-open-pixel
<signals>
Directive
The switch for one of three kinds of insertion; works only with tracking done by the engine, on by default.
use-https
<signals>
Directive
Makes inserted links encrypted; requires your own tracking domain with a certificate; off by default.
The node can insert pixels and rewrite links by itself
Mechanism
In the vendor’s tracking mode the engine parses outgoing HTML, rewrites links to the tracking domain and inserts open pixels — with a choice of what to do if the markup cannot be parsed.
Markup parsing and editing
Mechanism
Open and click tracking in
sparkpost
mode edits the message markup with the built-in gumbo-parser; by default a message whose markup could not be parsed is bounced.
Hand a message to a webhook instead of a receiver
Mechanism
The queue sends the message as a POST request in the form of a JSON object; only a 2xx response counts as success.