Anything linked to profile won't be available via /customResourcesThough standard objects won't be available via both APIs if extended, even if linked to a profile

Unfortunately you can't do a simple "search delivery" filter in dynamic reportingIf they are all under the same campaign, opening the reporting on the campaign context may help?

Unfortunately no.For Transactional Messages, the system has a pre-configured monthly aggregation which cannot be adjusted.

@shelly-goel: what did you choose under the identification tab?

Can you provide some sample screenshots / HTML code?Is it any specific mail client where the display is wrong or all?

If you want to do it to have the segment code available on the delivery logs, there is no need to use the dynamic segmentation code feature.Easier might be to use an Enrichment. Then just in Additional Data add an attribute and as field name use @segmentCode.This will process the value in the same w...

It is not stored in the system. You would have to calculate it using the delivery + Tracking logs. (using rownumber function and deduplication activity)

Domain level reporting is also only available in aggregated form inside reporting.But you could also calculate that inside a workflow but only during the retention period before the logs are cleaned up

The marketing history API unfortunately only would return the label of the communication sent but not the subject. There is currently no API to fetch the subject

Querying the broadlog table would be the right way to go.Half an hour indeed seems very long.Can you maybe post a screenshot of the query you are using?