Knowledge base
html-edit-error-mode<signals>DirectiveRefuse delivery or send as is when HTML parsing failed; the default is to refuse.privacy-policy<signals>DirectiveReplaces the local part of the recipient address with a one-way SHA-1 hash; by default it is sent as is.api-key<signals>DirectiveExactly forty hexadecimal characters; without it the node will not start at all.custom-message-id-header<signals>DirectiveThe name of the header with your message identifier; the service uses it to link opens and clicks with the other events.engagement-tracking<signals>DirectiveThree values: do not collect, send the events yourself or let the engine insert links and pixels; the default is not to collect.min-free-space<signals>DirectiveBelow this threshold the node starts deleting unsent export files; the default is 20 MB.process-x-sp-subaccount-id<signals>DirectiveAllows the submitting side to assign a subaccount with a message header; the number from the header overrides the one set by the configuration.retain-x-sp-subaccount-id<signals>DirectiveKeeps the service header in the message and makes it possible to write its value to accounting files; the line is shared with the seeding block.tracking-domain<signals>DirectiveThe domain that inserted links and pixels point to; the default is the vendor’s domain.enable-bottom-open-pixel<signals>DirectiveThe switch for one of three kinds of insertion; works only with tracking done by the engine, on by default.enable-click-tracking<signals>DirectiveThe switch for one of three kinds of insertion; works only with tracking done by the engine, on by default.enable-top-open-pixel<signals>DirectiveThe switch for one of three kinds of insertion; works only with tracking done by the engine, on by default.log-verbose<signals>DirectiveAdds messages about the export of events to SparkPost Signals to the log; off by default.use-https<signals>DirectiveMakes inserted links encrypted; requires your own tracking domain with a certificate; off by default.customer-id<signals>DirectiveBefore version 5.5 it was required for engine-side tracking; since 5.5 it is not needed.upload-url<signals>DirectiveThe event intake endpoint; by default the vendor service’s address.