Grace_Brebner3

+1 to Josh Hill​'s answer, this is what I've always done, just looks like:Alex Munro​ is correct too, especially on the why. A partial URL would work, and including the http:// reference won't necessarily make it not function as a link, Marketo just won't track it.But definitely make sure you test carefully, it's easy to accidentally include the http:// in the token, or miss it in the tag.On a side note, I've also used separate tokens for links and UTMs in the past, which can be a handy way of ensuring UTM consistency.

Hey Laura,It might depend on exactly what you're trying to show in the report (i.e., is the focus just the number of people, the performance of the email or the performance of the leads). You probably want to create an email performance report with some smart list filters to restrict it to exactly t...

Congrats everyone!

Thanks for compiling & sharing, Jessica Kao​! Such a useful resource for those of us who weren't able to be there this year & struggle to find the time to watch the recordings. Of the ones I have had the chance to watch, I actually really enjoyed yours. Reporting and analytics is always one of the p...

Hey Calvin,We logged tickets with Marketo support and they've said that universal ID only works for different instances under the one account (e.g. production vs sandbox) and wouldn't allow me to switch between my different unrelated clients under the one ID (posted this idea on their recommendation...

I agree with both Rachel Noble​ & Josh Hampleman​'s suggestions for the most part - either option could work for you, depending on how your organisation's comms are typically structured. I'd be interested in hearing more about whether you mostly use Engagement Programs for your comms, or whether man...

Hey Addy, no problem!I'd say part of your consideration here then should probably be future proofing.It sounds like your small team is running both brands rather than having independent teams separated between the two. Much of the benefit from different workspaces is being able to control which user...

I'd be interested to hear more about your specific use case. I.e., how big is your team? How are you thinking about splitting your workspaces? Will you have team members or data that you would like to restrict to only accessing one workspace/partition?I haven't found workspaces and partitions overly...