I have assumed that this means, you can upload a data file to a cross-device data source BEFORE an individual ID has been used in any browser, and then when an individual ID is seen in a browser (in an authenticated state) - the data will be available for targeting (cookie based destination).
As opposed to a NON profile-link/cross device data source, where Audience Manager must have received at least 1 ID sync/hit for an individual ID BEFORE a bacth file is uploaded so that any targeting will be available (cookie based destination).
However I cannot get this to work.
I have uploaded multiple files with NEW IDs to a cross-device data source - yet it is only those IDs which have ALREADY been seen in a browser (BEFORE the file upload) which ever have data returned for targeting (cookie based destination).
The ones which have never been seen in a browser yet - never resolve to any segments for the data which was uploaded.
We have server side forwarding enabled and I am using the setCustomerIds functions as requested for Profile Merge functionality.
Is there something special needing to be done to enable this functionality to work as described?
I am sure till now you must have figured out the solution for your query but I just wanted to share my opinion on this case.
I believe the scenario you defined is perfectly fine. Working as designed. Reason for that is:
When you upload a data file to a cross-device data source BEFORE an individual ID has been used in any browser, and then when an individual ID is seen in a browser (in an authenticated state) - the data will be available for targeting (cookie based destination). - Perfectly Fine.
But when you upload a data file with NEW IDs to a cross-device data source and those ones never been seen in a browser yet, so in this case an user profile got created in the edge server and user profile got processed into keystone/ backend server. It takes approx. 24 hours for the new user profile to get full profile created in edge server to return segments.
Same goes with the Inactive users across all customers. After 14-days of user inactivity across all customers, Audience Manager deletes user data from our edge servers. If Audience Manager records user activity in within this 14-day cycle, we will keep this data for another 14-days. If the user becomes active again after the 14-day period, there will be a delay between that first new page view and when the user becomes actionable. It takes 6-18 hours to get the full profile back out to the edge center after more than 14-days of inactivity.