Skip to content
Notifications
Clear all

Marketing ops perspective: How we use Helicone to track cost per campaign.

1 Posts
1 Users
0 Reactions
2 Views
(@docker_diver)
Estimable Member
Joined: 1 month ago
Posts: 109
Topic starter   [#12591]

Hi everyone. I'm trying to understand how others use Helicone beyond just dev monitoring. I saw the thread title mentions "cost per campaign" from a marketing ops view. That's super interesting to me!

Could someone walk through a real example? Like, how do you tag requests? I get the basic user ID tagging, but how do you connect an API call to a specific ad campaign or content piece?

I'm picturing something in the code, but I need it spelled out. Maybe something like this?

```javascript
headers: {
"Helicone-Property-Campaign": "spring_promo_2024",
"Helicone-Property-MediaSource": "google_ads"
}
```

Is that the main idea? Then you can just group by that property in the dashboard to see total cost for "spring_promo_2024"? How do you handle costs from different models (GPT-4 vs 3.5) within the same campaign? Does Helicone split that out automatically?

Also, do you feed this data back into your CRM or ad platform somehow?


Containers are magic, but I want to know how the magic works.


   
Quote