Glossary
Below you will find a list of the most common terms used within Flows by Enreach.
| Term | Description |
Automation |
An Automation is a way to automate Campaign Flows in Flows by Enreach, and create automatic communication flows to specific Segments of Leads. |
API Incoming Log |
An API Incoming Log will allow you to view a log of each time a Lead was used within an API Request. |
Blacklist |
A Blacklist, or Stoplist, is a list of Leads who have requested that they no longer want to be contacted, for example through a complaint or clicking an unsubscribe button Leads on a Blacklist won't be used in activities if it is configured in the settings. |
Campaign |
Campaign refers to a group of Leads that will be called within Telemarketing. Campaigns are usually built around one purpose. |
Change Log |
Change Logs will allow you to view all historical changes made within a certain part of Flows by Enreach, such as in the Segment builder. |
.csv File |
A .csv file, or comma-separated values file is a plain text file, usually created in Excel, that contains a list of data. .csv files are quick and efficient ways to upload large amounts of Lead data to Flows by Enreach. Learn how to create a .csv file here. |
Export List |
Export Lists will allow you to create a scheduled export of data from Flows by Enreach. Export Lists can be used in an Automation to automatically send a list of data to a preconfigured recipient, for example which email addresses bounced or reported the Email activity as spam |
Facebook Audience List |
Facebook Audience List is a way to create targeted Facebook ads that your Leads will see. |
Field Mapping |
Field Mapping is a way to create links between data types in two different systems. So for example, if you need to map Lead data between Outbound by Enreach and Flows by Enreach, you would connect the name of the Field in Outbound to the equivalent name in Flows. |
GDPR |
GDPR, or the General Data Protection Regulation are European laws that dictate how companies are allowed to store personal information and client data. Flows by Enreach is GDPR compliant. |
Goal |
Goals are custom created checkpoints that are used to track Lead activity, and trigger other actions. There are two types of Goals in Flows by Enreach: Automation Goals that are used within an Automation Flows, and Condition Goals, which measure how many Leads meet the condition criteria specified in the Goal configuration. |
Lead |
A Lead is an individual that has given their Permission to receive communications from your Organisation. |
Lead Data Fields |
A Lead Data Field is the name for each category of data belonging to a Lead. Lead Data Fields can be uploaded manually or via .csv file, or exported as a .csv file. |
Lead Log |
Lead Logs will allow you to view all of the Leads uploaded to a certain Lead Source, and work with individual Leads through the Lead Overview page. |
Lead Source |
A Lead Source is a method for uploading Leads to Flows by Enreach, either through an API, FTP, .csv file, or a Landing Page. Lead Sources will also determine the rules for validating Leads, Duplicate Rules, Permissions, and more. |
LifeCycle |
LifeCycle refers to all of the stages a customer moves through, from a prospective Lead, to a returning customer. In Flows by Enreach, you can create a LifeCycle for any occasion, and track Leads as they move through. |
LifeCycle Status |
A LifeCycle is made up of LifeCycle statuses. These describe the point reached by the Lead in the customer journey, and will allow you to plan your communications and actions. |
Mergefield |
A mergefield will allow you to replace data types such as a first name or country, and replace it will the Lead's information. Using mergefields in your communications enables you to quickly and simply create personalised communications. |
Order Confirmation |
A form sent to a Lead to confirm a purchase. In Flows by Enreach, use the Order Confirmation page to create custom Order Confirmations to send to your Leads. |
PersonID |
A individual ID given to each Lead in Flows by Enreach. |
Permission |
When a Lead gives consent to receive communications, such as a newsletter or a telemarketing call, they are giving their permission. Flows by Enreach has a Permission module where you can create permission lists, and remain GDPR compliant. |
Playbook |
A Playbook is a saved template created when working with Automations. Playbooks allow you to reuse Automation flows, and make necessary adjustments, instead of creating a new Automation flow each time. |
Pop-up |
Pop-ups are small windows that appear to visitors when they browse websites. You can create various types of Pop-ups in Flows by Enreach to convey information, or collect details from Leads. |
Pop-up Group |
In Flows by Enreach, a Pop-up Group is a container for different Pop-ups that will be displayed on the same website. A Pop-up Group has the same script installed for the website, and will determine when are where the Pop-ups will appear on your website. |
Segment |
Segments are a way to filter Leads based on a customisable set of rules. Segments are used to target specific groups of Leads. |
Stoplist |
In the Stoplist page of Flows by Enreach, you can create Stoplists, or Blacklists, to collect Leads that have requested to end communications with your Organisation. |
Telemarketing |
Telemarketing is a way to sell goods or services by calling Leads directly on the phone. In Flows by Enreach, you can connect with Outbound by Enreach to make Telemarketing calls. |
Telemarketing Agencies |
Telemarketing Agencies refer to a team of Agents who call Leads. Within an Agency are the various Telemarketing Campaigns, which are created to contact Leads with one specific purpose. |
Transaction Types |
In Flows by Enreach, a Transaction Type is a type of payment method that you can configure and integrate into your external eCommerce system. |
User |
A User is an individual with access to Flows by Enreach. |
Webtracking |
Installing your website with a Webtracking script will allow you to collect various types of data, such as unique users, page visits, device used, and orders placed. |