Skip to main content

Filter by idea status

10000+ Ideas

Welcome email for new Marketing Cloud users needs to indicate login/usename and ID typeNew

When I create a new Marketing Cloud user in the Admin console (for Analytics or Target, for example), the welcome email they received doesn't indicate what their username/login is, needed for when they try to log in and if they are logging into from a browser other than that the welcome email link resolves to, and needed for password resets. Also, the email doesn't indicate what kind of ID type they have: Adobe ID or Enterprise ID. My organization currently uses both for Adobe products (Marketing Cloud and Creative Cloud, respectively). Currently, I have to set solution permissions as a separate step in the user creation process, but I also have additional work when creating a user because I have to trouble-shoot with the user after they receive the "Welcome email" to resolve why they could log in initially with no password (yes, clicking on the welcome email link brings them directly into the solution with no password and logging in), but have been unable to log in subsequently, create a password or reset a password. If creating custom welcome emails was an option, as it is/was in Analytics, that would suffice. But the current "welcome" experience is confusing for the end-user and cumbersome for the admin, requiring much more work and time to resolve than the former process. Screenshot attached, no indication of username/login or ID type (required for login). Further, during the "Password Recovery" process, which was required because the user couldn't log in except from the welcome email, the Password Recovery email showed a "username" inconsistent with any user name I had entered, created or provided for this user. I have no idea where this name came from, except that it might have simply been a concatenation of the first and last name. Still, it was not the user name I created. And the email refers to SiteCatalyst, which hasn't been the product name for years! Screenshot attached.

cjpberry
cjpberryLevel 2

Atomic units of time, date, timezone, day surfaced in Processing RulesNew

Adobe captures a session timestamp. That timestamp, at present, is not surfaceable in processing rules. Understandable becauuse processing rules do not have regex or parsing capabilities. However, the atoms of that session timestamp, and associated metadata, are very valuable to a researcher. These include: "As a researcher, I want to cross the HH:MM with a video name so that I can calculate an AMA.""As a researcher, I want to cross the day of the week with a pagename so that I can compare Monday traffic patterns to Sunday traffic patterns in aggregate.""As a researcher, I want to cross HH:MM with timezone with a video so that I can understand how timeparting and timezones affects AMA." If specific components of the timestamp could be surfaced in processing rules, multiple timeparting features could be enabled. (The implementor would assign that data to specific variables to taste). A concrete example: a.hour  : expected value 00, 01, 02, 03 ... 22, 23a.minute: expected value 00...59a.second: expected value 00...59a.twentyfourhourtime: expected value 0000....2359a.dayofweek: expected value monday, tuesday, wednesday, thursday, friday, saturday, sundaya.weekdayorweekend: expected value weekday, weekenda.timezoneoffsetgmt: expected value -12.....0.....+16a.timezoneoffsetutc: expected value -12.....0....+16 IF such technical debt is undesirable, the most straight forward three features: 1. Enable read-only priveledges to the session timestamp.2. Enable read-only priveledges to the timezone.3. Enable regex in processing rules.