Is there a seamless way to get email notifications when changes are made in Adobe Target?  We'd like to have more of our team making changes, but it would be nice for us to get automatically notified of these changes.  

I'd like to try updating user's profile attributes as way to use them in experience targeting  (hide/show different content if they've seen it in the past x-amount of days).  It seems there's always a undetermined delay.  I've tried using the Profile API directly and the trackEvent() function. I'm u...

As we test with visitor's and updating their profile parameters, it would be nice to manually toggle the values the profile parameters have.  Is there some sort of admin screen to do this?

Are there any examples of using Adobe Target for "New Feature Walkthroughs"?  Ideally this would be a user logging into a site which integrates with Target.  The site just released a new feature, and we want to introduce that customer to the new feature.  If the user dismisses it, or logs in again, ...

We are setting up some simple experiences controlled by Adobe Target.  However some of it we want to only show once to each customer (for example, there is a new feature available and we want to highlight it to the customer, but only once).  What is the recommended approach to achieving this?

Whenever I create an Activity, it defaults to Inactive. These are using Experience Targeting and Json Offers.  Once I create it, I start receiving the inactive activity instantly before I activate it.  This seems to only occur in one of the workspaces that we have setup for testing only.  Is there s...

Is there a recommended approach to having Profile Scripts change but only effect a dev environment vs production?  Currently it seems like you can't allocate a profile script to a specific environment, so once it is edited, it will immediately effect production.

We have a react SPA.  First page that the user goes to, it seems the "adobe" object is available, but target.getJsonOffer() is not there yet.  Eventually it is there and we can execute it but not unless we do some sort of timeout functionality or force the SPA to re-render.  Is there some sort of me...

We are noticing that a lot of our users seem to hit a "network request failed" when bringing the at.js file into a React web application: This is a screenshot of the error we are detecting.  What is the typical cause of this?  Can it be security settings on the browser?  Is there a workaround?