As far as I know t parameter is a legacy one and really never used for processing. Don't know what it is used for.   For report suite that are timestamp disabled or timestamp optional(without manual timestamp), adobe will generate the timestamp when the hit is received server side.   For report suit...

Original article   Feature Flags or Feature Toggle is a common practice used by developers. It allows to deploy specific functionalities in an incremental manner and only enable them when needed. In the tagging world feature flags is a little-known concept. Most of the time a standard tagging releas...

I think the segment is not build correctly at all. Could you elaborate of what exactly you want to build?  By looking at how the segment if structured it does not make sense. In your own terms explain what is a "new buyer" and we might be able to help you.

For enabled I think it was removed as the API to return the dimensions only return the enabled dimensions. I think it is the same for metrics.

Perfect, could you accept reply as solution please.

Would be ideal if you could provide more details like which report you are running. Based on the title check this https://experienceleague.adobe.com/docs/mobile-services/ios/sdk-reference-ios/app-ids.html?lang=en  I believe App id is only sent if lifecycle metrics have been enabled, so please check ...

Please use the column hit_source and it should tell you how the data has been generated. Also if you are using Activity map please be aware that data is sent not to your report suite I believe but a generic one at adobe side, it is then stitched into your report suite so it could be that.

In terms of code it would be quite heavy. I would advise you to explore other product that use heat map functionality.  I believe some products already do that out of the box lke ContentSquare: https://contentsquare.com/platform/zone-based-heatmaps/  

For the HIT all of the rules needs to be TRUE in the HIT itself. So only visits where ALL the rules are met in SAME HIT will be picked up. For the VISIT all the rules needs to be TRUE during the VISIT lifetime so one or more HIT can contain one or more rule to be TRUE.  i.e : RULE  1 evar1 = 123AND ...