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

New Features of Dynamic Chat [launched in Feb 2023]

  We are excited to announce some important updates released to Dynamic Chat this month that we think you’ll find useful.   Roles and Permissions  Now manage access to your Dynamic Chat users with new roles and permissions functionality. Now you can create your own product profile and add different combinations of permissions to manage access to users.   Also from now on we can create the following 3 default product profiles with respective permissions: - Marketing Admin - Marketing user- Calendar Agent   Globalization of static content Most of you already know that you can create dialogues for non-English visitors, but we heard feedback from you that this serves the majority of the need but there is system-specific content that still shows up only in English.  we have implemented a language selection feature at the dialogue level and system-specific text will be automatically translated into the respective language for a  visitor.         Search in Stream Designer Managing long dialogue streams can be a challenging task. To make this process more streamlined, we have added a new search function that allows users to easily search for any text within a dialogue, and make quick edits as needed. Furthermore, our search feature is also designed to support keyboard shortcuts, such as search commands 'cmd+f' or 'ctrl+f'. With this enhanced functionality, users can more efficiently manage their dialogue streams and optimize their workflow.       Auto-populating Inferred data  Leads generated through the chatbot will be automatically synced with your Marketo Engage instance in near-real-time. In addition, inferred visitor data based on their IP will now be auto-populated into the appropriate inferred attributes, allowing for more efficient and accurate lead capture.     Goto any card from the Dialogue preview  Are you enjoying using Dialogue Preview? We are excited to share that the experience has been further enhanced. As you preview your dialogue, you can now easily identify and correct any errors by clicking on the corresponding icon within the response field. This new feature allows you to seamlessly navigate to the relevant card on your canvas, streamlining the editing process and improving overall efficiency.  

Marketo Engage New Experience: Snippet List View and Landing Page Template List View

The Design Studio Assets delivered in the New Experience as a part of Jan 2023 release are:   Snippet List View:   From Jan 2023 release, Marketo Customers would be able to get a glimpse of Marketo’s next generation experience for Snippet list view. Marketers will be able to discover Snippet list view with a brand new experience to enhance usability through uncluttered view as well as perform bulk actions on multiple snippet assets. A toggle switch placed at the bottom of the screen will help with the transition from old experience to the new experience and vice-versa in order to avoid losing context and help retain the changes. Users will be able to obtain a comprehensive view of all the snippets, perform quick actions and use filters to shortlist relevant snippets based on name, status and archival state.     Landing Page Template List View:   From Jan 2023 release, Marketo Customers would be able to get a glimpse of Marketo’s next generation experience for Landing page template list view. Marketers will be able to discover Landing page template list view with a brand new experience to enhance usability through uncluttered view as well as perform bulk actions on multiple Landing page template assets. A toggle switch placed at the bottom of the screen will help with the transition from old experience to the new experience and vice-versa in order to avoid losing context and help retain the changes. Users will be able to obtain a comprehensive view of all the Landing page templates, perform quick actions and use filters to shortlist relevant Landing page template based on name, status and archival state.     To the marketing practitioners out there, we hope this new Marketo Engage experience makes every day go faster and every goal feel closer. This is just one of the ways we’re investing in your success with the next generation of marketing automation software. In case you have any feedback for us, please feel free to reach out to me at ndalvi@adobe.com

The New ON24 Webinar Integration

REVISED ARTICLE (6/17/2024) What’s changed? The good, the bad, and the ugly do differently. UPDATES:  This article has been updated with some new and revised information. Documentation links have been updated to new ON24 docs Background: ON24 has changed their integration with Marketo, and the native LaunchPoint integration is no longer an option for new accounts.  (Existing accounts can continue to use the legacy integration.)  The new method of integration is API calls, with custom objects. [In a conversation with the ON24 team, I learned that the new integration was the result of several drivers.  Customers wanted more data to be available in Marketo from the ON24 event.  The Launchpoint integration was convenient, but it greatly limited the data sharing. Custom objects, while not perfect, offered the ability to share more datapoints which are mentioned later in this article. They also mentioned that an integration kickoff call is available to clients, if needed.] This fundamentally changes the way you set-up the integration and associated programs.  You no longer bind the program to the event.  Event registrations are passed from ON24 to Marketo and each event is represented by a separate custom object record.  There are some things I like about it and some things that I don’t, but you can make up your own mind. Pitfalls ON24 has revised their document, which have been referenced in the article below.  For your convenience, here are some quick links: Setup instructions: When Using ON24 Registration Setup instructions: When Using Marketo Registration - Option 1 Setup instructions: When Using Marketo Registration - Option 2 There is a bit of a learning curve on how to design your programs, but there are some set-up details that can cause headaches and hair-loss.  (This article may help reduce both.) The integration is documented in the Marketo ON24 Connect Data Integration, but not everything is obvious.  Especially if you like to start with a Marketo registration form, then pass the registrant to ON24. How to avoid some basic problems. Options – at the end of the document, there are “options” that are very important. “Create New People” needs to be enabled if you ever want to use the ON24 registration page and have the new leads added to Marketo.  If not, you will only see registrations for “known” in persons in Marketo. “ON24 Registrants” needs to be set to sync registration activity to Marketo.  This includes registrations and participation data. “Backfill in Marketo” is your safety net if you found that you missed the above settings and have active programs running. ON24 Attendee[i] – is the name of the custom object (or whatever name you choose to give it) is where all the magic happens. Marketo programs must use the data in the custom object to add program members, change status, etc. This means that you need triggers for future activities and batch campaigns for data that has already been passed to Marketo.NOTE: You only need to create one custom object for your Marketo Engage instance, even if you have more than one ON24 account or add another account in the future. The Webhook –The 36-page instructions linked above make no mention of a webhook or how you pass a Marketo registration to ON24. Webhook information can be found in the Marketo to ON24 – Webinars article. (insert ethereal Aha! sound here) If you follow the instructions in both of these articles and don’t skip any sections, you should be OK. Avoid Old Habits The old ways of doing things are gone. Reset your brain. You don’t use the native LaunchPoint integration. You don’t pick the event partner or event in the program settings. You don’t build smart campaigns that trigger on program membership or status changes. You cannot use the {{member.webinar url}} token. (It will be NULL.) The New Way The new integration will require a little more set-up, but you can build most of this into a program template for easy replication.  I recommend creating the template with all of the Smart Campaign variations then you only need to configure/activate the ones that are needed for your event.  Before we get into the details, this diagram may help visualize the integration activities associated with the event. ON24-Marketo Program Flow Not every path in this flow may apply to your set-up, but these are considerations you may want to include in your program template design.  Some key things to note: The custom object record is only created by ON24 when a person is added to the event in the ON24 environment Registrations that originate in Marketo are only added to the ON24 event by the webhook Last minute registrations via the webhook from Marketo can be delayed if the systems are busy and these activities are queued.  (This can impact when the user join link is functional.) Registrations that originate in ON24 will be known to ON24 before they are shared with Marketo ON24 will only create a custom object for existing records in Marketo unless you configured ON24 to “Create New People” You can register people during the event.  The custom object will be created and updated. All registration activities, notifications, status changes, and follow-up actions must evaluate the custom object existence and field values. Reading the Tea Leaves (Custom Object) The key to all actions and controls is in the custom object.  There are several fields within it that are important to understand and use in your smart campaign build.  While there are many more fields that can be configured, these are the ones that are key to program membership and status.  Also, note that these field names are set-up when you create the custom object and may not have been added by your system administrator. Custom Object Field Value Required/Suggested Use eventid integer The presence of a custom object with the ON24 event ID indicates that the person is registered for that event. This is the key to identifying the custom object and associated fields below. [required] attendedlive Boolean Use this Y/N value to identify if a user attended the live event. You can use this to change the program status to "Attended". attendedarchive Boolean Use this Y/N value to identify if a user viewed the on-demand event. You can use this to change the program status to "Attended - OnDemand". cumulativeliveminutes integer Use the number of minutes value to identify how long the person participated in the live event. You may want to use a minimum threshold value to qualify a person for the smart campaign that changes the program status or issues program incentives. cumulativearchiveminutes integer Use the number of minutes value to identify how much of the recorded content the user viewed. You may want to use a minimum threshold value to qualify a person for the smart campaign that changes the program status or issues program incentives. Member Join Link & Event Tokens Since the join link is no longer added to the program, you cannot use the {{member.Webinar URL}} token.  Instead, you need to create the link with a combination of tokens. You will need to create a token for the event ID e.g. {{my.eventid}} and the event key e.g. {{my.key}} which you can get from the “Audience” link in ON24. You can find it by clicking the link at the top of the event which will open a box as shown below.  See the highlighted text for an example.  (Of course your values will be different.)     Once you have created the tokens, you will use them to “build” a join link with as follows with the tokens in bold for visual clarity: https://event.on24.com/wcc/r/{{my.eventid}}/{{my.key}}?mode=login&email={{lead.email address}} Create New Habits The new way requires a focus on the custom object records and changes to those records. At a minimum you will need the ON24 Event ID to identify relevant data for the program. Create a local token for the event ID   e.g. {{my.eventid}} Create a toke for the event key   e.g. {{my.key}} Remember that an event custom object is added only once, after that you will need to trigger on updates to the ON24 Attendeei custom object. Sometime triggers don't happen. (It's a fallen world.) This can occur if your instance is very busy and the trigger campaign is waiting for an extended period of time, and the campaign times-out without executing.  (If you happen to be monitoring the campaign, you can bump the priority of the waiting campaign in the Campaign Queue of the workspace.) It is more likely that you have other things to do and you didn't see the campaign waiting in the queue. All is not lost, you can create a smart campaign that uses the custom object filter with the same settings as the trigger, and run it as a batch process. Power Tip:  You may just want to create this as a safety net, and schedule it to run every day during the event period. This will sweep any missed activity into the program. You don't need to recreate everything, add a "Campaign is Requested" trigger to the main smart campaign and request it in the flow of the sweeping batch campaign. You must build the member join link with multiple tokens. Create a test event and program to gain some experience … then Test. Test. Test.   There is much more to learn and understand, which will come with practice.  Hopefully this article will get you off to a good start and avoid some frustrations and mistakes.     [i] ON24 Attendee is the suggested name for the custom object.  You can use something different but note that this is how this article refers to the custom object. I also recommend creating all of the fields, because you may need them some day and it will reduce the need for troubleshooting in the future.

New Features of Dynamic Chat [launched in December 2022]

  We are excited to announce some important updates released to Dynamic Chat this month that we think you’ll find useful.   Chat Transcript  As you may already know, all lead engagement with the chatbot is captured as an activity against the lead in Marketo Engage. Now you can see how the conversation went with the chatbot transcript. A new attribute "Chat Transcript" is added "Engaged with Dialogue" activity type which captures the URL of the conversation transcript.   Once you open the URL, you can see the conversation between the person and the chatbot.   You can view the conversations either in the chatbot window or in plain text format, along with dialogue and time details on the right.   Support Integer and float field types Now you can sync and capture Integer and float data type fields into Dynamic Chat from Marketo. In the map-to-response option, you can see the data types along with the field names. You can use these attributes to capture information like company revenue or employee size etc.   Updates to target URL logic  We have made the following updates to target URL in audience criteria tab of a dialogue: 1. Now target URL will support URL formats without the HTTP or HTTPS protocol  2. When you enter *.yourdomain.com it will not only consider all subdomain i.e https://blog.yourdomain.com , https://support.yourdomain.com but also work for both naked domains and domain with www prefix i.e https://yourdomain.com and https://www.yourdomain.com    

[Release Update | Campaign Classic V7] Release 7.3.2 - Build 9356_November 2022

Release 7.3.2 - Build 9356 November 21, 2022   Find the detailed release information here: Latest Release   Compatibility updates Adobe Campaign is now compatible with PostgreSQL 14. Following the end of life of Microsoft Internet Explorer 11, the HTML rendering engine for dashboards in the client console is now using Edge Chromium. Improvements The Google BigQuery connector now fully supports boolean fields. You can now configure the IMS cookies validity duration in the Configuration for the redirection service section of the serverConf.xml file. This applies to the following cookies: uuid230, nllastdelid and AMCV_  The IP can now be hidden in the “/r/test” request by setting showSourceIP to false in the redirection node of the serverConf.xml file.  Deprecated features Social Marketing with Facebook is now deprecated. You can use Twitter integration to post on social media, or work with Adobe to create a custom channel. ACS Connector (Prime offering) is now deprecated. You can use Campaign export/import capabilities to extract and inject data in both products.   Check out the details about the compatibility updates, improvements, deprecated features, other changes and patches in this latest Campaign Classic V7 Release here: Release 7.3.2 - Build 9356   Feel free to reach out for questions and feedback through the below comment section.

New Features of Dynamic Chat [launched in November 2022]

  We are excited to announce some important updates released to Dynamic Chat this month that we think you’ll find useful.   Support boolean field types Now you can sync and capture boolean data type fields into Dynamic Chat from Marketo. In the map-to-response option, you can see the data types along with the field names. When you select a boolean field type, you will see responses Yes or No are auto-populated and the same will be shown to the visitor through the chatbot.     Submit button for info capture card Customer feedback we received - "When entering data in the chatbot as an end user, it’s not clear you need to press “enter” to submit". Makes sense right? So we added submit button to info capture card   Dialogue used by list As you might already know you can retarget or run operational campaigns based on visitor engagement with dialogues using the new set of Dynamic Chat triggers and filters in Adobe Marketo Engage. If you have any such campaign running and suddenly someone in the team deletes a dialogue, the campaign will never trigger again. This happens no more! Now when you try to delete a dialogue, you will be automatically shown all the Programs or Staticlists or Smartlists where current dialogue is being used. You can directly click on the links provided to update the campaigns before deleting the dialogue.   Changed default meeting buffer to 30 minutes We have changed the default buffer between the two meeting slots from 60 minutes to 30 minutes. This means you will now be able to get more meetings booked and also provide more slot options to your customers.   Skip asking for information that you already know I think nobody likes to give the same information again and again! If you also think so, this feature is for you. In the Stream designer, on the info capture card now you will see an option to either skip or overwrite the value provided by the visitor. By selecting the Skip option, the chatbot will check if you already have the respective lead information and automatically skips to the next card.     Disconnected nodes in a dialogue All disconnected cards and streams on the stream designer will be automatically highlighted. 😃   Hope you are enjoying using Dynamic Chat, if you have any feedback please write to us dynamicchat @ adobe .com