Skip to main content

Filter by idea status

10000+ Ideas

Andrew_Wathen_
Andrew_Wathen_New Participant

Rapid re-purposing of dimensions: Alternative to deleting data?New

IssueDeleting data is incredibly problematic (and expensive!) in Adobe analytics. One of the impacts is on our agility - we have several dimensions that are tied up as they contain historic data that is no longer relevant and we are waiting for that data to disappear through the standard data retention deletion process before we reuse - This is something we really struggle with. RequirementsThe requirement is to be able to quickly re-purpose variables/dimensions, thus increasing the flexibility/agility of the Adobe Analytics tool. For this scenario the requirement is to prevent end users seeing the historical data (rather than deleting the data).  Therefore I was wondering if there was an alternative approach which would allow us to free up dimensions quickly for new purposes.   Possible solution?The problem with deleting data seems to be unpicking all the processing that has happened.  My thinking is this unpicking could be avoided by having virtual variables (much like a "virtual track" on a digital multi-track recorder) Each prop/eVar would have say 3 "virtual" versions.  The admin console would allow admins to switch between which virtual version of a prop/eVar is in use. This would mean only one virtual version of a prop/eVar would be available at one time to record new data into and retrieve data from. At a time when the original purpose for a prop or eVar is no longer relevant the admin could simply cut across to a new/fresh version of the prop/eVar - allowing immediate re-purposing. This would be different to deleting data as all virtual versions would continue to exist in the background but only one available at any one time (i.e. no data is actually deleted) From a storage/infrastructure perspective it should also be different to just giving us loads more props/eVars as only one virtual variable could be recording new data at any one time (so storage requirement should be less)  NOTE: this sort of already exists for eVars in the way that switching between different attribution types (linear/first touch/last touch) cuts across to a different instance/version of the eVar

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.