Launch Rule Not Consistently Firing on Link Click | Community
Skip to main content
K
KMarchewa
Level 3
October 29, 2021
Solved

Launch Rule Not Consistently Firing on Link Click

  • October 29, 2021
  • 1 reply
  • 2175 views

Hello,

We have a a simple configured in Launch. The "trigger" event is merely Core -> Click with a simple CSS selector. There is no condition and the the "Action" portion is custom JS that fires a target mbox.

 

However, we are having issues with this rule firing consistently. It appears to be a timing issue. When the rule fails to fire, I notice a Warning being logged to the console: "Loading failed for the <script> with source “https://assets.adobedtm.com/xxxx/xxxx-source.min.js”.  This message does not appear when the Action fires correctly (with the "firing correctly" being verified using the Adobe debugger extension.) If I manually navigate to the script that the browser warns had failed to load, it loads just fine and I can confirm that it is the custom code I wrote for the "Action" in Launch. Additionally, the source (in Firefox's Dev Tools console) of the aforementioned warning is the initial/source page (the one with the link containing the rule trigger) not the destination page. However, the Warning itself is logged while on the destination page, not the source.

 

I am wondering if this is a common/known issues with Launch and how we might resolve. I realize there is an option to delay navigation in the "Click" event within Launch, but this is something we would like to avoid.

 

Any tips are much 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 Alexis_Cazes_

    Thanks for the information. Yes, it appears that the rule is firing correctly.

     

    The only extension used is Core (v1.8.3). The action type is a Custom Code that, in part, calls "adobe.target.trackEvent" to fire a custom mbox. It works consistently if I manually disable the link navigation event (that triggers the rule) and it works part of the time without any navigation delay inserted.

     

    Thanks again.


    Per what you described it might be linked to race issue. based on the documentation is seems you can specify an onSuccess callaback : How Do I Use the adobe.target.trackEvent() Function? | Adobe Target

     

    successFunctionNoA callback function used to signal that event has been reported.

     

    As the function only reports an event to target could it be as simple for your to preventDefault for the navigation link and once the success function is called navigate to your destination ? 

    1 reply

    Alexis_Cazes_
    Alexis_Cazes_
    Level 10
    October 29, 2021

    Could you provide us an url where we can test and see what is happening ? 

    If you cannot do that can you provide the adobe launch logs. 

     

    Is it the rule in itself that fails to fire or the action script that fails to run ?

      K
      KMarchewaAuthor
      Level 3
      October 29, 2021

      Thanks for the response. Unfortunately, I cannot provide a URL or logs. Sorry, I realize this will make troubleshooting difficult.

       

      How would I distinguish between the rule firing and action script? Currently, the only way I can determine whether or not it is operating correctly is using the Debugger extension and seeing if the mbox call (the action script) comes through. I assume the issue is caused by the action script failing to load (per the Dev Tools console), but why would it fail to load?

      Thanks.

        Alexis_Cazes_
        Alexis_Cazes_
        Level 10
        October 29, 2021

        A rule is successfully if you see in the developer console log (providing you enabled launch debug mode):

        🚀 Rule "MY RULE NAME" fired.

         

        Now if that is displayed the rule fired successfully, and if error is displayed then it means something in your action script fails at some point.

         

        Do you have more details on the extension version (I guess adobe target per your comment) and what you put in the action so we can try to support you

          Terms & ConditionsAccessibility statement

          Loading footer...