{"id":34076,"date":"2023-01-28T19:20:08","date_gmt":"2023-01-28T22:20:08","guid":{"rendered":"https:\/\/hml2.stract.to\/blog\/nao-categorizado\/how-to-calculate-your-cost-metrics\/"},"modified":"2023-01-28T19:20:08","modified_gmt":"2023-01-28T22:20:08","slug":"how-to-calculate-your-cost-metrics","status":"publish","type":"post","link":"https:\/\/www.hml2.stract.to\/en\/blog\/uncategorized\/how-to-calculate-your-cost-metrics\/","title":{"rendered":"How to Calculate Your Cost Metrics?"},"content":{"rendered":"

A common question is how to work with calculated metrics such as CPM, CPC, CTR, and others.
This happens because, when you bring data from your accounts into Stract and select fields like CTR or CPC, you’ll get something like this table:<\/p>\n

\"\"<\/p>\n

When you connect your table to Data Studio and use the CTR and CPM fields, you’ll notice that the data doesn\u2019t match the manager and the real value of these metrics for the period.
This is due to the aggregation that Data Studio applies to composite metrics:<\/p>\n

\"\"<\/p>\n

Even if you change the aggregation to “average” instead of “sum,” Data Studio will still generate different results:<\/p>\n

\"\"<\/p>\n

In some cases, the difference might be small, but in general, it\u2019s recommended to work with the calculation inside Data Studio.<\/p>\n

To create your calculated metric in Data Studio:<\/h2>\n

Access your Google Data Studio report and create a custom field:<\/p>\n

\"\"<\/p>\n

To calculate the cost per any desired metric, you\u2019ll use a formula similar to this:<\/p>\n

SUM(Cost) \/ SUM(Metric)<\/strong><\/p>\n

The SUM represents the total cost divided by the selected metric. Using Stract\u2019s fields, it would look like this: <\/p>\n

\"\"<\/p>\n

With that, you just need to create the calculated fields for each metric, such as Cost\/Conversion, Conversion Rate, etc.
One note: the CTR sent by the Facebook Ads API needs to be divided by 100.
If the data still shows discrepancies with the Manager, it\u2019s worth checking the support articles: <\/p>\n