Email Viewed as Webpage Returning an Error after Refreshing Browser - "Customer does not belong to any POD" | Community
Skip to main content
KCS_Integration
KCS_Integration
Level 2
March 19, 2019

Email Viewed as Webpage Returning an Error after Refreshing Browser - "Customer does not belong to any POD"

  • March 19, 2019
  • 4 replies
  • 2598 views

Issue Description
In sent emails, if the system token {{system.viewAsWebpageLink}} is used, the link will load successfully on web browsers. However on the same browser session, after refreshing the page once, the link will return an error "Cannot get email content- Customer does not belong to any POD".

Issue Resolution
After Marketo's 2019 Q1 release, a security enhancement has been set for Marketo emails. When loaded on a browser, a View as Webpage Link will include the recipients' unique mkt_tok parameter. If recipients of the Marketo emails were sharing these links, this would mean that they are also sharing their unique/private mkt_tok with third parties.

With this enhancement, the view as webpage link is only expected to load once and the mkt_tok value which is contained in the link will disappear after the page has loaded. With the removal of the mkt_token value on the link, hitting refresh will send a request to Marketo that does not contain the recipient's lead and email information, so there is no data for the link to return.

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

    4 replies

    Sarah_Burlhis
    Sarah_Burlhis
    Level 1
    March 19, 2019

    Does this mean we can no longer share that link with anyone?

    That was what we were using to proof emails in cases where sending samples would not make sense.

    Sarah Burlhis
    SanfordWhiteman
    SanfordWhiteman
    Level 10
    March 20, 2019

    Does this mean we can no longer share that link with anyone?

    • You can still share the tracked link from the email if you want.
    • You can't share the target link after it gets redirected and URL gets stripped.
    • You can still share the target link if you open the tracked link using the view-source: protocol. That is, open the URL view-source:http:​//tracking.example.com/dc/abc123def456 in your browser. In the JS you'll see the target link with the mkt_tok still present, which you can send around.
    Nick_Greca
    Nick_Greca
    Level 1
    March 20, 2019

    We're also experiencing this same issue.

    Removing the static view online URL has caused:

    - inability to share the URL with partners for review (contrary to what's posted above, our installation redirects once TO the email, and now once again FROM the email, so there isn't enough time to grab the URL before it changes)

    - inability to Refresh (F5) the browser window to see an updated version of the email (this just refreshes the Javascript redirect/destination file)

    - inability to view the source code of the email in the browser (it only shows the source code of the JS file)

    - Clicking a link in the email and navigating to a different page, there is no way to navigate back to the email in the browser using the browser's Back button (same error as above "Customer does not belong to any POD")

    - the error screen itself is jarring and simplistic--our users think there is something wrong with the system.

    Please revert if possible, or provide an alternate way to review email content.  This change has created more problems than it solves.

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    March 20, 2019

    our installation redirects once TO the email, and now once again FROM the email, so there isn't enough time to grab the URL before it changes

    Well, the first (from the branding server to the target LP, if you're tracking this link) is an actual JS location redirect.

    The second URL change is an in-place history replacement (not actully a redirect, the page is not re-fetched from the server).

    If you open view-source:http:​//branding.example.com/unique123codeABC, then you can share the internal link (which includes the mkt_tok). Of course that doesn't solve the other consequences.

    I wish you luck in getting this reverted, I don't like it either but assume it's here to stay.

    Terms & ConditionsAccessibility statement

    Loading footer...