@arpang16406580 Could you elaborate more about the Mobile App? is this customer facing app? Why would you need subset of data when you have access to Unified profile.
Also the datasets you describe would be enabled (some of them if not all) for "unified profile" which will stitch all relevant infor...
@SCB21 Ideally the AA to AEP connection should not affect this. The connection happens server side and does not really impact "data collection" where you are seeing increased volumes.
I would suggest checking your data to investigate what and where the events/hits are originating, highly suspect...
@Umberto as long as the dev's push the data into the array, the data should update the state, if this is visible i think they have done their job.
Everything from here is timing or typo in data element.
@JassonAlgo Could you elaborate bit more on how the libraries are structured? Are they all in one rule with multiple action? If yes this can be done using rule component sequencing
You also have an option of using "JS Promises" in custom code, if this helps your use case.
Hope that helps
@Umberto There could be few reasons ( to begin with) for this to happen.
The data required for data element was not ready ( i.e the datalayer push has not happened yet) when analytics tags are firedThe data element has incorrect code or configuration which prevents the data element to be set.
@MasterLeeman You can use the queryservice api to query the dataset and for desired data, but may really support the delta.
It will always get back the latest data at the time of query.
Hope that helps
@b_koth So there are couple of ways to do this
Include the consents and preference xdm fields: Like you mentioned this is probably best way to approach not only for server side tags but also will ensure the profile is enriched with latest consent status. use custom xdm field: instead of using the...