Are the "%mkt_webview_url%?mkt_tok=##MKT_TOK##" links tracked? | Community
Skip to main content
A
Anonymous
July 20, 2016
Question

Are the "%mkt_webview_url%?mkt_tok=##MKT_TOK##" links tracked?

  • July 20, 2016
  • 1 reply
  • 3930 views

Question for the Marketo gurus. Are click-throughs on the the links generated by the "%mkt_webview_url%?mkt_tok=##MKT_TOK##" system level token tracked?

We started using the "{{system.viewAsWebpageLink}}" on some of our templates more recently, and it appears click-throughs on those links are tracked, but, having clicked on a few of the "%mkt_webview_url%?mkt_tok=##MKT_TOK##" links myself, and having examined my activity log, as well as link reports for older e-mails which used the "%mkt_webview_url%?mkt_tok=##MKT_TOK##" token, I don't see any activity log entries or click-throughs.

Bonus question. What's the logic/benefit behind creating these two different tokens? We're working on a program that's triggered by an API call and noticed that this program, which uses the "{{system.viewAsWebpageLink}}" token, doesn't generate a web version that's usable. The bulk of the content is populated by the API call into tokens, but the tokens show up with their placeholder content rather than the content which was included in the API call when the "{{system.viewAsWebpageLink}}" is viewed. (Looks fine in the e-mail, but virtually nothing appears on the "{{system.viewAsWebpageLink}}" version since the bulk of the content is from the token.)

Wasn't true when we used the "%mkt_webview_url%?mkt_tok=##MKT_TOK##", but, due to the structure of the HTML, we'd prefer it be part of the template itself rather than use the "%mkt_webview_url%?mkt_tok=##MKT_TOK##" approach.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
July 20, 2016

Are you sure that the %mkt_webview_url% actually included the dynamic {{my.tokens}} from an earlier Request/Schedule Campaign API call, but the {{system.viewAsWebpageLink}} does not?  That sounds unlikely to me as they are expected to point to the same renderer.

A
Anonymous
July 20, 2016

Thanks, Sanford!

We actually have both of them running in our production instance right now. The new program contained the {{system.viewAsWebpageLink}} token. The e-mail looked great, but when we clicked through on the link generated by the {{system.viewAsWebpageLink}} token, the web version was "empty". We're in the process of testing, so only I and another colleague are receiving that e-mail when the campaign is triggered by the API call. (We've now removed the {{system.viewAsWebpageLink}} token and linked to some equivalent pages on our site since we couldn't get it working.)

To be clear, it did generate a link, but the areas where the tokens sat in the template (tokens also populated by the API call) were populated with the token's default content. Three periods (...), since the tokens can't be empty.

The second program, which is meant to be replaced by the new program once we hammer out this last issue, uses %mkt_webview_url%?mkt_tok=##MKT_TOK## and its web version renders correctly. We send it daily to and there's never been any issue with the web versions.

As for the renderer, I had assumed as much since the root path is identical, but still, no luck. Any insight as to why there are two different tokens for this? My suspicion was that they aren't quite identical. (Otherwise, why not eliminate the %mkt_webview_url%?mkt_tok=##MKT_TOK## method entirely?)

SanfordWhiteman
SanfordWhiteman
Level 10
July 20, 2016

If the entire path including the hostname, pathname, and mkt_tok is the same in the browser, they must render the same.

Terms & ConditionsAccessibility statement

Loading footer...