The following terms are relevant to your usage of Iterable:
Blast campaign - This is just another name for a standard marketing campaign that goes out periodically to a list. Think of the many "weekly email newsletter" you get in your inbox. Read our Blast Campaign Overview.
Channels - Message channels are a way to manage unsubscribes for your different email types within Iterable. Read our Channels and Message Types guide.
Data feeds - Iterable supports JSON data feeds in order to customize/personalize the content you send out in your messages. An example e-commerce use case is to have a data feed of your on-sale items that gets automatically included into a template at send-time each morning.
Dynamic List - As opposed to a static list, a dynamic list is constantly updated by our system to include any subscribers that fit the criteria/segment that you specified when you first created the list. Read our Static and Dynamic Lists Overview.
Events - Events are actions that your users took, either relating to an email/push notification (e.g., opened an email), or on your site or mobile app (e.g., made a purchase). When an event is generated, it is thereafter associated with a user and can be used in segmentations and A/B tests. Read our Events Overview.
Experiments - Experiments, or A/B tests, allow you to test different aspects of an email or a campaign. We'll run the tests for you and can even pick out a winner automatically. Read our A/B Experiments Overview.
Integrations - Iterable can integrate with different systems in ways that will make your marketing more powerful and easy. We have integrations for Magento, Segment and Mixpanel, and can also integrate with almost any other system via our extensive APIs and webhook support. Read our Integrations guides.
Revenue Tracking - Iterable lets you track the revenue (or other conversion metrics) that has been generated from your campaigns by calling the Iterable Commerce API. This allows you to measure the ultimate effectiveness of your campaigns and their ROI. Read our Purchase and Revenue Tracking guide.
Segmentation - This is a way to identify subscribers that have different characteristics. Iterable supports any number of segments, each using any number of criteria. Segments can be very general (e.g., users subscribed in the last 30 days) or very specific (e.g., users that have purchased more than $100 in the last 2 months but have not opened any of our emails in the last 30 days). Read our Segmentation Overview.
Static List - You can put any subset/segment of your subscribers into a list. A static list just means that the list won't change in the future unless you explicitly make changes to it. Read our Static and Dynamic Lists Overview.
Triggered campaign - Triggered campaigns are messages that get "triggered" by an action taken by your subscribers. This could be something that happens on your website or app (e.g., an abandoned shopping cart), subscribing to a list or any other property that gets set for a user (e.g., they give you their birthday). Read our Triggered Campaign Overview.
Templates - Templates are like the blueprints for your messages (emails or push notifications). A simple template is static and contains all the content that will be sent out, but we also support more sophisticated templates that can include personalized information, logic and data feeds, all incorporated into the template at send-time. Read our Template Overview.
Workflows - Workflows are a very powerful feature. A workflow lets you map out exactly what to do with a customer segment, like sending a message, waiting a set amount of time (a "delay"), changing a property, etc. And workflows can be triggered by any event or property. Read our Workflow Overview.
Users - This is another term for your subscribers or contacts. Every email address you have in Iterable is a user or subscriber/contact. Read our User Profile Overview.
Webhooks - Webhooks are a way to notify a web service that something happened, and optionally to take an action. Iterable's webhook support is a way to integrate it with any 3rd party system or your own backend.