Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Trade desk integration enhancements that connect paid to own.Adobe and The Trade Desk are helping brands bridge the gap between paid media and owned customer experiences by bringing advertising exposure data back into Real-Time CDP. By connecting paid media engagement signals with customer profiles, organizations can gain a more complete understanding of customer behavior and use those insights to improve audience segmentation, personalization, and future marketing efforts.Why It MattersToo often, paid media insights remain isolated within advertising platforms. By turning media exposure data into actionable first-party intelligence, brands can create richer customer profiles, improve customer experiences across owned channels, and make future campaigns more effective. This connected approach helps organizations move beyond campaign reporting to continuous audience learning and optimization.Learn MoreSee how Adobe and The Trade Desk are helping brands connect paid media performance wit
In your experience, what are the main reasons a Marketo lead scoring model fails to deliver expected results?
As a light/contributor/standard user (Reviewer and/or Approver), I want to be able to tag in a comment another user who is not in the workflow. This person should then be able to comment the proof but not make any decision
Adobe Express connector now available in Workfront FusionWe’ve added a new Adobe Express connector so you can automate common Express workflows—like listing tagged documents, creating variations, exporting renditions, and checking operation status—directly from Workfront Fusion integrations and automations.OverviewThe Adobe Express connector exposes the primary Express API surface so you can programmatically interact with Express documents and tagged elements from your Fusion scenarios. The connector maps the Express API endpoints into modules that make it easy to include Express operations in integration flows, automation canvases, and scheduled jobs.Connector capabilities (API endpoints)Tagged documents — List all documents that contain tagged elements so you can discover assets to process. Tagged document details — Retrieve metadata and the tagged-element structure for a specific document to inspect editable regions and element IDs. Generate variation — Create new document variatio
本日、メール配信をしたが配信保留のままメールの受信が確認できませんでした。色々とテストしたのですが、ZOOMと連携してイベント設定をし、ZOOMウェビナーの情報を受け取ってトークンで埋め込んでいるメールがどうやら保留になってしまうのかと思っています。一度調査いただけますでしょうか。
At present the brand theme for the new email templates is local to each workspace. Are there plans soon to make the brand theme it’s own component so it can be shared to select workspaces or an entire instance? If so is there a timeframe?We are keen to adopt the new email builder soon but don’t want to have to set up and manage 10+ versions given we have lots of workspaces.
We were hoping to utilise Marketo’s new picklist functionality so we can better control our data however we have identified some issues using picklist fields on forms. When editing forms users can still add or remove values from a field (with a managed picklist) however when the form is approved those additions or omissions are removed and all values that exist in the picklist are displayed to people viewing the form. Any changes to the values in the form obviously get removed when the form is saved. This seems a little counterintuitive to me because the form editor is allowed to make changes, but those changes are effectively ignored if they don't exist (or aren't complete) in the managed picklist. For example we have set a picklist on a field for persona, if we have a lead capture form in use at an event we may want to remove some of the persona options based on the event audience, with the current functionality we cannot do this. While the point of the picklist is to protect your d
We currently have 3 report suites in Analytics which we have set up the Analytics Data Connector to pull those into AEP so they can be used in CJA. 2 of the 3 report suites have migrated from legacy Launch to SDK and are now being captured in our AEP SDK dataset. I am thinking to remove the 2 ADC datasets from CJA and replace them with the AEP SDK dataset but I’m conscious the AEP SDK dataset will be real-time and the ADC dataset will continue to be batch. What are the considerations we should be aware of when looking at reporting data that is partially real-time and partially batch?
Hi all,Recently we got a security requirement to add the “require-trusted-types “ directive in the csp with value “script’ to lock down DOM XSS injection sinks. However when I add this to the CSP header, it’s blocking couple of lines in the launch scripts. Now I understand that I have to add the trustedPolicy and create a trusted policy in the JS and add that policy-name in the “trusted-types” directive.But how do I add that in the launch scripts? Because from AEM, we are only adding script url, the scripts are not written in the aem code base. Looking for any inputs to implement this.Thanks,Dayana
We have a very simple setup, an email asset with one module containing dynamic content set up in the legacy email editor. We get the email content using https://{{endpoint}}/rest/asset/v1/email/{{id}}/content.json and it returns a body similar to this { "success": true, "errors": [], "requestId": "4202#19ee08c5295", "warnings": [], "result": [ { "htmlId": "foobar2026", "value": "RVMtZm9vYmFyMjAyNg==", "contentType": "DynamicContent", "isLocked": false } ]} However, if we attempt anything in the email DynamicContent whether it’s a GET or POST using either of these endpoints https://{{endpoint}}/rest/asset/v1/email/{{id}}/dynamicContent/{{htmlId}}.json where the htmlId is the one returned by the first email content endpoint, we get a no assets found response. { "success": true, "errors": [], "requestId": "e1d4#19ee08ffc81", "warnings": [ "No assets found for the given search criteria." ]} Can you help clarify
Currently in Realtime CDP, using tracked event data that is also evaluated in Adobe Analytics, it is not possible to segment profiles based on the number of visits (as metric “Visits” in Adobe Analytics) that they have since there is no “visit-id” that is exposed on the UI or even the possibility to select audiences based on “count unique” [element]. The number of visits in a given timeframe is an important KPI for our department and we would like to select profiles in different intervals of it.Thanks!
We are configuring a destination in Adobe Experience Platform using Destination SDK server configuration. We are able to create the connection and send profiles to the destination, but the payload is resolving to null values even though the source attributes are populated.We are using PEBBLE_V1 in the requestBody template and referencing nested profile attributes under personal_details, we are looking for guidance on whether there is any syntax issue in the template logic that could cause populated fields to resolve as null.structure:{ "templatingStrategy": "PEBBLE_V1", "value": "{\n \"items\": [\n {% for profile in input.profiles %}\n {\n \"firstname\": {% if profile.personal_details.first_name is empty %}null{% else %}\"{{ profile.personal_details.first_name }}\"{% endif %},\n \"lastname\": {% if profile.personal_details.last_name is empty %}null{% else %}\"{{ profile.personal_details.last_name }}\"{% endif %},\n \"emailaddress\": {% if profile.personal_detail
when we execute a query, is there a away to find if query used regular QS vs data distiller ?
Hello,how come in a segment comparison when I add a new dimension item or a new calculated metric, the difference score is not calculated. It shows n/a. Is there something I need to do to have it calculate? Thank you
Hi team, I was following the Adobe EDS implementation steps.I had forked the xwalk repo from last release version 0.2.0 In this paths.json has been deprecated and xwalk.json is introduced.This new release is not working for me.I have correctly setup the site using site-template from xwalk release page.And then configured AEM code sync as well for my repo.In my repo I have correctly setup the mount point as that of my dev author.fstab.yamlmountpoints: /: url: "https://{dev-author-domain}.adobeaemcloud.com//bin/franklin.delivery/pulkit-vashistha/aem-eds-demo/main" type: "markup" suffix: ".html"x-walk.json{ "public": { "xwalk": { "multi-field": { "enabled": true } } }}But when I publish the page from AEM author to preview or liveI have unable to view my page at https://main--<repo>--<owner>.aem.page/ or https://main--{repo}--{owner}.aem.live/It shows 404 page not found.When I click on update in AEM sidebar , I still see the original adobe x-w
Hi all,During Adobe Summit I saw a demo of the Journey Canvas in Adobe Analytics, and I noticed in the release notes that general availability was announced on June 5. However, I still don’t see the Journey Canvas available in my Adobe Analytics environment, even after checking regularly. I’m trying to understand whether this is expected or if something is missing on my side:Is the rollout still happening gradually?Do others already have access?Or does this feature need to be enabled somewhere (e.g. report suite settings, permissions, etc.)?If anyone has insights on availability, rollout timing, or required configuration, I’d really appreciate it.Regards,Arjanhttps://experienceleague.adobe.com/en/docs/analytics/release-notes/latesthttps://experienceleague.adobe.com/en/docs/analytics/analyze/analysis-workspace/visualizations/journey-canvas/journey-canvas
Hi Community,I am working with our team to implement a very simple trigger-based email that includes a single Velocity script token.The purpose of this email is to trigger a second email from Trust Pilot that grabs the data from the first email (sent by Marketo) and uses this to request an online review from the recipient.This VS token looks for the most recent cruise booking opportunity on a contact record, grabs the booking id from the opportunity, and populates it in the email. The email then gets sent to Trust Pilot’s Automatic Feedback Service (AFS) via a Send Alert smart campaign flow step.When I initially tested this using only my account, the token was populating just fine:And the email successfully created a record in Trust Pilot that included my email address and the booking ID number. Plus I received an email from TP asking for a review: However, when I tried to send the alert email via both a batch and trigger campaign, with multiple people qualifying (23 ppl), this resulte
Issue SummaryWe are using a common footer fragment across multiple email templates. The footer receives a variable (welcomeText) from the email template and renders it using triple braces ({{{welcomeText}}}).When the welcomeText variable contains HTML tags such as <br>, <sup>, <b>, or <p>, the email validates successfully.However, when the variable contains an HTML anchor tag (<a href="...">...</a>), the email validation fails with the following error:welcomeText of email variant is malformedSteps to Reproduce Define a variable in the email template: {% let welcomeText = "<a href='https://google.com'>Google</a>" %} Render the variable in the email template or a content fragment using: {{{welcomeText}}} Save or validate the email. Actual ResultThe email validation fails with the following error:welcomeText of email variant is malformedExpected ResultThe welcomeText variable should accept valid HTML anchor tags in the same way it accepts o
Is anyone else having issues with how comments/updates are loading in Workfront? We’ve been working with support since yesterday on comment/update display issues. At first comments weren’t loading, then we noticed some comments were missing from projects, but appearing on people’s profile pages.Support initially thought they had fixed it yesterday, but today we noticed that many older comments (1 year+ old) were not displaying in some cases.It seems this all might be related to this Q3 2026 update, Optimization of Comment Archiving’: https://experienceleague.adobe.com/en/docs/workfront/using/product-announcements/product-releases/release-26-q3/26-q3-other#optimization-of-comment-archiving Support are aware and working on fixing the issue, but I wanted to see if any other Workfront customers were running into the same issue. Let me know, thank you!
It would be very helpful to me as an admin to be able to prevent users from creating objects with the same name (IE multiple projects with the title “Project 1”). We have a lot of users who will duplicated projects or other objects and name them the same thing as their counterparts, which causes confusion among team members. We also have users who have accidentally duplicated objects without realizing it, then can’t determine which was the original.
Issue SummaryWe are using a common footer fragment across multiple email templates. The footer receives a variable (welcomeText) from the email template and renders it using triple braces ({{{welcomeText}}}).When the welcomeText variable contains HTML tags such as <br>, <sup>, <b>, or <p>, the email validates successfully.However, when the variable contains an HTML anchor tag (<a href="...">...</a>), the email validation fails with the following error:welcomeText of email variant is malformed Steps to ReproduceDefine a variable in the email template:{% let welcomeText = "<a href='https://google.com'>Google</a>" %}Render the variable in the email template or a content fragment using:{{{welcomeText}}}Save or validate the email.Actual ResultThe email validation fails with the following error:welcomeText of email variant is malformed
As an online shopping enthusiast, I'm always looking for ways to save money, and Revounts Australia has been incredibly helpful. It offers best discount codes and deals as well as seasonal discounts for 2,000+ Australian and international brands. Whether you're shopping for everyday essentials or premium products, Revounts Australia makes it easier to find great deals and maximize your savings.
Is there a way in Fusion to generate a report of all scenarios that have turned off/errored out in the past week or so?
What should be the payload if the data is non XDM? I use Data Prep … Its not explained and I got the errors :(https://developer.adobe.com/experience-platform-apis/references/streaming-ingestion#operation/sendMessage
RTCP keeps only last profile fragment (XDM Individual Profile). How that looks like when it comes to Data Lake?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.