Using pURLs for batch or trigger campaigns

[Anonymous]

Hi!

We have a big event coming up and what we want to do is send out mass emails to our target lists with pURLs to each lead/contact. I had tried creating a custom URL field and tested it for short urls (i.e. nike.com), but we have lengthy URLs that we're using. Is there a way to successfully create pURLs for each lead in a massive list but have them shortened via a marketo url shortener or some kind of mass hyperlink (i.e. "click here")?

So for example, say we have 500 leads in one list. Each lead has a unique pURL.

So instead of abccompany.com, it will be

abccompany.com/john-doe

abcompany.com/jane-doe

abccompany.com/james-doe

etc, etc.

We could do that with a custom field and a personalized token in the email, but the email string will be very long. How can we abbreviate this or shorten the url, or maybe convert it to a hyperlink for everyone (i.e. "click here")?

Hope this makes sense. Any help is greatly appreciated!!

[Josh_Hill13]

Why would you want a PURL for an email? All email links are wrapped and tracked, unless you set mktNoTrack.

If you are saying you have a coupon code or something, then you could append that to the URL using a parameter token as you suggested. Just upload the two columns: Email | Coupon Code and it will work.

[SanfordWhiteman]

Totally agree with Josh. It doesn't make sense to generate pURLs (I think you're not really talking about Marketo pURLs, which are their own beast, but something like Bitly URLs) because the "short" URL will simply be rewritten to a longer tracking URL by Marketo.

So you'd end up with click.example.com/938f8fs723hsc763 -> bit.ly/23jwu -> pages.example.com/mypage.html, which doesn't offer any cosmetic advantages (it might offer specific tracking advantages if you like Bitly, but that's a totally different matter).

It also seems like from your next-to-last sentence you just want <a href="http:​//pages.example.com/mypage.html">click here</a> which is of course a standard link.

[Anonymous]

Thank you so much. This was really helpful! I think what we'll do is stick with the column upload to custom object. I tested it and it worked.