Skip to main content

Ideas

Filter by idea status

10000+ Ideas

markTwoLevel 2

Front or back loading planned hoursNew

Description - It would be ideal if you were to specify, at project template level, that planned hours can be front or rear loaded (in addition to being spread evenly across the task duration) when assigned to a user. Why is this feature important to you - This would help our project managers to schedule resource more accurately, it will allow them to schedule tasks on the same day, get get the most for the available resource on a granular level. The assignees would also benefit, they can concentrate on one task at a time, moving onto the next once the fist has finished. How would you like the feature to work - If a task has a two day duration and 8 planned hours and is assigned to a user who has a capacity of 7 hours per day, WF would allocate 7 hours in day 1 and 1 hour in day two. The task would be set to start at 9am and finish at 5pm which is inline with our default schedule. If the assignee has 2 hours available on day 1 and 7 available in day 2, the task would be spread accordingly, 2 and 6 hours. If an assignee has less than the required amount of capacity across the 2 day duration, an error message should be displayed when trying to assign the task or they are not available to assign when selecting. (similar to the plane icon when they are on leave during the task duration.  If the assignee has a different schedule, eg they start at 11am, the task will schedule to start at that time rather than 9am, the same would be done if the assignee has a task finishing at 3pm on day 1. Current Behaviour - Currently the above is a manually process and has to be adjusted on each task as WF distributes the planned hours evenly across the duration days. 

bjoern-koth
Adobe Employee
bjoern-kothAdobe Employee

Web SDK - Simplify and fix Cookie Consent HandlingNew

Description - the current Web SDK "set-consent" behaves a little unexpected in different situations, leading to unwanted results, whereas a the legacy Visitor ID service behaved differently.   Examples:   A) A new visitor denies cookies. With the Visitor ID service, you would've just denied the consent categories, mapped to the Adobe tools without having any whatsoever cookie written. With the Web SDK however, if you send a general "opt out" through the "set-consent" action, two things happen "kndctr" cookies are set (!) if the company has a RT-CDP license, a pseudonymous profile is created (correct me if am wrong!) with the consent preferences attached to it   In my opinion, none of the two above make sense, and cookies written lead to potential legal problems.   Now, I am a seasoned Launch developer and have a workaround that involves local storage and some other constructs to make sure the "set-consent" rule only triggers (and writes cookies and creates a profile), when it is needed.   I am wondering what happened to the super simple approach with the old Adobe optIn API.   Why is this feature important to you - ease of use, legal compliance and cost control. If I don't consent, why does the Edge network return cookies. And when I am a new visitor without consent, why create a profile?   How would you like the feature to work - Web SDK should send a set-consent call if a user previously consented and changed his settings e.g., now opts out. a user gives consent to be tracked ("collect")   Web SDK should NOT send a set-consent call if the user has never consented and rejected all consent categories, resp. the "collect" category   Current Behaviour - opt out with cookies stored on client side and needed workaround in place to disable Adobe tools and functionalities that were automatically handled through the Visitor ID Service in the past.

vimsr1
vimsr1Level 1

First Touch Campaign: What It Is and How can it Benefit your Business?New

First Touch Campaign: What It Is and How It Benefits Your Business A First Touch Campaign is a marketing strategy designed to create the initial interaction between a brand and a potential customer. In analytics terms, it represents the first marketing touchpoint that introduces users to a brand, product, or service.These campaigns are commonly executed through channels such as Google Ads, paid social, display ads, or organic discovery, and they play a critical role in first‑touch attribution analysis within platforms like Adobe Analytics and Customer Journey Analytics (CJA).The primary objectives of a First Touch Campaign are to:Build brand awareness Reach new or unknown users Create a positive first impression Initiate long‑term customer relationshipsBelow are examples of how First Touch Campaigns differ by industry.📈 eCommerce Industry – First Touch CampaignIn the eCommerce industry, urgency is often a key factor in the success of First Touch Campaigns. Consumers typically make faster purchase decisions, so timely and compelling offers work well.Example: A potential customer clicks on a paid search or display ad and lands on the retailer’s website. As part of the first interaction, the user is shown:A first‑purchase discount Free shipping A limited‑time site‑wide offerEcommerce Industry — First Touch CampaignFrom an analytics perspective, this campaign is often tracked as the first attribution touch that introduces the customer to the brand. A strong first impression helps increase engagement, conversion likelihood, and repeat visits.👷 B2B (Software Product Companies) – First Touch CampaignIn B2B software companies, the urgency of a First Touch Campaign depends on:Product complexity Market competition Business goalsThe sales cycle is usually longer, but the first interaction is still critical in moving users into the consideration stage.Example: A software company promoting a project management tool may use a First Touch Campaign offering:A free trial for a limited time Early access to premium features Event‑based promo codes for webinars or conferencesFrom an Adobe Analytics point of view, these campaigns help identify:Which channels introduce high‑quality leads How first‑touch interactions influence downstream funnel stages🤝 B2B (Service Providers, Manufacturers, Distributors)In traditional B2B service‑oriented industries—such as manufacturing, supply chain management, wholesalers, or distributors—the sales cycle is longer and often involves multiple stakeholders.Here, the goal of a First Touch Campaign is less about urgency and more about:Building trust Establishing credibility Educating potential clientsExample: Instead of discounts, the first interaction may focus on:Case studies Whitepapers Introductory consultationsIn analytics reporting, First Touch Campaigns in this space are valuable for understanding brand discovery, top‑of‑funnel engagement, and long‑term contribution across multi‑touch journeys.