This article provides a detailed comparison of compatibility features across four marketing channels: OptiMail, Mobile Push, Web Push, and OptiText. It covers campaign types, editor options, personalization capabilities, content components, additional channel features, and the specific ability to preview and test data connections in OptiMail.
Types of Campaigns
The following table outlines the types of campaigns supported by each channel:
| OptiMail | Mobile Push | Web Push | OptiText | |
|---|---|---|---|---|
| Scheduled | Yes | Yes | Yes | Yes |
| Triggered | Yes | Yes | Yes | Yes |
| Transactional | X | N/a | N/a | N/a |
Types of Editors
The available editors for content creation vary by channel:
| OptiMail | Mobile Push | Web Push | OptiText | |
|---|---|---|---|---|
| Visual Editor | Yes | N/a | N/a | N/a |
| HTML Editor | Yes | N/a | N/a | N/a |
Personalization Tags as Lookups in Formulas
Personalization tags enable dynamic content based on data lookups. The table below details their support:
| OptiMail | Mobile Push | Web Push | OptiText | |
|---|---|---|---|---|
| Activity Data | X | X | X | X |
| Content Functions
, only date driven functions, following tags are not supported: LOWER../TITLE../UPPER |
Yes |
Yes | Yes | Yes |
| Content Management | X | X | X | X |
| Customer Data | Yes | Yes | Yes | Yes |
| General | Yes | Yes | Yes | Yes |
| Transactional Customers | X | X | X | X |
All channels support customer data and general tags for personalization. Content functions are planned for future support.
Content Blocks and Components
Content creation capabilities differ across channels, as shown below:
| OptiMail | Mobile Push | Web Push | OptiText | |
|---|---|---|---|---|
| Email Details: Subject | Yes | N/a | N/a | N/a |
| Email Details: Preview text | Yes | N/a | N/a | N/a |
| Email Details: From Name | X | N/a | N/a | N/a |
| Message title | N/a | Yes | Yes | N/a |
| Message content | Yes, select any text component, then Personalisation in context menu | Yes | Yes | Yes |
| Image | Yes, create data connection formula, then copy and paste in a field related to Image Url in the Image Properties area in components like Image, Stickers, etc. | Yes, add Image and choose URL tab | Yes, add Image and choose URL tab | X |
| Link | Yes, create data connection formula, then copy and paste in a field related to URL in components like Button, Image, Video, etc. | X, not supported in Open URL, however could be part of the Message | X, not supported in Open URL, however could be part of the Message | X, not supported in Open URL, however could be part of the Message |
| Common/Template settings | - | X | X | X |
Other Channel Features
Additional features enhance channel functionality:
| OptiMail | Mobile Push | Web Push | OptiText | |
|---|---|---|---|---|
| Content Tags | Yes | N/a | N/a | N/a |
| Conditional Language | Yes | Yes, but not as part of conditions | Yes, but not as part of conditions | Yes, but not as part of conditions |
| Template Translations | X | X | X | X |
| Preview | Yes* | Yes, as a tag, with no data | Yes, as a tag, with no data | Yes, as a tag, with no data |
| Smart Preview (for customer ID) | Yes* | N/a | N/a | N/a |
| Target group Preview | Yes* | N/a | N/a | N/a |
| Test Send | Yes* | N/a | N/a | N/a |
| Instant Previews | Yes* | N/a | N/a | N/a |
| Validate | X | N/a | N/a | N/a |
Note: Features marked with * are expanded on in the 'Ability to preview/test data from Data Connections in Optimail' section below.
Ability to Preview/Test Data from Data Connections in OptiMail
OptiMail's ability to preview and test data from various data connections is detailed below:
| Preview (any) | Test Send | Real Send (launch test campaign) | |
|---|---|---|---|
| CSV/JSON Data Connections created via upload or with API methods | Yes | Yes | Yes |
| External API Data Connections | X | X | Yes |
| Data Connections based on Opti-X Placements | Yes | Yes | Yes |
| If Data Connection primary key lookup value is Activity Data Tag (from triggered campaigns) |
Activity Data Tag not supported as a lookup value for primary key |
Activity Data Tag not supported as a lookup value for primary key |
X |
| If Data Connection primary key lookup value is a supported Content Function | X | Yes | X |
| If Data Connection primary key lookup value is Customer Data Tag | Yes | Yes | Yes |
| If Data Connection primary key lookup value is General Tag | X | X | Yes |
| If Data Connection primary key lookup value is Transactional Customers Tag |
Transactional Customers Tag not supported as a lookup value for primary key |
Transactional Customers Tag not supported as a lookup value for primary key |
X |
| If Data Connection primary key lookup value is exact value from your source | Yes | Yes | Yes |
|
If the Data Connection formula contains composite keys and they only include Customer tags, e.g., |
Yes | Yes | X |
|
If the Data Connection formula contains composite keys with a mix of different tags, e.g., |
No | No | X |
Compatibility Summary
This section summarizes the compatibility details from the tables above, providing a quick reference for all supported features and limitations.
- Creating Data Connections:
- Uploading CSV or JSON files in the Opti-X UI is supported.
- Creating Data Connections from an External API is only available via API methods and is not supported in the UI.
- Uploading CSV or JSON files via API methods is supported.
- Creating Data Connections from Opti-X Placements is supported in the UI and via API methods for Opti-X Recommend customers.
- Creating Linked Lookups can only be done via API methods, not in the UI.
- Data Structure and Keys:
- Pulling multiple records (e.g., multiple product recommendations) is not supported for any Data Connection type.
- Single primary keys are supported for all Data Connection types.
- Composite keys are supported for file-based Data Connections but not for External API, Placement, or Linked Lookup Data Connections.
- Feature Compatibility:
- Placeholders functionality is supported for External API and Placement Data Connections but not for file-based or Linked Lookup Data Connections.
- Linked Lookups are not supported with External API Data Connections.
- Channel and Campaign Support:
- Data Connections are supported in Scheduled and Triggered campaigns across OptiMail, Mobile Push, Web Push, and OptiText.
- They are not supported in Transactional campaigns in OptiMail.
- Personalization Tags as Lookups:
- Supported: Customer Data tags, General tags, and date-driven Content Functions are supported as lookup values across all channels.
- Not Supported: Activity Data tags, Transactional Customers tags, and non-date Content Functions (LOWER, TITLE, UPPER) are not supported as lookup values.
- Content and Feature Usage:
- OptiMail: Data Connection formulas can be used in the subject, preview text, message content, image URLs, and link URLs.
- Mobile/Web Push: Data Connection formulas can be used in the message title, content, and image URLs. They are not supported for the "Open URL" link action.
- OptiText: Data Connection formulas can be used in the message content only.
- Conditional Language: Data Connections are fully supported in OptiMail. In other channels, they can be used as an outcome but not within the conditions themselves.
- Template Translations and Common/Template settings do not support Data Connections.
- Preview and Testing in OptiMail:
- Data from External API Data Connections cannot be previewed or seen in a test send.
- Data from File-upload and Placement Data Connections can be previewed and test-sent.
- If the primary key is a Content Function, data will only appear in a test send, not in the preview.
- If the primary key uses General tags or a mix of different tag types in a composite key, data will not appear in previews or test sends.