Key Updates
SMS in Odyssey!
Now you can send personalized SMS messages in your Voyages! Whether it’s for event reminders or A/B tests, SMS helps you engage customers instantly and directly.
Audience members who have opted in and provided a mobile number will receive messages when they reach the new SMS element. Available in both static and continuous voyages. Ready to boost your marketing? Add SMS to your next Voyage and see the difference!
For full details, refer to the SMS element knowledge base article (coming soon).
Watch in Action
The updated UI for Omeda's Campaign tools is now available for users who have enabled the New UI in the navigation menu. These enhancements introduce a streamlined user experience for key features such as Scheduled Outputs (formerly known as Lead Gen), Promo Codes, Lead Scoring, and Hosted Content.
Promo Codes and Lead Scoring now feature a step-by-step guide on the left side of the page to assist users through the setup process. With the redesigned Scheduled Outputs pages, users can continue to create recurring audience outputs to Email Recipients and FTP sites. Additionally, a new feature has been introduced, allowing outputs to be sent directly to Amazon S3 buckets.
Watch in Action
Send Images via SMS!
SMS users can now send images through the SMS Builder. In the Message Content section, simply click "Insert Media URL" to send .jpeg, .jpg, .gif, or .png files under 5 MB. These messages will be delivered via MMS, which may affect the credit usage for each campaign.
Other Highlights
Message Types added to Add Customer Action in Zapier
Users can now map Cell Phone Number and SMS opt ins/outs from another source to Omeda's Message Types using the ‘Add Customer Action’ in Zapier.
Download Product Details from the Product Dashboard
In the Products section of Client Empowerment, users can now easily download the product list as an Excel file for convenient access or external analysis.
Update to Product Magazine Mapping to remove Active Version
To improve the mapping process and prevent any potential errors, users will no longer be able to map to the 'Active Version' field from the Product-Magazine mapping section. The 'Active Version' is typically set during the Issue Close process, and users should not need to manually interact with it.
For magazine version requests, please map to the 'Requested Version' field instead. Any existing template that currently has Active Version mapped, will be updated to Requested Version for your convenience. Any existing template that has both Active Version and Requested Version mapped, the Active Version field will become ignored.