Glossary

AMQP is an open standard for message-oriented middleware used by Momentum 4. For more information see ampq.org.

In a Momentum 4 cluster configuration, an aggregator or cluster aggregation node is a node used for cluster log aggregation. If you require log aggregation, you must install Momentum 4 on the aggregator first. An aggregator is referred to as a Platform node but it does not perform any messaging functions.

All messages based on a single piece of copy. A campaign contains recipients and template information. You may have a campaign group that contains related messages.

Tracking of clicks on the links within a message. In order to track clicks set the click_tracking field of the transmission object to true.

A component of the template that can include: html, text, SMS MMS rich media, push payload, or other recipient-viewable data.

When the recipient of a message performs the desired action; receiver goes beyond open and click.

The EEC is a global organization that strives to enhance the image of email marketing and communications, while actively advocating its importance to business. For more information see Email Experience Council.

Key value pairs associated with an injection which are included in the event stream and are available for filtering or reporting. These key value pairs are also given to the substitution engine as a convenience to the customer (with recipient metadata taking precedence over injection metadata when there are conflicts).

Injection-specific JSON data which is supplied to the substitution engine. Recipient substitution data takes precedence over injection substitution data. Unlike metadata, substitution data is not included in any event streams and is not available for filtering or reporting.

The concept behind "IP Warmup" is that new IPs need to build a reputation with ISPs. For example, if you send 100,000 emails from a newly acquired IP address that has no history, most large ISPs will block email from this address. IP Warmup slowly increases the send rate on new IPs so that ISPs have time to gauge customer feedback. If there are minimal spam/abuse reports then the ISP will allow an increased send rate.

Sometimes an IP with a good reputation will accidentally send bad content and damage its own reputation. In such cases, it may be necessary to re-establish a good reputation by temporarily suspending sending, reducing the send rate, or by "re-warming" the IP address. With Momentum, this is achieved using the adaptive module, which automatically sets any new bindings to "zero days old" and then slowly increases the send rate unless it starts seeing negative feedback. If this happens, the adaptive module throttles or temporarily suspends the IP address according to internal rules. For more information about the adaptive module, see “adaptive – Adaptive Delivery”.

JSON is a lightweight data interchange format. It is the input and output format used by the REST API.

The standard that specifies the format of email messages so that they can be exchanged between different MTAs.

Track the opening of messages.

During network communication, passively collect information about the remote device with the intent of inferring the OS. Doing this makes improved TCP/IP communication possible. You must install the Policy Tools suite to enable p0f.

In cluster configurations a quorum is the minimum number of active machines that will allow Momentum to continue functioning. Should any nodes go down, you need a quorum within both your Platform servers and within your Analytics servers in order for Momentum to continue functioning. For Momentum, 51% or more active nodes makes up a quorum.

Whenever quorum is lost and regained, the node(s) that lost quorum must inquire whether they have lost the jobs that they were previously working on. This is necessary to minimize the number of duplicate messages that are sent.

What constitutes a quorum has implications for redundancy. For example, you cannot support redundancy with only two Analytics and two Platform nodes. Should any one node go down, you will not have the 51% required for a quorum. Redundancy is only supported with clusters of three or more Analytics and Platform nodes.

Sum of links clicked per recipient, over multiple recipients. For example, Recipient 1 clicks 1 link. Recipient 2 clicks 2 different links. Recipient 3 clicks 5 different links (out of the 20 links in the message). That's a total of 8 Raw Clicks. Raw clicks are also known as "uncooked clicks".

Key value pairs associated with a recipient which are included in the event stream and are available for filtering/reporting. These key value pairs are also given to the substitution engine as a convenience to the customer.

Recipient-specific JSON data which is supplied to the substitution engine. Unlike metadata, substitution data is not included in any event streams and is not available for filtering or reporting.

Persons receiving a message. Typically information regarding recipients is extracted from a data store. Recipients are passed to the transmission API as JSON objects.

Web services available over HTTP. Using REST you can interact with Momentum 4 programmatically.

A self-contained specification of the basic protocol for the Internet electronic mail transport.

Specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages.

Message components (header, text, HTML, SMS, etc) submitted via API and Momentum will perform substitutions and assemble the multi-part MIME format.

Injecting a fully formed (multi-part MIME) message via an API (still subject to substitutions and tagging).

Generate messages by using an API that injects structured data to be used with a stored template.

Injecting a message via SMTP (rather than a template).

A system component that personalizes each individual message. It takes as input a piece of UTF-8 data which contains substitution syntax such as "Hello {{ name }}", and JSON representing the key/value pairs to be substituted. The engine outputs expanded UTF-8 data.

A client-defined label that can be applied to a message. Tags can be inherited from a campaign.

A collection of message components (headers, text, html, SMS and attachments). Each component (with the exception of attachments) is run through the substitution engine prior to construction of the MIME.

Every click in a message, including duplicates. You're counting clicks.

Every click on a particular link.

All conversions.

All opens that were recorded by open tracking.

A transactional message is a message that has only one recipient. The gen_transactional_threads option ensures that these kinds of messages are handled efficiently by minimizing database access wherever possible.

A collection of messages belonging to the same organization and the same campaign; also know as a mailing.

The number of recipients that clicked on any link in the message. You're counting recipients. From the example in Raw Clicks, that's 3 Unique clicks.

Number of recipients who opened messages. This is recorded using the open tracking pixel or, if images are blocked, it is recorded when the user clicks any link including the unsubscribe link. This metric applies to both HTML and plain text emails. (Unique Opens plus Unique Clicks that do not have a corresponding Unique Open.)

Number of recipients that convert.

Number of recipients who opened messages. This is recorded by the open tracking pixel.

This technique specifies a different return path for every message making it possible to associate bounced message with a specific sender so that invalid addresses can be removed from mailing lists. For more information see "RFC 3464".