Release Notes: 2016

Table of Contents:

December 2016: v4.2.50

New Features / Changes

  1. Email Message: added the ability to set a pre-header text for email messages. See step-1 of editing an email message:


  2. List → Form Builder: added the option to be able to update existing contacts as well as add new ones. See option in step-1:


  3. API Documentation: 
    1. Added how to associate a Tag with an email message and how to get aggregated stats report based on a Tag. (Search for "tag" in the following: POST /api/emailsPUT /api/emails/POST /api/reports/query).
    2. POST api/contact_search: now you can indicate which fields you want to retrieve when doing a search by using the new 'selected_fields' array parameter. Till now all list fields would always get retrieved on a search. This feature allows for faster queries if you don't need to retrieve all list fields. 

November 2016: v4.2.00

New Features / Changes

  1. List → Segment: allow to add more than 31 days in behavioral time frame criteria (e.g., Opened and Sent):


  2. Campaigns → Events & Triggers: Event Type: List: option "Current List" renamed to: "Recurring Campaign" (clearer and more straightforward name of this option): 

     
     
  3. Import & Export completed notifications have been consolidated in order to reduce number of notifications:


  4.  Enabled the ability to overwrite an SMS message, as already exists with email messages:
     

  5. New List Settings Tab: "General Settings": contains "Apply Footer & Header" settings as well as "Welcome Email" setup. These settings were moved here from their previous location List  Manager → Edit List, as this is a more organic and intuitive location for these settings:
     

  6.  Added search filter functionality to Settings → Users Management screen, thus improving the UX for accounts managing many users:


  7. New Dynamic System Field for Message ID: {{ocx_message_id}} was added for your usage. Some customers were interested in adding this to the URLs of their email messages, so they can track click performance of messages, on their websites and back-end CRMs / Data Warehouses.
     

  8. List → Change/Delete Screen: add the ability to mark contacts with status "Complained":


  9. Form Builder: added examples of CSS code that can be used for styling the form:

     
  10. List → Form Builder: added "Responsive Design" checkbox. By checking this option, Ongage will automatically apply a responsive web design to this web form:

     


  11. Automatically add horizontal scroll-bar in analytics stats tables, when columns don't fit into screen:

     

September 2016: v4.0.283 

New Features / Changes

  1. Contact Activity Report → Export Combined Detailed Report: now contains Sent data in export CSV. Previously only open and click behavioral data was included in this CSV report. Now it also includes all Sent data as well.
  2. Added Amazon SES to the set of SMTPs that we support the ability to inject custom X-Headers. For more info, see Injecting X-Headers and the X-Header Replacement Tag aka Macro on this page.

August 2016: v4.0.248

New Features

  1. Added ability to duplicate (make a copy of) an Event. See new action icon:
     

  2. In List → Manager: Edit Suppression List page: added history of imports and exports:

     
  3. Import Page: new "Imported by" Column was added indicating the name of the Ongage User that issued that import:
     
     

  4. Unsubscribe date added to Contact Activity Report:
     
     

  5. List → Contact Manager → Search:  Added "Re-run" option, for faster and easier issuing of reports that you want to run again.
     
     
  6. List → Contact Manager → Search: now entire search criteria is indicated in the detailed report:


  7. Ability to set password for import zip file via the Ongage UI, on the account settings page:
     
     
  8. Preview Email Message: added new tab to also preview the Text part of the message:
     
     
  9. Preview Email Message: added the From Name and From Address to preview:
     
     

  10. Customize Unsubscribe Success Page: added separate plain text input box for unsubscribe redirect URL option, for easier less error prone entering of URL:
     
     

  11. Added ability to use MD5, SHA1, and SHA256 hashing all within the same email message. See: Advanced Hashing Functions. Till now you could use only one of the 3 in the same email message.

  12. Added ability to set the from name dynamically, when using SMS provider Twilio:

     
  13. Added Segment Search to List Settings -> List Level -> ESP/Segment Distribution (was previously missing here):
     
     

  14. Added warning notification to your Ongage Homepage notifications when you're approaching your contact limit.

June - July 2016: v4.0.91

New Features

  1. Ability to support more than one Dynamic HTML tag, in same email message (in the same campaign): till now we only supported the use of 1 tag in the same email message, now we support multiple. See Ongage Feeds: HTML, RSS, XML and JSON for more info about Dynamic HTML feeds.

  2. Added support for SHA-256 hashing: you can now encrypt your emails, using SHA-256 hash (in addition to SHA-1 and MD-5 that Ongage already previously supported). See Advanced Hashing Functions for more info on this topic.
  3. New Indeed XML invocation tag: Ongage has provided built-in Indeed practically since it's inception, It then went on to add a host of integrations to essentially all leading US Job-boards. Overtime Ongage in improved these integration and came out with a more dynamic invocation tag, that provides full user control as to which List fields to use when calling the Indeed XML API. This new invocation tag also supports using 2 different publication keys in the very same email message! For more details see The New Indeed XML Invocation Tag

April 2016: v4.0.28

New Features

  1. New updated GUI (Graphical User Interface): for a document outlining these changes see Ongage GUI Face-Lift: April 2016.

  2. Sparkpost setup, new optional setting for IP pool: Sparkpost provides customers the ability to buy dedicated IPs and put them into pools. You can now indicate the desired IP pool in the Ongage connection setting. For more about this see Setting Your Sparkpost IP Pool in Ongage.

March 2016: v3.8.111

New Features

  1. New default header and footer setting for your emails messages:
    You can now choose and set a default header & footer, that you'd like to automatically add to all your emails messages in a given list. This feature can be found in the 'Edit List' action under the List Management Page:

    1. For more about this feature, see: How to Set a Default Header and Footer.

  2. New API method for creating external segments (Beta): This feature is designed to serve a whole new set of Ongage customers, that do email marketing from within their own CRM. These customers don't have any need for the Ongage front-end, nor its robust segmentation and campaign management features, as those already exist in their CRM. On the other-hand, they are interested in Ongage's unique ability to easily and seamlessly connect to, and route emails via multiple ESPs/SMTP relays (and/or via multiple accounts on the same ESP/SMTP vendor). For more information about this feature please speak to your account manager.

  3. Enhanced Transactional API method with 2 new parameters- 'delay_send' & 'schedule_date': allowing users to send a transactional email, after some delay or at some set date and time in the future instead of immediately. See POST /api/notify_transactions

February 2016: v3.8.52

New Features

  1. New account level features: Ongage has now added account level views (aka across lists), to several of its modules, where you can see summarized data for all lists. You can access that view from the list drop down where there is now a new 'All lists' option:
     

    1. Analytics Reports: view aggregated stats for all lists.

    2. List Dashboard: list db data summary, of all lists in account.
    3. Calendar view of campaigns: see all scheduled campaigns across all lists in one calendar view.
    4. Note: Only Admin users can see all lists. If a General User has access to only some of the lists, then they will see an aggregation only for those lists they have access to.
  2. Send SMS text message in a Transactional campaign: we've added the ability to send SMS text messages using the Transactional API.

  3. Dynamic HTML don't send empty email: if HTTP call fails for a given recipient, then don't send empty email, and go on to next recipient.

  4. AdStation don't send empty email: if no content comes back from API call to AdStation for a given recipient, then don't send an empty email to that recipient.
  5. Welcome email stats per segment: if you use the Ongage segmented welcome email feature, you can now get email delivery and performance stats for those segments.
  6. Available X-Paths for a given RSS feed: Ongage now displays the available X-Paths for a given RSS feed, when entered into the RSS UI of the email editor.
  7. Added TLS option to private SMTP setup: You can now select to indicate TLS directly from the Ongage UI setup. Till now you had to contact Ongage support in order to turn this on. TLS is short for Transport Layer Security.
  8. Overwrite/replace an image in Ongage image library: you can now overwrite/replace an existing image in the Ongage image library. Till now you could add or delete only. This in essence enables the ability to change an image that will be displayed in an email, even after it was sent.
  9. Added "Targeted" column to Analytic reports: you can now choose to see the targeted value in all major Analytic reports (e.g., Aggregate, Matrix, etc.)
  10. API: we've added soft-bounce status for all contacts in the return set of the GET /api/contacts/cross_account method (an account level, across all lists, API method).

January 2016: v3.8.15

New Features

  1. Added new Jobs2Career dynamic 3rd party job content integration (documentation coming soon! Speak to your account manager for more details).
  2. 10 free responsive templates: we've added a new folder to the Content > Template Library called 'Ongage Free Templates', containing 10 responsive templates that you can use and tailor as you wish.
  3. Added new feed type- text: enabling you to populate the text part of your email with text content served from an external text feed (i.e., a URL that returns text content), typically from your content server or CRM. This feature is also perfect for your SMS campaigns that are text based messages!!

    {{ocx_feed_text{url=... }}}
  4. Ability to set image and tracking domains per campaign: in the configuration page of campaign setup (Step 3), under the 'Advanced Configuration' section, you can now set image and tracking domains per campaign. This setting will override the Account level setting (Settings > Hosting & Tracking domain).
     
  5. Added ability to include or exclude a segment by default: if you use for example a seed list in every campaign, you can now indicate to include it by default. Similarly regarding exclude segments. You'll find this new setting in the 'Advanced configuration', of the Segment Edit screen.
     

  6. Transactional campaigns have been added to all campaign drop-down menus system wide: prior to this upgrade, some campaign drop-down menus in the system were missing the transactional campaigns.
  7. Added additional campaign types to the Search page campaign filter: in addition to transactional campaigns (noted above), events (aka triggered campaigns ) and split campaigns have now been added to this filter.
  8. Segment IDs added to segment selection UI in campaign configuration page: (Step 3): for improved UI/UX.

  9. Added alphabetical sort to content library folders: now you can sort the the image and template folders alphabetically.

  10. Campaigns > Dashboard we'd added an ESP Filter.

  11. Easily Deactivate ESP Network Connections: with the new 'Deactivate' icon under that actions column of your Networking > Dashboard.
     

  12. API method POST /api/v2/contacts/remove has been replaced by POST /api/v2/contacts/change_status: as that is a much better description of what this API method can do. The remove method has been deprecated (i.e., kept in use for backward compatibility ONLY).


Older Release Notes