if the guardrails are mentioned as hard limit, then the platform will not allow to exceed that guardrail. if not, platform will continue to accept but there will be delay in processing or/and there will be performance degradation. but if we exceed the guardrails in extremely high volume then there w...

if you want to avoid creating two profiles, you can consider to mark phoneno (given in laptop login) as identity, and while signing up you need to get the phoneno and mark it as an identity as well, then you can stitch them into a single profile. in your example, in the first login (from laptop) if ...

failed batches cannot be retrieved using query. As per the previous comment can be done using API. --ssj

try with MM instead of mm. "MM" represents Month, "mm" represents minutes.format(date(ava_subscribedate),"yyyy-MM-dd") --ssj

Yes. It remains constant after creation. As an alternate you can create a new dataset as "Test2" with the same schema. --ssj

you can query (using query service) the profile snapshot dataset with the filter condition in email attribute and get the identity, which you can then use to lookup the profile. --ssj

In general, only profile attributes can be exported to destination, and not the timeseries attributes. In case of profile, its a record type schema, and attribute will be overwritten, whereas in case of event attributes, there is chance of "n" number of records with different values for an attribute...