Update as of Wednesday, August 29, 2018
Customer Attributes allows for customers to upload additional visitor information to the Experience Cloud, which is then made available in Adobe Target and Adobe Analytics.
Customer creates a “Data Source” within the Experience Cloud user interface (UI). The Customer is then able to upload visitor information from a third-party system to this data source via FTP (up to 4GB .csv files) or directly in the UI (up to 100MB .csv files). Within the Data Source, customers define which solutions will be able to consume this information. Currently Target and Analytics are the only options.
When visitors go to the website and identify themselves (typically by logging in), the Experience Cloud ID is tied to the CustomerID that was uploaded in the Customer Attribute data file. This is how the data is stitched to the Adobe solutions.
Update as of Friday, August 24, 2018
The backlog includes the files from the last two to three weeks. You can navigate to the Customer Attributes UI, and click on a data source. If you scroll down below the graph, you should the files that have been uploaded for the last 30 days. If you look at the status column, you will see “queued” or “failed”. You may also see previously "queued" files move to the "failed" status.
There are a few steps that need to happen to return back to full service with Customer Attributes:
A cross-functional team has been working on this around the clock to bring the processing back in line and ensure this does not happen again. These are the actions taking place:
Are only file uploads via FTP affected? Or are Customer Attributes uploaded via web interface also experiencing latency?
Regarding the delay of processing files, that is limited to FTP files only. However the schema mis-match issue was occurring with both FTP and UI uploaded files. Engineering just rolled out a release in the last day to resolve the schema mis-match issues.
I had problems 09/03, Do you know somenthing abou it?
Update to the two current issues:
We will keep you updated as more information is available. Thank you for your patience.
Thanks again for your patience.
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 needs happening? Is there further time to get that new value truly synched into other "production tables" so to speak? I'm seeing behavior in some that'd lead me to believe that - even though the ID Lookup shows an updated value, that doesn't mean that the final production source tables for adobe have that value replicated to it.
That's a good question. There is some time delay. What you illustrated is that you updated the value in the Customer Attributes system. From there, once the change is realized. It then pushes the changes to the relevant subscriptions (think solutions). It can take a few hours to push the data into Analytics and Target. Once that push happens then the solutions should see the change reflected (Reward Level Y) etc.
I hope that helps,
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 set of attributes).
Next question that might be dumb: We're referencing Client Attributes in a Target Audience. Is there anyway to surface/ confirm "what value did Target see in Client Attributes as it ran this test"? We're trying to confirm that a Target experience is wonky because the Client attribute must not yet be up to date with the most recently uploaded value (as seen in ID Lookup)