​@Lukas Hi there!

I worked with the Supermetrics Looker Studio product a few years ago, so someone on the Supermetrics team might be able to chime in with a little more intimate knowledge, but I remember running into a similar issue when it came to the ‘Results’ metric. When you hover over ‘Results’ in Meta’s platform, which might list ‘Multiple Conversions’, Meta will give you a breakdown of those conversions… I think this is similar to what you’re saying. Unfortunately this breakdown doesn’t translate over to anything in the API, so when we pull it into Looker Studio, we just get a flat number and can’t break it out by any field. 

When it comes to pulling product-specific data into Looker Studio from Meta’s API, there’s a ‘product_ID’ dimension available to the API, but I’m not positive if it will work with all queries to that data. For example, I can pull impressions by Age and Gender, but I can’t look at Age and Gender in combination with Country and DMA. While I can see impressions by Country and DMA, I might not be able to see 50% video plays or 100% video plays. The API is brutal, so test out ‘product_ID’ first (if it’s available), to see if conversions will breakdown further for you in the Action/Action Type reports.

My direct solution in the past (when there weren’t a ton of products to work with) was to come up with custom conversions for each product, that way when I loaded the data into Looker Studio, I could break out all of the custom conversions, and have the ‘overall conversions’ metric be my rollup. It’s a bit tedious, and doesn’t backfill your data, but might help solve this.

My indirect solution is to reconcile everything in GA4 with custom timestamp dimensions, and then work to attribute conversions every week side-by-side within hour-level windows of time. For example, if Meta logs 3 conversions between 8a-9a, and I see 3 conversions in GA4 between 8a-9a, I can have some level of confidence that the reporting matches. It’s a less ideal solution (since GA4 has its own attribution difficulties), but could alleviate the manual work involved in pulling in those extra custom conversions directly on Meta.

Hope this helps!

Hey ​@gcfmineo!

Thanks for your help and tips. It has definitely helped us to think outside the box and we have made a few adjustments - and I don't want to keep you in suspense for too long - we’ve found a solution. 
It was actually easier than we thought for our use cases, as in our case as a cinema group, we only had to search for the specific name of the respective META Custom Conversion as a field in the Dimensions area in Looker Studio and could ultimately display it.

Sometimes the solution is right in front of your eyes, but you think far too complicated.
Thanks anyway and have a great week!