Product ideas | Community
Skip to main content

10000 Ideas

TylerKrause
TylerKrauseNew Participant

Trigger off Journey events via Query Service JobsNew

Description - Presently, Query Service jobs do not write to the DCCS (Data Collection Core Services) which results in these events being ineligible to be qualified for event qualification to kick off a journey. I would like to be able to use a Query Service job to kick off a qualifying event for Why is this feature important to you - This would allow us to kick off journeys from a more flexible point of view. We typically have relied on subscriptions to events from our IT partners that we digest via the HTTP API Source. Unfortunately, development of these events is heavily dev intensive and can often take months. We had a use case for a reminder email for a customers order to send 2 days before their quoted pickup time. We frequently see updated date/time for our order pickups, so we need to use contextual data from other events to qualify the send. We were able to right the logic very eloquently in query servives, but we were not able to actually excecute using it, because of the inability to qualify the event via DCCS, even though it looks good on the profile.How would you like the feature to work - I would love a toggle in the dataset level to indicate whether or not I would like the data to be digested via DCCS. Current Behaviour - Event data that is generated via query service jobs are ineligible for event qualification. We're able to write the data to profile, so there shouldn't be an inflation in usage, but we would be able to better utilize the data that we're digesting from our various partners to drive customer facing results.

amariamorarEmployee

Easy to delete or alter custom formsNew

On a recent Ultimate Success call I mentioned that I was concerned about the ease with which it is possible to delete or alter custom forms.  This came of the back of Case Number 00425051 - Accidental deletion of custom form - undelete request, where I had accidentally deleted one of our teams custom forms.  When custom forms are deleted we are required to contact support to get them undeleted, which seems like a step that could be avoided.  As a result I would like to suggest one of the following:          Confirm deletion pop up         Ability to undelete from the system admin settings menu         Custom forms having a ‘lock’ that requires and extra step to unlock I believe any of the above would have prevented me from deleting the custom form.  In another incident recently a staff member with Admin access altered a custom form with an additional data requirement, which then resulted in all existing copies of that form no longer displaying data until the new data requirement had been met.  This makes sense but it not immediately obvious, it would also be beneficial we had a way of saving custom forms so that experimentation can be done, although maybe its best that I ask changes are first made to the form in the preview environment to check compatibility.  Finally, If a field is deleted from within a custom form it seems all historical data collected by that field is lost, it would be good to have a way of reverting changes etc if needed to avoid data loss.

ddirrenNew Participant

Use Geo-Location Lookup and IP Obfuscation from the Datastream (WebSDK) in Adobe AnalyticsNew

Description:In our use case, we utilize the WebSDK and the Datastream for data collection. In addition to AEP, we also use Target, Analytics, and Event Forwarding as services. Our goal is to use IP obfuscation [full] and identical GEO lookup data across all services. Why is this feature important to you:For security and data governance reasons, it is important to us to configure these settings only once and not have to configure them additionally for each service. How would you like the feature to work:General settings and additional data determined in the datastream (IP obfuscation, geo lookup data) are extended in the payload/XDM, and all services use this data if available. The configurations that rely on previous integrations from AppMeasurement.js only apply if this data is not already present in the payload. Current Behaviour:Currently, and according to Adobe Support, we need to set the IP obfuscation in the datastream from "Full" to "Partial" so that the IP address reaches Adobe Analytics and another geo lookup can be performed. The geo lookup in the datastream and in the WebSDK configuration cannot be used to make geo information (country, state, city) available in the Analytics Workspace for analysis.This leads to the need to search for settings in the other services to ensure that no IP information or similar data is stored.