Trying to get "if you are not <email address>, click here" to remove preloading | Community
Skip to main content
EggBoy
EggBoy
Level 3
January 23, 2017
Solved

Trying to get "if you are not <email address>, click here" to remove preloading

  • January 23, 2017
  • 16 replies
  • 11515 views

Hi All,

We are working on trying to simplify how we reduce the effect of recipients forwarding emails with preloaded webApp links.

The basic "click here if you are not johnsmith@smith.com" message.

Currently we use 2 identical webapps....one with a link as below, that then links to another identical webApp that is not preloaded.

If you are not <%= ctx.vars.recipient.@email %> <a href="http://m.communications.waters.com/webApp/APP1924"> click here </A>

Ideally, we would like one webApp, and have a container with visibility set by whether or not the email was already preloaded.

We tried by setting visibility by @email is not empty, which almost works....but as soon as you fill in the email field and move to the next, the container shows.

So, there must be a way to set the visibility only if the form was preloaded.

You can see the problem at this link....type anything into the email field then move to another field...you will see the 'If you are not...." container show.

http://m.communications.waters.com/webApp/testingPreload

Is there anyway that this can be addressed? Note that I am not a developer...and right now don't really have easy access to an FED, alas.

Any help is greatly appreciated!!

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

    Hello,

    it seems that you are working on incomingLead not recipient. So, for option 1, instead [recipient/@id], can you try [incomingLead/@recipient-id]

    Regards,

    Damien

    16 replies

    Show previous replies
    EggBoy
    EggBoyAuthor
    Level 3
    January 31, 2017

    Hello Florent,

    Were are on build 8705 of 6.1.1

    We are finishing an integration in the next few weeks....and plan to address updating to the newest build in Feb or March at the latest.

    If you think that is the issue, I can go down the two webApp or two landing pages in a webApp for now...

    Thanks,

    Eugene

    EggBoy
    EggBoyAuthor
    Level 3
    January 31, 2017

    Hello Florent,

    Were are on build 8705 of 6.1.1

    We are finishing an integration in the next few weeks....and plan to address updating to the newest build in Feb or March at the latest.

    If you think that is the issue, I can go down the two webApp or two landing pages in a webApp for now...

    Thanks,

    Eugene

    D
    Adobe Employee
    ddphotoFrAdobe Employee
    Adobe Employee
    February 1, 2017

    Hello,

    it seems that you are working on incomingLead not recipient. So, for option 1, instead [recipient/@id], can you try [incomingLead/@recipient-id]

    Regards,

    Damien

    D
    Adobe Employee
    ddphotoFrAdobe EmployeeAccepted solution
    Adobe Employee
    February 1, 2017

    Hello,

    it seems that you are working on incomingLead not recipient. So, for option 1, instead [recipient/@id], can you try [incomingLead/@recipient-id]

    Regards,

    Damien

    EggBoy
    EggBoyAuthor
    Level 3
    February 1, 2017

    Hello Damien and Florent,

    The [incomingLead/@recipient-id] worked PERFECTLY!

    I guess another learning when asking questions is that we use Campaign 6.1.1 with Leads  :-)

    Truly thank you again!

      EggBoy
      EggBoyAuthor
      Level 3
      February 1, 2017

      Hello Damien and Florent,

      The [incomingLead/@recipient-id] worked PERFECTLY!

      I guess another learning when asking questions is that we use Campaign 6.1.1 with Leads  :-)

      Truly thank you again!

        Terms & ConditionsAccessibility statement

        Loading footer...