Glossary of Terms

Anonymous Contacts: visitors who have not yet been identified by any interaction. These contacts are tracked by Mautic via IP address but typically remain hidden so as not to clutter segments.

API: (Application Programming Interface) provides a way to pass data in and out of Mautic to/from other software programs. API is a code that allows two software programs to pass information back and forth (communicate with each other). The code of the API spells out the proper way for a developer to write a program that enables this communication between the two programs.

API Settings: users have the ability to enable access to the API under the configuration settings. Users are also have the ability to enable HTTP basic authentication for Mautic’s API — and it is highly recommended to only use this when using secure sites (HTTPS).

  • Access token lifetime (in minutes) – If using OAuth2, set the lifetime of the access tokens used to authorize the request.
  • Refresh token lifetime (in days) – If using OAuth2, set the lifetime of the refresh tokens which is used to request a new access token once expired. Once the refresh token expires, reauthorization is required in the amount of days this field is set to.

Assets: items to deliver to contacts – typically upon completion of a form. Assets are trackable items and carry their own point values, history, and tracking statistics. Examples of assets would be a white paper, downloadable demo, any file of interest such as mp3, presentation, etc.

Campaign: a marketing activity that aligns components (i.e. assets, landing pages, forms) with the channels (i.e. email, social media, notifications, text messages) to nurture leads along a customized sales cycle. Campaigns have both time and triggered events. Automation and personal can happen together!!!

Campaign Builder: where campaigns are built, allowing users to build out specific actions, decisions and conditions. An action is defined as anything executed by Mautic (i.e. send email, modify contact segment). A decision is when a contact makes a decision (i.e. the contact decided to “open email” – users can build follow-up actions and conditions based off a decision in the campaign builder). A condition is based on known or unknown profile field values or submitted form data.

Campaign form: after a contact submits a form, a Campaign Form allows users to send the contact immediately through a campaign.

Campaign Settings: users can use this setting to select the amount of times an action should be retried if it fails within a Campaign. This setting is looking beyond Mautic downtime or failed actions — this setting looks at downtime on the internet or on certain site hosting platforms.

Channels: channels are included on the left hand side of the Mautic screen, and include; Marketing Messages, Emails, Tweets, Text Messages, Focus Items, and Social Monitoring.

Components: the components menu contains: assets, forms, landing pages and dynamic content. This is where a Marketing Campaign starts – these items must be created before they can be used in a campaign.

Configuration: this is where users can setup and configure system settings, email deliverability and frequency rules, tracking code from a website, default platform settings.
Under configuration are the following tabs

  • System Settings
  • API Settings
  • Campaign Settings
  • Email Settings
  • Landing Page Settings
  • Tracking Settings
  • User/Authentication Settings
  • Webhook Settings
  • Social Settings

Contacts: known or unknown visitors. Contacts can be added 5 ways.

  • “Quick Add”.
  • “New” – this shows the contact’s whole profile where all detailed information can be added.
  • Upload a contact list – must be a CSV file in UTF-8 format.
  • Automatically when a contact fills out a form on website.
  • Via a plugin.

CORS: once set up, allows Mautic to speak to a user’s website for certain functionality. A user can add their full website as a valid domain and then turn it to “on” (advanced website content will not work properly if this is not setup correctly). Additional information can be viewed in our Setup and Configure Mautic Cloud guidebook.

Custom Fields: a user has the ability to create a field. For example, Mautic does not come with a “Birthday” field, but a user has the ability to create this field if it is helpful for the user’s particular, customized work flow.

Dashboard: a usher can customize their dashboard. The dashboard is the first screen users see when logging into their account. Users can customize the widgets that they would like to see that contain the information that a user wants to track.

DNS – Domain Name Servers is equivalent to a phone book for the internet. They maintain a directory of domain names and translate them to Internet Protocol (IP) addresses.

DKIM: DomainKeys Identified Mail is an email authentication method designed to detect email spoofing by providing a mechanism to allow receiving mail exchangers to check that incoming mail from a domain is authorized by that domain’s administrators.

Dynamic Content: allows users to add alternative content that will be seen by particular, pre-determined contacts. Mautic gives users the ability to embed content on a web page that can change out dynamically for known contacts. It is only associated with campaigns and can be used on your WordPress or Joomla websites. This is possible by pulling in the request from a campaign to determine what text is shown for known and/or unknown contacts. For example, Mautic makes it possible for contacts located in the United States to see different content than contacts who are located in Europe.

Emails: can be created in full HTML or basic text. in Mautic there are 3 types:

  • Form Emails are emails sent as an action to a contact after they submit a form. These are considered transactional emails and do not abide by the frequency rules set during configuration.
  • Segment Emails are considered marketing emails. Segment emails cannot be changed to transactional. A user can send a Segment email to a particular segment at a specified date and time. Note – each contact can only receive a segment email once.
  • Template Emails can be sent to contacts multiple times over multiple campaigns. These emails can only be used in campaigns. A user has the option to determine whether they’d like their Template Email to be Transactional or Marketing.

Email Settings: a user can set frequency rules for their emails. This will determine the frequency for which a contact can be contacted in a given time period. Contacts can choose their frequency rule by selecting their preference on an email preferences page which can be linked to in an email.

Focus Items: focus items are a type of web personalization that enable users to display a message, a form, or a link based on someone’s behavior on a webpage. These can be used to convert visitors into known contacts at the moment when they’re most engaged with the user’s brand. Focus items can include a form, message or personalized information for that contact.

Forms: used to collect user information, often in exchange for providing access to a download, an event registration, or an email newsletter. Forms allow users to collect data and add additional information to a contacts profile. There are two types of forms:

  • Campaign Forms: used to kickstart a campaign.
  • Standalone Forms: provides more immediate actions than a campaign form. This allows a user to push contacts to an integration, change segments, send email notifications and more immediately after a contact submits a form.

Integrations: enables users to manage the complete end-to-end marketing experience. Whether it is moving contacts into a CRM system when they are qualified, or using a plugin to embed forms and dynamic content right on a website.

Known Contacts: visitors who have identified themselves via a form or some other source. As a result, these contacts typically have a name, email address, and/or other identifying fields.
Known contacts have more detail, allowing users to build a nurture campaign based on the information that the contact supplied to the user. When contacts are known, it means that Mautic knows their email address and can start keeping track of all of their activity listing it under their contact record.

Landing pages: a landing page in Mautic can be used to promote content or provide a call-to-action. Landing Pages are created in the Landing Page Builder (once you select “Landing Page” from your left-hand-side menu, you come to a screen that allows you to “Launch Page Builder”). Once in the builder, users can drag and drop slots, text, buttons and more using a wysiwyg tool. Mautic allows for additional customization with the “code mode” tool where a user can use their own fonts, HTML, etc for a specific theme.

Landing page settings: users can add their Google Analytics script and tracking script for the user’s website. Mautic has the ability to track visitors who are not identified, they are called, “anonymous or unknown visitors” and we track unknown visitors once they have interacted with a marketing message. Once a visitor submits their email address, Mautic changes them from an unknown visitor to a known contact, allowing users to copy tracking code and enter onto each page.

Manage Actions: this allows a user to adjust a contacts’ points. These actions can be either positive or negative point changes based on a particular action that you determine.

  • Manage Actions: point actions – when a contact receives a change in their point totaly. These actions can be either positive or negative point changes and are based on a particular action as you determine.
  • Manage Triggers: point triggers – when a contact reaches a minimum number of points, the trigger is fired and an action is performed.  

Marketing Automation: a tool that saves time and increases sales. Marketing automation gives users the ability to set up repetitive marketing and sales tasks on predefined schedules, and by gathering critical and useful information into a central location to help sales teams focus on the right potential customers and leads at the right time.

Mautic: The world’s first and only true open marketing cloud solution.

MySQL: An open source relational database management system (RDMS) that is powered by the Oracle Cloud – MySql Cloud Service.

Points: allows users to leverage lead scoring. Points give weight to known contacts and potential leads. Points can be set up as Triggers or Actions within Mautic. If a contact reaches a minimum number of points (customized by the user), then the available trigger events are: “modify contact’s campaigns”, “Modify contact’s segments”, “Modify contact’s tags”, “Push contact to integration”, and “send an email”.

Point Triggers: a user has the ability to set point triggers once a contact reaches a particular minimum number of points (decided by the user). Once a contact reaches this number, the point trigger fires off an action.

Reports: are used to measure the performance of the user’s campaign(s), form(s), email(s), page hit(s) and more. There are many different reports that can be created within Mautic, allowing users to see how successful their nurture campaign is (or is not).

Roles: give users the ability to set up different permissions for their team members within Mautic. Once a user defines the role, they can apply it to the new user or team member they’re setting up.

Segments: a list of contacts based on certain criteria. For example, some marketers segment their contacts based on a contact’s location, so they can email that list of contacts a specific location-based offer or promotion.

Settings Gear: located at the top right hand side of your Mautic Dashboard, next to the account name. This is where you set up your Themes, API Settings, Email Settings, etc.

Single Sign-On (SSO): is a property of access control of multiple related, yet independent, software systems. With this property, a user logs in with a single ID and password to gain access to a connected system or systems without using different usernames or passwords, or in some configurations seamlessly sign on at each system.

Social Monitoring: users can add contacts to Mautic through Twitter mentions and hashtags. Note: the Twitter plugin must be configured within the plugins page. The app/console mautic:social:monitoring must be added to a user’s cron configuration.

Social Settings: users can select the Twitter handle field under this setting.

SPF: (Sender Policy Framework) is a simple email-validation system designed to detect email spoofing by providing a mechanism to allow receiving mail exchangers to check that incoming mail from a domain comes from a host authorized by that domain’s administrators.

Stages: enables a user to keep track of where their contacts are in their marketing/sales funnel. Stages are customized by the user.

Standalone form: a form that allows a user to set up multiple actions based off of a contact’s submission. A Standalone form does not have the ability to kick off a new campaign like a Campaign Form, but it can send a contact into a segment which can then be used to kick off a campaign.

System Settings: are located under ‘Configuration’. This is where users can edit different settings and features for their Mautic platform.

Under General Settings:

  • “Mautic’s root URL” – this is the landing page a user chooses to show when browsing to Mautic’s root URL (i.e. http://your-mautic-site.mautic.net/). A user can leave this blank to be redirected to Mautic’s dashboard by default.
  • “Default theme” – this is where a user can choose the theme that will give the landing page it’s look and feel. Once a user adds a theme under configuration, a user can navigate to the “Page Builder” (under “Landing Pages” tab) to fill in the contents. Note – Changing the theme after building a page may cause content to not display if the two themes do not use the same placeholders.

Under System Defaults:

  • “Default item limit per page” – sets the default number of items to display per page for all lists.
  • “Default timezone” – where a user sets the default timezone for the platform dashboard and reporting.
  • “Default language” – where a user sets the default language for the platform.“Cached data timeout” – some chart and table
  • data are cached to speed up the load. A user can define how often the cache should expire and refresh from the database to bring the latest data. A user can insert 0 to disable cache.
  • “Default format for full dates” – where a user can set the default format for full dates. A user can use PHP’s date format (http://php.net/manual/en/function.date.php) to customize. For example, ‘F j, Y g:i a T will be formatted to December 21, 2017 5:22 pm CST.
  • “Default format for short dates” – where a user can set the default format for short dates. A user can use PHP’s date format (http://php.net/manual/en.function.date.php) to customize. For example, D, M d will be formatted to Sun, Dec 21.
  • “Default format for date only” – where a user can set the default format for date only. Use PHP’s date format (http://php.net/manual/en/function.date.php) to customize. For example, F j, Y will be formatted to December 21, 2017.
  • “Default Time Only Format” – where a user can set the default format for time only. Use PHP’s date format (http://php.net/manual/en/function.time.php) to customize. For example, F j, Y will be formatted to December 21, 2017.

Under CORS Settings:

  • “Restrict Domains” – a user can is asked, “Would you like to restrict the domains that can send CORS requested to your Mautic installation?” And the user can select, “Yes” or “No”
  • “Valid Domains” – a user can enter the domains (http://yourdomain.com), one per line, to which a user would like to restrict incoming CORS requests.

Miscellaneous Settings:

  • “IP lookup service” – a user can set the service to use to lookup geographical information from an IP address. Some of the services listed are commercial serviced. Mautic is not affiliated with the listed services but provide them for convenience.
  • “IP lookup service authentication” – a user can set authentication credential(s) required by the selected service. For services that require a username and password, Mautic suggests for users to use the format username:password.
  • “List of IPs to not track contacts with” – users can list IPs (one per line) that should not be associated with contact tracking.
  • “List of Bots to not track with” – users can list Bots (one per line) that should not be associate with contact tracking.
  • “URL Shortener” – users can add their full URL (including access key) to the URL shortener that, when queried, returns a plain text shortened URL.
  • “Item max lock time (seconds)” – a user can set a time (in seconds) before an entity (email, segments, etc.) is automatically free.

Text Messages: in order to send a text message through Mautic, a user can either sign up for a text messaging service that’s integrated with Mautic, such as Twilio, or use Mautic’s proprietary solution. If you are interested in sending texts through Mautic’s proprietary service then reach out to sales@mautic.com.

Themes: Mautic comes pre-packed with a number of themes, which can be used ‘as-is’. It is also possible to create a theme from scratch within Mautic. Users can also have their theme developed and installed in Mautic.

Tracking Settings: located under ‘Configuration’. This is where users can:

  • Access the tracking code that a user can add to a 3rd party Landing Page (all Mautic Landing Pages are tracked automatically).
  • Identify visitors by IP – if enabled, unidentified visitors with the same IP address as an existing contact with be tracked as that contact.
  • Identify visitor by tracking URL – if enabled, returning visitor is identified by tracking URL from channels (especially from emails) when no cookie exists yet. Note: Email field has to be marked as unique identifier and publicly updatable in Configuration.
  • Identify visitor by device fingerprint – if enabled, returning visitor is identified by device fingerprint when no cookie exists yet.
  • Facebook Pixel ID – this can be enabled on a user’s tracking page and can also be enabled on a user’s Mautic Landing Page.
  • Google Analytics ID – this can be enabled on a user’s tracking page and can also be enabled on a user’s Mautic Landing Page.

Tweets: a Twitter application has to be created for authorization. You are able to send a personalized tweet to a contact, display tweets for a contact with a valid Twitter handle, load additional information from the Twitter profile, or place a share button to landing pages.

Unique Identifier: the unique identifier within Mautic is a contact’s email address. If Mautic knows the contact, it will merge the contact action with the contact within Mautic that has the same IP address.

Users: based on their role and permissions, a user is someone that has access to the Mautic platform.

User/Authentication Settings: SAML SSO Settings – this is where a user can access the entity ID in the IDP. Users can also enter the names of the attributes the configured IDP uses for the established users and use a custom X.509 certificate and private key to secure communication between Mautic and the IDP.

UTF-8 Format: stands for Unicode Transformation Format that uses 8-bit blocks to represent a character. It is the dominant character encoding for the World Wide Web and is safe to use within most programming and document languages. All CSV files in Mautic must be in UTF-8 Format.

  • Limit: # of contacts to import per batch – we recommend leaving this at “100”, which is automatically set in Mautic.
  • Delimiter: how values are separated within your CSV – we recommend updating your CSV to match “,” delimiter in Mautic.
  • Enclosure: characters that enclose each field – we recommend updating your CSV to match ‘ “ ‘ in Mautic.
  • Escape: the escape character – we recommend updating your CSV file to match “\” in Mautic.

Webhook: Also called a web call back or an API push. Allows users to send data from Mautic to their 3rd party system seamlessly.

Webhook Settings: users can select chronological or reverse chronological order for the order that a webhook with several events will occur.