DTM Rule Approved, but does not show up on the site included. | Adobe Higher Education
Skip to main content
Preetpal_Bindra
Community Advisor
Preetpal_BindraCommunity Advisor
Community Advisor
June 1, 2017
Respondido

DTM Rule Approved, but does not show up on the site included.

  • June 1, 2017
  • 6 respostas
  • 4458 Visualizações

Hi All,

I have few set of rules that we configured to the web property. this web property has 2 report suites configured.

For the one corresponding to Staging, the rules fire correctly, however, when i "Approved" and "Published" the rules to use them on the production, none of the rules trigger.

The website includes both the header and footer code for DTM property.

When i look at the satellite js included on the page it does Not contain the rules i created neither for -staging JS not the productions JS.

Can someone please tell me, after I "Publish" the rule is there a delay in the rule to make it 'live' from the DTM end?

It has already has been over 5 hours since i published them.

To rule out the code logic issue, i created a simple page load rule, that too did not fire with the same web property.

    Este tópico foi fechado para respostas.
    Melhor resposta por Kaushalendra

    If you are not comfortable sharing the URL or if it is an internal site, please open a ticket with support by writing to <clientcare@adobe.com>

    6 Respostas

    Preetpal_Bindra
    Community Advisor
    Preetpal_BindraCommunity AdvisorAutor
    Community Advisor
    June 1, 2017

    Also to mention, the already present "older" rules are working fine.

    The new rules do not.

      Preetpal_Bindra
      Community Advisor
      Preetpal_BindraCommunity AdvisorAutor
      Community Advisor
      June 2, 2017

      Anyone?

        Andrey_Osadchuk
        Andrey_Osadchuk
        Level 10
        June 2, 2017

        Check if you are getting the latest DTM library version when testing the prod env. Type in the following code in the console to check the version:
        _satellite.publishDate;

          Preetpal_Bindra
          Community Advisor
          Preetpal_BindraCommunity AdvisorAutor
          Community Advisor
          June 5, 2017

          I tried it, it shows the latest, June 1st, when i did publish my code, and this is correct. However, I still do not see my rules firing when i set

          _satellite.setDebug(true); in the browser console.

          The same DTM web property has staging (pre-production environment) report suite configured. When i run the same rules on "staging"  mode environment, i see my rule getting triggered in the browser console and the data gets tracked in the eVar reports.

          However, when in "production" mode, I do not see the rules triggering in the console.

          Strange thing is that I do not see the rule firing on the page, though i see data getting tracked in the production report suite (less likely from a wrong site or environment).

          and another strange thing is that the data getting tracked is not the entire data I am generating. Meaning, it has some data in few reports and other reports do not have the generated data at all, which should have been tracked in them.

            jantzen_b
            Adobe Employee
            jantzen_bAdobe Employee
            Adobe Employee
            March 23, 2020
            Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?
              Andrey_Osadchuk
              Andrey_Osadchuk
              Level 10
              June 5, 2017

              Could you share the URL?

                Kaushalendra
                Adobe Employee
                KaushalendraAdobe EmployeeResposta
                Adobe Employee
                June 5, 2017

                If you are not comfortable sharing the URL or if it is an internal site, please open a ticket with support by writing to <clientcare@adobe.com>

                  Termos e condiçõesAccessibility statement

                  Loading footer...