1 19000057079 2017-01-23T14:26:54-05:00 19000151098 false Glossary 5 2018-03-16T10:15:25-04:00 1 1 2017-01-23T14:28:04-05:00 0 0 When creating fields within your DataMart there are 4 different data types to make note of: Email Address - This data type is for collecting email addresses for your contacts for use with segmentation and deploying email type communications. In most situations, this will also be your "Identifier" field. Text - This is the most common field type. The majority of the data you collect will be text. Common uses for this type are First Name, City, or dynamic content you wish to have appear in your email messages. Date - This data type is for collecting dates that you wish to use for segmentation purposes. Any date field information should be ordered according to standard North American format (month, day, year). Number - This data type is for collecting numbers that you wish to use for segmentation purposes. Common uses for this type are Total Donations, Revenue or other monetary related numbers. UMPIRE stores these numbers up to 2 decimal places. <p>When creating fields within your DataMart there are 4 different data types to make note of:</p><p><br></p><ol> <li> <strong>Email Address - </strong>This data type is for collecting email addresses for your contacts for use with segmentation and deploying email type communications. In most situations, this will also be your "Identifier" field.<br><br> </li> <li> <strong>Text - </strong>This is the most common field type. The majority of the data you collect will be text. Common uses for this type are First Name, City, or dynamic content you wish to have appear in your email messages.<br><br> </li> <li> <strong>Date - </strong>This data type is for collecting dates that you wish to use for segmentation purposes. Any date field information should be ordered according to standard North American format (month, day, year).<br><br> </li> <li> <strong>Number - </strong>This data type is for collecting numbers that you wish to use for segmentation purposes. Common uses for this type are Total Donations, Revenue or other monetary related numbers. UMPIRE stores these numbers up to 2 decimal places.</li> </ol><p><br></p> 19000151098 139 19000043335 2018-01-15T09:26:22-05:00 19010004040 1 2 0 0 Field Data Types 2017-01-23T14:28:04-05:00 19002521488 1 2017-01-23T14:32:32-05:00 0 1 Deployment indicates the act of combining a message with a list of recipients for the purpose of sending them content through UMPIRE.  This could mean that you are sending an email message to a list of 1000 recipients through UMPIRE or you have a Welcome program in operation and when a new subscriber enters your DataMart, it becomes a recipient and is sent the first message in your welcome program.  There are a few different ways of creating a deployment in UMPIRE.  The first is creating a Bulk deployment through the "Deploy" tab.  This allows you to select a subscription, segment, or list file as your list of recipients and select a message that you have created in the Compose tab.  The second option is to set up an AutoProgram in the "Automation" tab.  This allows you to define (using a segment) your recipients and if new subscribers will become recipients as well.  It also allows you to choose a path of messages that each recipient will receive.  <p>Deployment indicates the act of combining a message with a list of recipients for the purpose of sending them content through UMPIRE. </p><p><br></p><p>This could mean that you are sending an email message to a list of 1000 recipients through UMPIRE or you have a Welcome program in operation and when a new subscriber enters your DataMart, it becomes a recipient and is sent the first message in your welcome program. </p><p><br></p><p>There are a few different ways of creating a deployment in UMPIRE. </p><p><br></p><ol> <li>The first is creating a Bulk deployment through the "Deploy" tab. <ul><li>This allows you to select a <a href="https://support.umpiredigital.com/entries/22926298" target="_blank">subscription</a>, segment, or list file as your list of recipients and select a message that you have created in the Compose tab. </li></ul> </li> <li>The second option is to set up an AutoProgram in the "Automation" tab. <ul> <li>This allows you to define (using a segment) your recipients and if new subscribers will become recipients as well. </li> <li>It also allows you to choose a path of messages that each recipient will receive. </li> </ul> </li> </ol><p><br></p> 19000151098 145 19000043337 2018-01-15T09:28:02-05:00 19010004040 2 2 0 1 Deployment 2017-01-23T14:32:32-05:00 19002521488 1 2017-01-23T14:39:00-05:00 0 0 Behind every database is set of data points that you have decided to collect. These points provide not only a way to organise the data you collect, but also allow you an easy reference point to segment on. Fields are data points that you have pro-actively decided to collect within your database. Fields can be anything from email address to postal code to the last purchase you made. In order to utilise Fields properly in UMPIRE, this requires some pro-active thought. It is recommended that you Map out each of the data points you will be collecting from your customers and then set up each field in your DataMart.  Once you have these fields set up, you are able to not only map incoming data to these fields so that your database stays organised, but you are also able to easily segment your data using these fields AND use the field names in your templates to pull in data. <p>Behind every database is set of data points that you have decided to collect. These points provide not only a way to organise the data you collect, but also allow you an easy reference point to segment on.</p><p><br></p><p><strong>Fields</strong> are data points that you have pro-actively decided to collect within your database.</p><p><br></p><p>Fields can be anything from email address to postal code to the last purchase you made. In order to utilise Fields properly in UMPIRE, this requires some pro-active thought.</p><p><br></p><p>It is recommended that you Map out each of the data points you will be collecting from your customers and then set up each field in your DataMart. </p><p><br></p><p>Once you have these fields set up, you are able to not only map incoming data to these fields so that your database stays organised, but you are also able to easily segment your data using these fields AND use the field names in your templates to pull in data.</p><p><br></p> 19000151098 114 19000043339 2018-01-15T09:30:02-05:00 19010004040 3 2 0 0 Fields 2017-01-23T14:39:00-05:00 19002521488 1 2017-01-23T14:44:21-05:00 0 0 The driving force behind any email program is the Opt-in/Opt-out process that has been put into place. This will allow customers to start receiving your email campaigns or stop receiving them.  Subscriptions helps you manage this process. Subscriptions are a collection of people who have decided at one point to receive or not receive, all or specific email communications from your company.  In a majority of cases, email programs only have one Subscription.  The customer either does or doesn't want to receive all email publications from you. However, some email marketing programs are little more sophisticated.  Many programs have a Monthly Newsletter, as well as Promotional email alerts. Then the option to opt-in or opt-out to one or both of the campaigns is presented.  This is where Subscriptions shine. They allow you to manage each opt-in/opt-out process in one Community.  You are able to see the total size of each subscription, segment on this subscription and deploy email marketing direct to it.  There are even users that have a preference page that Subscriptions can manage.  This preference page provides their customers to opt-in/opt-out of different types of alerts so they can customize their email experience with your company. UMPIRE Subscriptions provides each user the flexibility to manage the simplest of email programs to the most complicated. <p>The driving force behind any email program is the Opt-in/Opt-out process that has been put into place. This will allow customers to start receiving your email campaigns or stop receiving them. </p><p><br></p><p>Subscriptions helps you manage this process.</p><p><br></p><p><br></p><p><strong><u>Subscriptions</u></strong><u> </u>are a collection of people who have decided at one point to receive or not receive, all or specific email communications from your company. </p><p><br></p><p>In a majority of cases, email programs only have one Subscription. </p><p><br></p><p>The customer either does or doesn't want to receive all email publications from you. However, some email marketing programs are little more sophisticated. </p><p><br></p><p>Many programs have a Monthly Newsletter, as well as Promotional email alerts. Then the option to opt-in or opt-out to one or both of the campaigns is presented. </p><p><br></p><p>This is where Subscriptions shine. They allow you to manage each opt-in/opt-out process in one Community. </p><p><br></p><p>You are able to see the total size of each subscription, segment on this subscription and deploy email marketing direct to it. </p><p><br></p><p>There are even users that have a preference page that Subscriptions can manage. </p><p><br></p><p>This preference page provides their customers to opt-in/opt-out of different types of alerts so they can customize their email experience with your company. UMPIRE Subscriptions provides each user the flexibility to manage the simplest of email programs to the most complicated.</p><p><br></p> 19000151098 131 19000043343 2018-01-15T09:34:45-05:00 19010004040 4 2 0 0 Subscriptions 2017-01-23T14:44:21-05:00 19002521488 1 2017-01-23T14:50:07-05:00 0 0 Record types give the user the flexibility to flag individuals in their DataMart as employees or account stakeholders so that they may be included in certain processes throughout the email campaign. Listed below are the different types of records that can be flagged in the system. 1.  Test Accounts Test Accounts are defined in UMPIRE as email addresses used solely for testing purposes.  This might be Gmail or Hotmail accounts that would be used to see how a campaign is rendering in different email clients. They can also be individuals who want be included in all testing deployments such as the Campaign Manager. 2.  Stakeholders Stakeholders are defined in UMPIRE as individuals who follow a campaign from start to finish and wish to be included in the process.  You can add stakeholders to any testing that is being performed on a campaign and you can include them in the final deployment. For a company, Stakeholders might be department leaders or managers.  For an agency, Stakeholders might be account managers or key client contacts. You may include Stakeholders at any time, so it is important to only choose to add them to a deployment/test when you are ready for them to see the campaign. 3.  Seed List Seed lists are similar to stakeholders, however this separation is provided as Seed lists can only be used in final deployment and are added in with the regular customers. Seed lists tend to include executives and other individuals who wish to see final deployment as the customer sees it. Note: Records flagged as a Seed List will not be included in the final metrics <p>Record types give the user the flexibility to flag individuals in their DataMart as employees or account stakeholders so that they may be included in certain processes throughout the email campaign.</p><p><br></p><p><strong>Listed below</strong> are the different types of records that can be flagged in the system.</p><hr><p><br></p><h2>1.  Test Accounts</h2><p><br></p><ul> <li>Test Accounts are defined in UMPIRE as email addresses used solely for testing purposes. </li> <li>This might be Gmail or Hotmail accounts that would be used to see how a campaign is rendering in different email clients.</li> <li>They can also be individuals who want be included in all testing deployments such as the Campaign Manager.</li> </ul><hr><h2>2.  Stakeholders</h2><p><br></p><ul> <li>Stakeholders are defined in UMPIRE as individuals who follow a campaign from start to finish and wish to be included in the process. </li> <li>You can add stakeholders to any testing that is being performed on a campaign and you can include them in the final deployment.</li> <li>For a company, Stakeholders might be department leaders or managers. </li> <li>For an agency, Stakeholders might be account managers or key client contacts.</li> <li>You may include Stakeholders at any time, so it is important to only choose to add them to a deployment/test when you are ready for them to see the campaign.</li> </ul><hr><h2>3.  Seed List</h2><p><br></p><ul> <li>Seed lists are similar to stakeholders, however this separation is provided as Seed lists can only be used in final deployment and are added in with the regular customers.</li> <li>Seed lists tend to include executives and other individuals who wish to see final deployment as the customer sees it.</li> <li> <strong>Note</strong>:<span> </span>Records flagged as a Seed List will not be included in the final metrics</li> </ul> 19000151098 112 19000043346 2018-01-15T09:36:56-05:00 19010004040 5 2 0 0 Record Types 2017-01-23T14:50:07-05:00 19002521488