Structure of the Mirror Page link | Community
Skip to main content
Selliers
Selliers
Level 4
August 11, 2025
Solved

Structure of the Mirror Page link

  • August 11, 2025
  • 2 replies
  • 788 views

I wonder i sombody knows anyting about how the Mirror Page link is build, the structure of the link.
I have faced a problem that in some cases I get a Mirror Page URL without the /ee in the final link in an email. And that link does not work. Sometimes I get a Mirror Page with the /ee included in the link, and then it  works. I can manually change the link in my browser (set in the /ee in the right place, and then it works)

https://data.nordea-test.cjmadobe.com/ee/v1/ ..................

https://data.nordea-test.cjmadobe.com/v1/ ..................

So the one million dollar question, what causes the /ee to be created in the final link, and what make this to be left out when rendering the link. Since it is the same mistake every time withe the same letters, this to letters must have some connection to something in the solution - putting them into the final URL.

Best answer by Selliers

We have run more tests regarding this challenge with the Error in the Mirror Page link. And the new findings seems where interesting. If you have a Mirror Page link inside of a email fragment, The fragment is not broken, and if you turn of all email tracking (opned and clicks) the Mirror Page link fails. In the URL structure there will the be missing /ee. If we then manually put /ee into the link in the Browser, it works. 

The newest teori is that there is something going on when using email fragments, and removing the email tracking. Mirror Page links then generated without a /ee in the link, and will then fail. Why /ee is kept out from the URL when the link is inside a Fragments, and the tracking is tuned off, is the next question in this saga.


We have now got a respond recognizing this issue as an AJO bug. We see that turning of the email tracking is breaking the mirror page link in an email fragment that has not the heritage broken. If you break the heritage on the exact same fragment, the link will then work.    

2 replies

gengaipandi03
gengaipandi03
Level 4
August 11, 2025

Both urls are generated after the publish or one for during test run and another for normal publish?

 

Selliers
SelliersAuthor
Level 4
August 11, 2025

In the Journey where this comes from there is two email nodes, the Journey is published and the email has been sent. But for some reason the Mirror Page link is different in those two emails. They use the same fragment, where the link is stored, but the result for the end user, in there inbox is different. When I compare the two links, there is /ee that is the difference from the one that works and the one that don't work. For some reason the /ee is not been rendered into the url string for one of the templates. 

Pulkit_Jain_
Adobe Employee
Pulkit_Jain_Adobe Employee
Adobe Employee
August 14, 2025

@selliers 

The /ee in your mirror page URL is essential—it routes the request to the email engine backend to render the online version of your email. If you get a link without /ee, it will not work.

It's likely due to a template, personalization, or fragment issue—most often a hardcoded string or out-of-date block. Is the mirror page link hardcoded or inserted incorrectly in the template or fragment?
Ideally, when creating these links, always use the platform’s built-in mirror page personalization block, never a manual URL.

    Selliers
    SelliersAuthor
    Level 4
    August 14, 2025

    Thank you for your answer - and this makes sense. We have since this post was posted done enormous amount of testing and checking to find the source of the problem. And we have found some thing I would like to highlight here. 

    We see that if we create a email in a Journey, and in this process we create the email template totally from scratch (blank) we get it to work. The mirror page link is created in a fragment, that is dragged into the template, and nothing else. Then the link works. 

    But if we create the template before the email is created. Store the template in the "library" with the exact same fragment as before. When the mail is been created, we then dont create it from scratch but we use the store template. We do nothing else with the template. The mirror page link in this case dont work. Everything i similar, the only difference is how the template is created -stored before the mail is created, or created on the fly with the email. 

      Pulkit_Jain_
      Adobe Employee
      Pulkit_Jain_Adobe Employee
      Adobe Employee
      August 14, 2025

      Thank you for documenting your testing!

      So if I understand the observations correctly, 

      • If you create an email template from scratch within a Journey and add the mirror page link fragment, the link works.
      • If you pre-save the template to the library (using the same fragment), and later use this template to create an email in a journey, the mirror page link does not work—even though nothing else has changed.

      The only variable is whether the template was created “on-the-fly” in the Journey, or pre-saved in the library and then used.  

      This is a perfect candidate for a reproducible bug that can be logged with the product team. Please provide examples of working and non-working links (including fragments, templates)

        Terms & ConditionsAccessibility statement

        Loading footer...