Please use the following template when requesting a new feature or enhancement by email to email@example.com. Alternatively, you can create an Idea in this community, but try to include the same details. Field (*required) Input *Summary <One-liner> *Business Priority P1=Can’t use/ adopt without it, P2=Highly desirable, P3=Nice to have, but can live without *Feature Name (Event Cap or Event Goals) *Request Details <Describe what you would like to see that is missing today, with as much detail as possible> *Business Justification/ Use Case <Why do you want this addition or modification to existing functionality? How would your business benefit?> *Who Needs This <Which roles/ personas/ job titles in your organization would benefit from this?> Screenshot(s) Attached? (Yes or No) <Don't forget to attach!>
Email to firstname.lastname@example.org and attach any screenshots. You can upload screenshots or other relevant documents to this community and link to them. You can also initiate a discussion to find out if others have faced the same issue. Field (*required) Input *Summary <One-liner> *Severity P1=System down, P2=Feature unusable, P3=Workaround available *Feature Testing Event Cap or Event Goal *Page/ Screen Title or Navigation Path Instance Name <Munchkin ID> *Browser and Version *O/S *Steps to Reproduce <As numbered list; include error messages and as much detail as possible> Why you believe it is a bug? <Versus an enhancement request> Screenshot(s) Attached? (Yes or No) Yes or No
Hello Beta User, Your feedback is crucial to helping us provide the highest quality experience to our customers. We recommend capturing all issues as you go along. For bugs, complete and submit the bug template For feature requests, create ideas in this community or submit the feature request template For all other questions, suggestions, and comments, email email@example.com Your contacts in Adobe Product Management, Badsah Mukherji (primary) and Niranjan Kumbi (secondary), will both receive your communications. You are also welcome to take advantage of the features of this closed community for knowledge exchange and communications with Adobe and other beta customers. Additional information about being a beta user we would like you to know: Be sure to check out the Helpful Links on the landing page of this community to familiarize yourself with the functionality. Ask your admin to check the event and webinar channel configurations and make changes, if needed. Under helpful links, you'll find a link to an explanation of the new Waitlisted status in the event and webinar channels/ tags. Incorporate the features into your day-to-day job, applying them to real-life scenarios rather than simulations. If you are enabling the features in a sandbox environment, replicate what you do in production. We encourage you to identify areas where you would like to see embedded help or suggest ways in which we can make onboarding of new users easier. (Think about where you and others in your organization typically go for help.) Thank you. The Marketo Engage Product Team
Adobe's Marketo Engage is preparing for a release that will make managing events and webinars easier. To help ensure we're providing the highest quality release possible, we ask that you test-drive the beta features and share your feedback. The beta features help the marketer with three key tasks: Setting goals for registrations and attendees as part of planning an event or webinar (additional goal: on-demand attendees) Setting registration limits for an event or webinar Automatically placing overflow registrants on a waitlist Highlights of the beta program: The beta involves two features: Event Cap (Set event registration caps, page redirects, and waitlists – see Helpful Links for details) Event Goals (Set event registration and attendance goals and track actual progress – see Helpful Links for details) Prerequisites for participation in the beta program: Have a signed beta agreement on file (request this from your Customer Success Manager) You must be licensed for the Events and Webinars add-on (also helps to have some event data in your system) Marketo Sky: If you are not using Sky today and don’t plan to right away, then consider a hybrid model for the beta. In other words, have beta users use Sky for programs of “Event” and “Event with Webinar” type, and use classic UI for everything else. These features are only available in Sky. There is no cost to you. At the end of the beta, we will turn off the features unless you decide to subscribe to the GA product. Pricing and packaging for the GA product is to be determined. If you have a need to make these features available to specific users, you can require beta users to use Sky for events and webinars while non-beta users continue using the classic UI, where the new features are not available. If all users are already on Sky and you still need to isolate the features to certain users, please contact us so that Engineering can work with you to figure out a solution. Note: Predictive Audiences (that is, AI predictions and predictive filters) will come later. The beta for that will not require a new beta agreement, so you are welcome to participate when the time comes. We will announce its availability when it is ready.