utm_name/utm_campaign issue

[timgl]

Segment, for whatever reason, sends utm_campaign properties as utm_name. While confusing, this was mostly fine. However, about a month ago I accidentally committed this line, which started sending all utm_name properties as utm_campaign.

Going forward this feels right as it consolidates everything. But right now we've got a lot of user properties that are slightly wrong.

I'm creating this issue to note down what I did for future reference.

Specifically:

• There are 89 teams that have this issue, with a total of 3.4 million persons affected.
• organizations affected

To fix this, for each person we need to

• grab $initial_utm_name and set it as $initial_utm_campaign
• grab utm_name and set_once it as utm_campaign

We'll send a non-billable event for each person to set those properties. I wrote a little temporal python script to do this.

It'll be hard/impossible to fix events, so I think it's okay to just leave those be.