Product ideas | Community
Skip to main content

10000 Ideas

MichaelMa60New Participant

Adobe Alert Request - Ability to exclude alerts from firing for specific hours of the dayNew

Description:We need be able to identify irregularities/defects in our ecommerce business (declines in web traffic/sales/conversion).Using Alerts (both daily and hourly) with segments applied helps our teams triage in root cause analysis and investigations.Some of our hourly alerts trigger frequently if the criteria are met, most often during hours of the day where a large portion of our website/app visitors and purchasers are not browsing or purchasing. Why is this feature important to youWe are receiving specific hourly alerts for certain use cases more often then we would like.We have leadership and other stakeholders that have requested to receive these alerts, but we do not want to add them to the distribution until we can control the frequency to exclude these known instances from firing. We want to prevent the integrity of the Alerts tool from being deemed inaccurate and irrelevant as a result of this. How we would like the feature to workWe would like to have a dropdown filter to select specific hours of the day to exclude the hourly alert from triggering for. Alternatively, if we can apply apply a segment that excludes specific hours of the day from being included that would work.With current behavior of applying a segment using either of the criteria below still yields triggering an alert during the 3AM, 4AM or 5AM hours of the day.Logic Option 1: Exclude Hit where Hour of Day = 3AM OR 4AM OR 5AM Logic Option 2: Include Hit where Hour of Day = 12AM OR 1AM OR 2AM OR 6AM OR 7AM OR 8AM OR 9AM OR 10AM OR 11AM OR 12PM OR 1PM OR 2PM OR 3PM OR 4PM OR 5PM OR 6PM OR 7PM OR 8PM OR 9PM OR 10PM OR 11PM  

jlinhardt_blueAcornNew Participant

Update Designated Market Area (DMA) ID in Experience Event Field Group to String, from IntegerNew

Hi All.  I hope things are going well.  I had an idea I was hoping you could consider. It seems that the OOTB functionality of the AEP data processing from a Web SDK implementation includes converting the user's IP address into the Designated Marketing Area Identifier (DMA ID).  This identifier is part of the Web SDK Experience Event Field Group and again is provided by Adobe automatically, meaning this is NOT something we set or configure within the Web SDK itself (if you exclude "turning the feature on" within the Data stream and Web SDK extension). The values within this field look like numbers - for the US based visitors505, 506, 507, etc The problem with this field is it's data type.  It's set up as an "integer" field, not a text string For example, ID = 505 is actually the Detroit MI area.  but there is no 'DMA Name' field in AEP, just the DMA ID.  So running a report in AEP Query Services or CJA and getting a 505 number is not helpful to our analysts.  We need to translate the ID 505 into Detroit. The problem is since the field is set up as an integer we are not able to classify it.  We've tried setting up an AEP Lookup Table, but you can not set up a Relationship between two dataset when you're dealing with 'integer' fields, the keys that connect tables together must be 'string' values. We tried converting the DMA ID integer into a String using the Data Prep Mapping Services, but it seems the DMA ID doesn't yet exist or isn't accessible by the Data Prep tools so those efforts also failed. We tired using CJA Lookup capability within Derived Fields and we after 4 business days can't seem to get our DMA Dataset connected to our CJA Connection... the tool just won't process the dataset because we can't set the DMA ID field as an 'identity field' because it's an integer data type. So our idea is:- to have Adobe add the DMA Name field to the field group and then update the DMA processing to also populate the DMA Name field automatically without the need for us to 'classify' the DMA ID- if that's not possible, we'd like Adobe to update the Web SDK Experience Event Field Group so that the DMA ID field data type is a 'string' instead of an 'integer'. - If that is not possible without impacting already existing customer who are using that Field Group, then we ask that you expose the DMA ID field to the Data Prep services so we can manually create a rule that will convert the integer field into a string field. - If that's not possible due to the way AEP processes data, then we ask that Adobe provide a solution to calculate the DMA within the Web SDK Extension or Adobe Data Collection Data Element so we can set our own custom field in our Schema to collect the DMA ID as a string value (so we can classify it within AEP / CJA) I hope that all made sense 

Farzaneh
FarzanehNew Participant

Make it possible to track changes to the name and status of the projectsNew

Description - Tracking changes to the name and status of the projects that present what the changes was (old to new) and when it happened. Why is this feature important to you - Executives need reports on changes that happened to the project status, for example, how projects changed status during the past month, and from what status to what status. The purpose is to report changes that happened within the portfolio since last portfolio meeting: for example, how many projects went in progress, on hold, completed, etc., during the past 2-3 months.  How would you like the feature to work - I would like to be able to track changes to the name , status, and some other attributes of the projects that are captured in custom fields. Journal entry field allows some of the tracking but it is not for all and not intuitive. Also, journal entry fields cannot be accessed through custom forms if I try to create custom fields based on them. Current Behaviour - Journal entry field allows some of the tracking but it is not for all and not intuitive. Also, journal entry fields cannot be accessed through custom forms if I try to create custom fields based on them. Also, while changes of status from in progress to completion and from entry to in progress can be tracked and demonstrated by creating reports Entry Date and Completion Date, there is no way to track other statuses a project goes through its lifecycle.