Allow UTM tracking codes to work with dynamic variables

[BricoleR9]

We have multiple lists like I imagine many others have in their email campaigns. These lists represent different sources of leads (some from FaceBook, Google, Website newsletter sign ups, etc) Each contact is on a different list. When we send email campaigns, we select multiple lists for the email to go out to. We usually hard code in UTM parameters for utm_source, utm_campaign, utm_medium, etc.  So that we can use this data in Google Analytics to understand the effectiveness of each campaign.

For the utm_source campaign, it's great to not just "Constant Contact" as the source. From an email marketing perspective, it's better to identify the utm_source as something more meaningful, like "facebook email subscribers", or "google ads subscribers", or "past customers", etc. This lets you identify the source of your leads and how each lead segment is performing.

In our case we have about 5-6 different contact lists. Most of these lists receive the same promotional email. For efficiency, we send out our mailing and check all the lists to send it to. But this doesn't allow us to break down our mailing by "Contact List". In this case, we just have to hard code in the utm_source as "subscribers", which doesn't give us the real lead source.

It would be amazing if Constant Contact could allow us to dynamically substitute at send time, the utm_source with the appropriate contact list's name.

I'm thinking it would be something like, utm_source={Contact List Name}

This would allow better tracking in Google Analytics and prove more granular data which most marketers would appreciate and start employing, to better understand which lists their buyers were on, etc.

If contacts were on multiple lists, then you could add a feature to be able to set a Contact's "List Priority", meaning if the person was on say both List A and List B, and if you had set List B as the priority, the utm_source would use the List B as the parameter.

[Frankie_P]

Hi @BricoleR9

At this time we do not officially support UTM tags, and do not know to what extent they will work if added outside of Constant Contact on the user's end at as a result of that. We do however want to update the status of this request to support our new community idea statuses and add better insight into your feedback. We can't guarantee a commitment to deliver on this feature request but should indicate some awareness that we have heard your feedback and are continuing to collect both requests along with use case examples. 

[Aldercoop]

I'm a big fan of this. I would love to be able to distinguish clickthroughs based on data like that