Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
With the way Workfront Planning is expanding, do you think there is a need for a separate topic specially for Workfront Planning within Workfront product community?
Are we able to populate the text used in the call to actions as a value in the URLs for tracking?{CTA Text} is "Schedule a Tour", having the url populate in "schedule_a_tour" for the UTM_Content=so it would be utm_content=schedule_a_tour
Hi everyone,I’m facing an issue with Adobe GenStudio and would appreciate some guidance.I have Admin access, and we have completed the setup steps mentioned in Adobe’s documentation.However, when I go to the Brands section, I’m unable to click the Create Brand button. Instead, I see the following message:“No brands to use — yet. An administrator is currently completing setup. Brands will appear here when available.”I have already checked the available settings and permissions, but the Create Brand option is still not enabled.Could anyone please confirm:Is there any additional setup required before creating a Brand? Does the user need a specific role or permission apart from Admin access? Is any backend provisioning required from Adobe?Any help or suggestions would be appreciated.Thanks!
I’m preparing for an interview and would love to speak with someone who uses Adobe GenStudio for end-to-end program setup and workflow optimization, from planning and content creation through approvals, activation, and reporting.Would anyone be open to a 20–30 minute call to share how you’re using it in practice? I’d really appreciate it.Please feel free to email me: jasminekokphuikuan@gmail.com Thank you!
Hi everyone,We are currently exploring Adobe GenStudio integrations and would like to learn from others who have already implemented them.Could you please share:What best practices should we follow when setting up GenStudio integrations? What challenges or issues have you faced during implementation? Are there any common permissions, configuration, or integration-related issues we should be aware of? Are there any specific recommendations for a smooth integration and setup?Any real-world experience, tips, or lessons learned would be greatly appreciated.Thanks!
Use this thread to ask any questions related to the Experience League LIVE session titled, Coworker Unlocked - Audience & Journey B2C capabilities in Coworker. Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!
Hello! Anyone have recommendations for Fusion training for someone who has zero technical experience? Any resources, YouTube channels, or guides that you recommend? For context, I taught myself the basics of Fusion out of necessity and it was very ugly.We may be looking to add to our team in the near future and I would like something more in-depth or more use case/providing examples of when you would use what functionality, etc. Thanks!KP
One of the interesting aspects of integrating Adobe Workfront with AEM as a Cloud Service using the native connector is designing the right metadata model and synchronization strategy.For the implementation, I used Workfront Custom Forms to capture business-specific metadata that is not available through the standard Workfront fields.Workfront allows custom forms to be attached to different objects, including Projects and Documents. This provides a flexible way to maintain metadata at different levels of the content hierarchy.Project Custom Form → AEM Folder MetadataThe first custom form is attached to the Workfront Project.The Project represents the business context and folder structure for the content. The custom form captures metadata that needs to be associated with the corresponding folder in AEM.For example: Brand Business Unit Region Market Campaign Language Content Category Folder DescriptionThe metadata captured at the Project level can then be mapped to the appropriate AEM fo
With Internal Lookup fields replacing Typeahead fields in Workfront, I would like to suggest an improvement to how dropdown options are displayed within reports.Previously, Typeahead fields allowed users to easily view the full name or description of each dropdown option without requiring excessively wide report columns.Currently, Internal Lookup fields display dropdown options within a limited width, making longer names or descriptions difficult to read. Increasing the column width to accommodate this information takes up valuable space and negatively impacts the overall report layout.Proposed Enhancement:Allow Internal Lookup field dropdown menus to automatically expand beyond the report column width, similar to how Workfront's native fields (such as User fields) currently function.This would allow users to view the complete names or descriptions of dropdown options without having to widen report columns.Benefit:This enhancement would improve readability, usability, and reporting eff
When people think about online learning, the quality of the educational content is only one part of the overall experience. The way information is presented, how easily users can find what they need, and how well a platform works across different devices can also influence whether learners continue using it.This is particularly relevant for families, where parents may be managing learning for children while also dealing with school schedules, work, and other responsibilities. A straightforward digital experience can make it easier for parents and children to understand available learning resources and follow a regular routine.For example, online Quran education can involve different types of content, including reading materials, audio resources, lesson information, practice activities, and communication between learners and teachers. When families research services or resources related to Learning Quraan UK, the user experience can be just as important as the educational material itsel
Hosted in partnership with the Adobe Workfront Product Management team, this 1-hour webinar highlighted the latest Workfront Planning, Workflow, and Automation & Integration feature enhancements that are scheduled to roll out in the Fourth Quarter Release on October 15, 2026. Note that users on the fast release (monthly) schedule will receive the release one day early (October 14, 2026). For more information on the fast release process, see Enable or disable the fast release process. IMPORTANT: This webinar did not cover all feature enhancements, so please make sure to read through the full release notes to ensure you and your team are fully prepared for what’s to come: Workfront Workflow Fourth Quarter 2026 Release notes Workfront Planning Fourth Quarter 2026 Release notes Workfront Fusion Release activity If you weren’t able to attend live or want to revisit any part of the session, you can access the recording below. Slide Deck PDF Event Recording – apologies the first ~2 m
Hi Team,I'm relatively new to Orchestrated Campaigns and am trying to develop a deeper understanding of a few concepts that seem closely related but are not fully explained in the documentation:Grain Target Dimension Reconciliation Enrichment Change DimensionI've reviewed the available documentation, but most examples are fairly basic. I'm hoping to get a more conceptual explanation, ideally with sample data and before/after results.My Current UnderstandingGrainMy interpretation is that grain refers to the level of detail of the dataset, or simply:"What does a single row represent?"Examples:Customer table → 1 row = 1 Customer Order table → 1 row = 1 Order Claim table → 1 row = 1 ClaimTarget DimensionMy understanding is that the Target Dimension represents the schema/entity that the workflow population currently belongs to.Examples:Customer Order ClaimExample ScenarioCustomerCustomerID C1 C2 OrdersOrderID CustomerID O1 C1 O2 C1 O3 C1 O4 C2 This is a standard Customer →
DescriptionCurrently, Adobe Analytics 1.4 API provides several powerful endpoints that allow administrators to manage report suite configurations programmatically. These include the ability to:Fetch and update eVars, props, events, and classifications.Retrieve configured processing rules for a given report suite.Adobe has announced that the 1.4 API will be deprecated in favor of the 2.0 API next year. However, these configuration-level features are not yet available in the 2.0 API. Once 1.4 is removed, these critical capabilities will be lost.For many enterprise-scale implementations, this functionality is not just convenient — it is essential. Proposed ideaExtend Adobe Analytics 2.0 API to include endpoints for:Variable Management: Create, update, and fetch eVars, props, events, and classifications at the report suite level.Processing Rules: Fetch and (if possible) update processing rules for a given report suite.Cross-Suite Comparison: Provide efficient ways to compare variable
I’m building a journey where the decision criteria are based on whether users clicked or did not click on communications, both for email and push notifications. I tried using the Reaction Event, but it doesn’t behave the way I expected. What would be the best approach to implement these decision points in the journey? Should I create an audience for users who clicked and another one for those who didn’t? Could you please help me understand the best way to set this up? Im using the AJO.
I have a site URL as https://mycompany.com/en-us/office/printers/func-print/cap-color/paper-ltr/vol-2501-10000/speed-36-50-ppm/brand-c-series/feat-airprintI want the dispatcher to do a PT and send it to publisher using selectors as https://mycompany.com/en-us/office/printers.func-print.cap-color.paper-ltr.vol-2501-10000.speed-36-50-ppm.brand-c-series.feat-airprint.htmlSince the number of selectors are dynamic (currently max of 7) and can even increase over time, how should I handle the rewrite rule dynamically N times?Below are all valid URL’s for my site which I need to be formatted with selectors:https://mycompany.com/en-us/office/printers/func-printhttps://mycompany.com/en-us/office/printers/func-print/cap-colorhttps://mycompany.com/en-us/office/printers/func-print/cap-color/paper-ltrhttps://mycompany.com/en-us/office/printers/func-print/cap-color/paper-ltr/vol-2501-10000https://mycompany.com/en-us/office/printers/func-print/cap-color/paper-ltr/vol-2501-10000/speed-36-50-ppmhttps://
OverviewWe’ve added a new field to the HTTP modules: Additional Retry Status Codes. This lets you list extra HTTP response codes that should be treated as retryable connection errors when Evaluate all states as errors (except 2xx and 3xx) is enabled. Previously Fusion retried only the built‑in retryable statuses (408, 429 and all 5xx). Now you can extend retry behavior to other status codes (for example, 422 or 404) when your integration needs it.What’s newAdditional Retry Status Codes — a free‑form field on the HTTP Make request module where you can add numeric HTTP status codes (comma or space separated) that should be treated as retryable. When Evaluate all states as errors (except 2xx and 3xx) is enabled, any code listed here is reclassified as a retryable connection error and will be retried according to the module’s Retry Count. Default retryable statuses (408, 429, and all 5xx) remain unchanged and continue to be retried even if this field is empty.How it worksEnable Evaluate a
The August 2026 AEM as a Cloud Service release (2026.8.0) had a lot for Assets teams. Several of the more interesting items are Beta or Limited Availability, so each one below carries its status.Listed under main release sections (no Beta or LA label on the page)1. C2PA metadata on renditions (Assets, and Dynamic Media with OpenAPI and Scene7). Renditions now carry C2PA metadata based on the original asset. It records the asset's origin, edit history, and whether generative AI was used. Two JCR properties are added: dam:hasC2PAManifest and dam:isAiGenerated. Adobe says customers should validate regulatory compliance themselves, and advises against relying on the manual Gen AI label where C2PA is available. If you publish AI-generated imagery, this is worth testing now. It isn't a compliance guarantee.2. Assets Insights moves to the Analytics 2.0 API (action required). Assets Insights now uses the Adobe Analytics 2.0 API with OAuth Server-to-Server authentication. You must reconfigure
OverviewWe’ve added service‑account authentication options to the Jira Software connector in Fusion. You can now create Jira connections using a service account API token or service account OAuth 2. These options let teams build reliable, machine‑level integrations that aren’t tied to an individual user account.What’s newService account — API token: Authenticate the Jira connector with a service account identity using an API token. Service account — OAuth 2: Authenticate via OAuth 2 using a registered OAuth client tied to a Jira service account. Both connection types appear alongside existing user‑based connection options in the Jira connector dialog.Why this mattersStability — Service accounts reduce disruptions caused by employee changes or credential expirations. Auditability — Activities generated by connector operations are scoped to a dedicated service identity, making logging and compliance easier. Enterprise fit — Supports machine‑to‑machine integration patterns and centralized
Hi,We have a Marketo Engage AWS migration scheduled for October 16 and are preparing for the migration.Could you please clarify the required actions around IP allowlisting?The migration guide says to “review and update IP allowlists for login, API access, email sending, web tracking, and integrations.” Which of these updates need to be made within Marketo/Adobe, and which need to be handled by our company IT/Network/Security team? The guide also says to “add new IP addresses and keep your current IPs as-is.” Should the three new AWS IPs for our data center be added only to our corporate/network allowlists, or are there any specific locations in Marketo Admin/Adobe Admin Console where we need to add them? Is there a pre-migration validation/checklist that Adobe recommends to confirm that our IP allowlisting and integrations are ready before October 16? After the migration, are there any post-migration validation steps we should perform to verify API access, web tracking, email delivery,
Description:The Upcoming Campaigns panel in Marketo Sales Insights (shown in the Salesforce contact view) lists scheduled email campaigns for the next 30 days. It also says these are "not limited to qualified leads."Problem:Our Marketo instance supports multiple businesses and brands. Sales reps see campaigns from other businesses in the panel and assume the contact is about to receive those emails. This causes confusion and unnecessary escalations. Reps think the contact is being mis-messaged, when in fact the contact doesn't qualify for those campaigns.Requested enhancement:Add an admin setting or user toggle, such as "Show only campaigns this lead qualifies for", that filters Upcoming Campaigns to campaigns whose smart list and filters the lead actually meets. If full qualification evaluation isn't feasible, allow admins to filter the panel by workspace, program channel, or tag, so each business sees only its own campaigns.
Convert the programs page into a widget that can be added to WF Home. This would allow convenience of accessing that page without leaving Home and allow project managers to quickly search for programs they need to access
Hey all! Just wanted to share a blog post by our amazing PM on how to write effective prompts for the teams edition of Coworker. Since this version of Coworker takes all the legwork out of creating a campaign, the better your prompt, the better your first draft of the campaign will be. Check it out: From prompt to polished journey in Adobe CX Enterprise Coworker for teams.
I have noticed this ‘module’ section that is now accessible where you can select components to drag into the email you can also select prebuilt modules. I can’t find any documentation about this or if it’s possible to customise and add our own pre-built modules instead of creating fragments. Does anyone know if this is possible?
Our team has a need to make the filter selection in the My Approvals widget sticky. We have multiple team members that submit work to others for approval and receive work from others for approval. Having to reset the filter each time to show only “My Approvals” instead of “All” wastes a few clicks of time and makes it more difficult for us to work through time-sensitive approvals.
We would like to thank the 650 customers who registered for this event.The objective of this webinar was to provide a "sneak preview" and a look under the hood to discover what our engineering and product team are working on.You will find here the recording of our last webinar organized on September 26th 2026: Adobe Target Engineering Webinar #6Slides are available as an attachment to this post.The Q&A file for this event will be available in the next days.The agenda of the webinar was the following:Coworker +Target Flags Bayesian Statistical Calculation for A/B tests : already available for customers! CJA reporting for auto allocate Popularity Based Recommendations grouped by Profile AttributeFor customers interested in Flags and/or Coworker, you are welcome to fill the following form Form AT engineering webinar #6
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
