Product Updates | Community
Skip to main content
  • 311 Product updates

[Release Update] Adobe Journey Optimizer 2021 Releases

Hi Everyone, This post highlights all the Journey Optimizer product releases that happened in 2021. For detailed update on New Capabilities, Improvements, and Fixes, check here: Release Notes November 2021 Release CNAME subdomain delegation: Adobe Journey Optimizer now supports CNAMEs. A CNAME, or Canonical Name record, is a record that points to another domain address rather than an IP address.  October 2021 Release Decision Management - Offer Simulations: You can now simulate which offers will be delivered to a test profile for a given placement in the Journey Optimizer UI. This allows you to validate your decisioning logic including eligibility constraints and ranking algorithms easily before you put them in production.  Decision Management - Personalize your offers: You can now personalize the content of your offers using Adobe Experience Platform profile attributes and segments, using the same expression editor component found throughout Journey Optimizer UI. September 2021 Release New Capabilities Reporting - Better insight to targeted audience: New metrics are available in reporting: Targeted and Excluded for email & push messages are visible in both live and global reports.  Pass lists of data dynamically using custom actions: You can now pass collections or a list of data in your custom action parameters that will be dynamically populated at runtime.  August 2021 Release New Capabilities Send messages at the best time - Send-Time Optimization: Automatically send your push or email at the best time for every customer you engage with Adobe Journey Optimizer. Send-Time Optimization, powered by Adobe’s AI services, predicts the best time to send an email or push message to maximize engagement based on historical open and click rates out of the box. Leverage schema relationships in business events - Lookup table management: You can now leverage relationships between schemas when configuring a business events. Personalized URLs: Personalized URLs take recipients to specific pages of a website, or to a personalized microsite, depending on the profile attributes. Make sure your emails get to your users - Email Retry: You can now define the retry period on a per preset basis to ensure that retry attempts are not performed anymore when no longer needed. Define addresses to exclude from sending - Suppression list: Adding email addresses and domains into the suppression list is now available from the user interface, either one by one, either in bulk mode through a CSV file upload. July 2021 Release New Capabilities Use metadata in your messages - Lookup table management: Enrich your experiences with reference data you've loaded into Journey Optimizer. Allowed list: You can now define a define a specific sending-safe list at the sandbox level, to have a safe environment for testing purpose.   Find the detailed release information here: Latest Release

Apple iOS 15 Privacy Announcement: How Marketo Engage Could be Affected (UPDATED October 8, 2021)

Apple recently announced new features in their upcoming iOS and macOS releases which are designed to protect data from third parties. A broad set of FAQs on the potential impact can be found on Adobe Experience League. We have provided an additional set of Marketo Engage-specific FAQs below. Since the new features have not yet been released by Apple, much of the information below is speculative. We plan to post updates as we learn more, so please stay tuned.  UPDATE: iOS 15 is now generally available on both iPhone and iPad.  We have conducted tests using iPhones running iOS 15 with Mail Privacy Protection enabled.  Please see updates to this FAQ below (in red).    Will this impact email open-tracking in Marketo Engage?  Highly likely. Early reports suggest that the open-tracking pixel contained in Marketo emails may be obscured and downloaded as a background process, irrespective of how you interact with the email. It is possible that an email open could occur without opening the email, which could artificially inflate the number of email opens. Also, the timing of when an email open activity is generated could be impacted since it may be decoupled from the actual open.  UPDATE: Yes, we confirmed that unopened emails can trigger an email open activity.   Test Methodology We used a batch campaign to send a test email to 5 testers with Mail Privacy Protection enabled on their iPhones.  We instructed each tester to not open the email and then waited 1 week before checking results.  Create a static list of test leads Create a batch campaign to send an email to members of static list Run campaign once Wait for 7 days and inspect campaign results   Observations After the 7 day wait, we found that 3 of the 5 unopened emails had open email activities logged in Marketo.  These activities were “machine-generated” due to a background load of the open-tracking pixel that occurs when Mail Privacy Protection is enabled.  For the 3 machine-generated opens, we found that 1 occurred within minutes of delivery, and the other 2 occurred several hours after delivery.    We then had testers go ahead and open the delivered emails.  For the 2 emails that did not machine-generate an open,  we found 2 email open activities were logged as usual.  For 3 emails that did machine-generate opens, no additional open activities were observed as expected.  This is because Marketo only ever records a single email open activity for any given campaign/mailing/lead combination.   We ran same test with Mail Privacy Protection disabled and did not observe any machine-generated opens.   To summarize: When Mail Privacy Protection is enabled, some delivered emails will have machine-generated opens, and the timing of when machine-opens occur is unpredictable. When Mail Privacy Protection is disabled, no machine-generated opens occur. Will this impact email link click tracking in Marketo Engage?  It is unlikely that tracked links will be impacted.  UPDATE: No, we confirmed that click email activities are logged as expected.  No change here.   Which product areas within Marketo Engage might be affected?  While there is no immediate impact right now, here is a quick look at the potential areas of impact within Marketo Engage.   Assuming that email opens may not be accurately trackable in the native Mail app, and that a user’s IP address will be altered by the native Email app and the Safari browser, we have identified the following areas of potential impact.  Activities It is hard to predict what the impact will be on the “Open Email” activity. For example, if the open-tracking pixel request is generated even though the email is not actually opened, then email opens could be overcounted. Also, the time of the open-tracking pixel request could differ from the time of the actual email open. Finally, there are activities that contain a “Client IP Address” attribute which may not be as accurate as before (Visit Web Page, Fill Out Form, Click Link, Unsubscribe Email).  UPDATE: There is no way to identify which open email activities are machine-generated, and which are not.  Machine-generated opens will likely increase the overall number of opens, but by how much is hard to know.   The User Agent on iOS15 has changed to simply “Mozilla/5.0”.  Since some activities contain metadata that is derived from User Agent, some of this metadata has changed (Platform, Device, User Agent, Is Mobile Device).   Open Email Activity - Before iOS15 Open Email Activity - After iOS15   This could impact your smart lists should they leverage these attributes as constraints.   Here is an idea that could help provide insight into iOS15 adoption.    First, build a smart list that looks for leads that have opened email using an earlier version of iOS. Since at the time of writing, iOS15 is only available on iPhone/iPad, we limit results to those devices only. Click on the People tab and record the number of list members (in lower righthand corner). Next, add another filter to smart list for leads that have opened email using iOS15. Since at the time of writing, iOS15 user agent is "Mozilla/5.0", we limit results to that browser only.  This provides the list of leads that have opened email using a prior version of iOS and using iOS15 in past 30 days.  Click on the People tab again and record the number of list members. You can then compare the two results and gain insight into iOS15 adoption.     Here are some of our test results over the past 30, 60, and 90 days. Date of Activity (in Past) 30 Days 60 Days 90 Days Device iPhone/iPad 23,723 38,901 52,964 Device iPhone/iPad & Browser Mozilla/5.0 1,160 2,621 3,444 iOS 15 Adoption Rate 4.9% 6.7% 6.5%   From this list, you can inspect the lead activity history and identify when a lead switched over to iOS15. Your mileage may vary!   Reporting Email opens can be inferred through email link clicks without the open-tracking pixel being activated, but reporting may be impacted. The “Opened”, “% Opened”, and “Clicked to Opened Ratio” columns in Email Performance Report columns may contain less accurate data. Also, any open-related measures or fields in Revenue Cycle Analytics Email Analysis Report may contain less accurate data.   UPDATE: There is no way to identify which open email activities are machine-generated, and which are not.  Machine-generated opens will likely increase the overall number of opens, but by how much is hard to know.   A/B Testing If you use Opens as Winner Criteria, then test results may be impacted since this criteria relies on accurate email open tracking.  UPDATE: See Reporting (above).   Web Personalization The “Location” and “Industry” firmographic Web Segments may not match as they had before. This is because the segment attributes are derived by doing a lookup using the client IP address.  UPDATE: See Inferred Fields (below).   Inferred Fields Since client IP address may not be as accurate, Inferred Fields may be impacted. Send In Recipient Time Zone can use inferred fields to calculate time zone (as a fallback when known location fields are not populated). Lead to Account Matching can also use inferred company name field in matching logic. UPDATE: The client IP address behavior on iOS15 has changed.  To allow users to hide their IP addresses from websites and network service providers, requests now go through an Apple proxy server. The proxy server assigns an IP address from a pool of users grouped by their approximate location.  As a result, the location information stored in Marketo inferred fields will be less precise.  Best practices for using inferred data can be found here.   As a Marketo Engage user, what can I do now to prepare for this change?  Review your usage of product areas described above and assess potential impact. Reduce dependency on email open rates. Look for activities from the click onward to measure engagement. Think about how you measure success of your email campaigns and how email opens fit into your overall methodology. Gather device and OS data to understand potential impact. This can be done using either Email Insights or Smart Lists as described here.  UPDATE: Reduce dependency on email open rates.   As a Marketo Engage user, what should I be thinking about in the future?  Email opens are not the most important indicator for measuring success of your email campaigns. Email is the vehicle by which you drive your customers to a landing page to convert via filling out a form or other action. Web page visits, link clicks, and form fills are the high value activities that you should concentrate on.    Geographic and firmographic data based on client IP address lookup is not entirely accurate since many IP addresses return data for the Internet Service Provider instead of the actual user. In some cases, an IP address lookup will return no data at all. An alternative could be to use a third-party data enrichment service.    Privacy changes are transforming email as we know it. Changes to proxies, location data, and blocked email opens present new challenges to email measurement. Here are Deliverability resources that may prove useful to address those challenges:  Optimizing Marketo Engage Email Deliverability  Email Deliverability 101: 4 Tips to Inbox Success 

Adobe Audience Manager Release notes | August 2020

Get the latest information on Audience Manager's new features and fixes. Also, do let us know in the comments below - How are you utilizing these features for your success? Do you have any feedback related to these features? List of features in August - You can now use People-Based Destinations to target users via Google Customer Match. Before you can use People-Based Destinations to send your first-party audience segments to a Google Customer Match destination, it is mandatory that Google adds you to their allow list. Check the People-Based Destinations documentation for details. (PLAT-53962) Predictive Audiences now supports the selection of a Profile Merge Rule per model, during model creation. (AAM-55178) Destination mapping start and end dates are now visible in each segment's page. (AAM-40056) Fixed an issue where the Device Type of a trait was automatically set to Cross-Device when creating a new trait. (AAM-55368) Fixed an issue where the Audience Marketplace would fail to load. (AAM-55549) You can now un-map segments from Google destinations when the Google UserList parameter is not retrievable. (AAM-42655) Fixed an issue where adding multiple segments to a destination would not always work correctly. (AAM-55651) Fixed an issue where users who had their Profile Merge Rules limit increased would not see the Add New Rule button. (AAM-55700) Fixed an issue where the 30 Day Overlapped Unique Users title would go missing from the Data Feed Report Metrics. (AAM-55801) Lifetime metrics are now excluded from the Destination view when the destination is configured to export UUIDs. (AAM-54196) Fixed an issue where users would not be able to view Tableau reports. (AAM-55868) Fixed an issue where users would receive an error when creating a new Predictive Audiences model. (AAM-55921) Multiple accessibility improvements across the interface. (AAM-49062, AAM-49063, AAM-49365).