Cost related Tagging for EMR Serverless

Hi team, I need some clarification on whether cost tracking is supported at the per-job level with EMR Serverless? For example, with regular EMR, costs are tracked at the cluster level, tagged by cluster id (aws:elasticmapreduce:job-flow-id). With Serverless, is the costs associated for each job submitted by application id or some other job identifier ( I am asking from cost granularity by tagging prospective)