@KeironWratt AJO's recent release of the Execute Metadata helper function allows users to attach custom key-value pairs to the Profile Message Feedback Event Dataset. This enriches standard events (send, open, click, bounce) with runtime-specific data beyond profile attributes. Note that the Execute...

@trojanHorse12 You can't do anything; those are URL-encoded values that ensure that URLs remain valid and can be correctly interpreted by web browsers and servers.

@Pradeep-Jaiswal The current landing page functionality has limitations. However, a recent release introduces forms within the landing page feature (Limited availability). These forms offer a variety of field types and greater flexibility in mapping different attributes. More details on using landin...

@Vrushali_K This likely stems from nuances in handling right-to-left formatting. Please open a ticket with Adobe Support regarding this issue.

@ShushmitPa Yes, you can set up an audience to target customers who have received communication from a specific journey or campaign, and a query service is not required for this. For example, you can create an audience of customers who have successfully delivered a message from a journey in the last...

@HardikJa3 While a Condition activity can technically handle all the functionalities, the Optimize activity simplifies experimentation setup for marketers by combining the features of both experimentation and condition activities. This makes it easier for marketers to set up experiments using the Op...

@HardikJa3 When using daily frequency capping, the cap resets at 00:00:00 UTC each day, as the cap is valid until 23:59:59 UTC. From documentation, https://experienceleague.adobe.com/en/docs/journey-optimizer/using/conflict-prioritization/capping-rules/channel-capping "Daily - The daily frequency ca...

@RakeshK1I've noticed an intermittent issue where the copy and paste journey node(s) fail. Reloading the page each time, allowing the copy and paste of journey nodes to work correctly afterward. I'm also looking forward to the release of the journey fragments feature to address these kinds of issues...

@An1 You have already seen this. The throttling configuration is restricted by a guardrail that prevents the use of more than one external endpoint or configuration per organisation. An enhancement request can be submitted through an Adobe support ticket if this functionality is needed. https://expe...

@Silvio6 It's a guardrail that you can't use timeseries data like feedback status and campaignversionID in journey conditions. It has to be a batch audience. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/events-journeys/experience-event-schema https://experie...