Re: View in browser -> 404

Anonymous
Not applicable

Hi All,

I'm currently seeing a weird problem, which is happening when I send an email to myself (as a regular lead, not a sample email) and then click "view in browser".

I get a 404, the redirect url is empty. the links looks like http://mkto-sjXXXXXX.com/v/TTeRq0U07000fE910N0XXXX"http:/promo.XXXX.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiWkdSaVpHRTJZakE1T1dZeSIsInQiOiJaYS9sQVRHOHZPR2dJZzlIL0tTZWFrM0x6UWxZRTJKVDltNFhZZ3lLUXB3Qis5Q1hxcUliWVhITmtrUFcveW1IYjdHL09BTUwwcnFCK2t2OVJ6QmZ1Ky95ZlZXYXhHWStET0F1Rm9BQ3dvQWNzU3preUZjQnFlZ1ovSTM5d3FxRSJ9

Any takers?

Tags (2)
15 REPLIES 15
SanfordWhiteman
Level 10 - Community Moderator

You've gotta post the real URL.

Anonymous
Not applicable
SanfordWhiteman
Level 10 - Community Moderator

Are you using the {{system.ViewAsWebPageLink}} or building your own?

Anonymous
Not applicable

I'm using the {{system.ViewAsWebPageLink}}

SanfordWhiteman
Level 10 - Community Moderator

Try creating a link that has Enable mkt_tok disabled:

pastedImage_8.png

and this href:

<a href="http://promo.abbyy.com/index.php/email/emailWebview?mkt_tok=##MKT_TOK##">View as web page</a>

Is this tracked and functional?

Anonymous
Not applicable

Yeah, it is.  Wonder what's breaking the redirection using native Marketo functionality?

SanfordWhiteman
Level 10 - Community Moderator

I'm wondering too! There've been some reports tonight (I got some via email as well) of broken tracked links, though not mentioning the View as Web Page specifically. I haven't been able to reproduce the problem across 3 instances. Like many such problems it could be localized to certain pods.

Scott_McKeighe2
Level 5

I'm having a similar problem with a VTL script-driven URL. Preview renders the output URL correctly but it looks like Marketo's failing to encrypt prior to send:

Screen-Shot-2017-11-04-at-10.37.09-AM.png

For reference we're pulling a specific Marketo Custom Object string value into an anchor tag, like this:

<a href="https://${customobject_cList.get($a).LinkURL}">Some such text</a>  

Wondering if I need to establish some other parameters like notrack and mkt_tok, or taking a different tactic and encoding the entire URL output into that custom object variable.

If anyone has an idea what might be happening, I'd love to hear from you

SanfordWhiteman
Level 10 - Community Moderator

Also, I used a list with the same structure and your exact code and didn't have the same problem. Are you using this CO in some other VTL in the same email (try reducing the email to just this token to test)?

Scott_McKeighe2
Level 5

Hey there again, Sandy.

Just finished trying a few versions of an intermediate variable ($url). The encryption step seems to work—Marketo is successfully passing a tracked  URL:

Screen Shot 2017-11-06 at 11.31.50 AM.png

But the actual output behind that encrypted URL is this:

Screen Shot 2017-11-06 at 11.33.27 AM.png

As you can see it's just pushing an encoded version of "$url" instead of the desired URL value

SanfordWhiteman
Level 10 - Community Moderator

You have my email, I think -- ping me and we can work on this offline.

Scott_McKeighe2
Level 5

I do, both of them in fact. Sent!

Scott_McKeighe2
Level 5

Hey there Sandy,

I was able to get the URL functional with mktNoTrack, but haven't taken it from there to do anything else yet. I am using the CO twice in this scenario -- once to grab a specific range of data (top 3), and again to grab the remainder and style it differently in a separate section.

Can you explain the [$a] suggestion a little bit more? My understanding of the syntax here is falling behind.

Thanks

Scott_McKeighe2
Level 5

Ok I tried the [$a] syntax you described above (thanks!). Worked in the script, but the inbox output was still the same. Also tried reducing the script to one instance, and still getting the same tracking decoration failure

SanfordWhiteman
Level 10 - Community Moderator

Have you tried this with an intermediate variable? Also use [$a] instead of the wrapped .get($a). Let me know... there's always some permutation that works in these weird post-parsing situations