FTP also is needed in our case because we have a system that cannot accept the published emails out of the workspace area. So our users cannot share artifacts through the 'share/ send file' functionality of the tool. FTP would give us a needed option of getting info out of the Adobe walls and to us....Why? combination of a limitation of our system and the limitations of Workspace publish options.Outbound email from Adobe’s Adobe Analytics Workspace publishing process arrive to us as completely H...

Got it. Extremely helpful. I've always assumed immediate update of downstream solutions once Customer Attributes said "complete"...and we've always experienced very quick practical 'realization' of attribute updates in Production experiences... except for this past week. Is there a chance that's related to this 'backlog/synch' event? If so then it'd be pertinent to update the impact statements as I'm not using FTP (just the browser drag/drop function for fairly small csv files with a very small ...

Question for Users of Client attributes from someone who is suspecting synching issues:- I Upload new attributes file- status goes from loading, publishing, to complete- This update changed client attribute "Reward Level" from "X" (as established in a prior file upload) to a new value of "Y" for a particular customer ID- I use the "ID Lookup" and it, as hoped, shows the Reward Level of "Y"Does that mean everything is complete? or is there further synching down the line of adobe architecture that...