Skip to main content
gunjanm
gunjanm
Expert ⭐️
June 30, 2022
New Idea

Document the Participant Criteria Step Execution object

  • June 30, 2022
  • 1 reply
  • 68 views

There are a lot of nuances with what to expect when using this object to report on step-wise conversion of JO programs. The program has to be set up certain ways and some key understandings are required to use the object effectively. None of this is documented anywhere. We had to learn about all of this the hard way when our reporting looked significantly off from what we expected, and learned one key thing:

If I put in a condition of A AND B AND C AND...all the way to I, each of A through I must be TRUE in order to continue in the program, otherwise they will drop - which is fine, that is what I want. This also means that once any of A through E are FALSE, based on the issue identified, this object does not even attempt evaluating the rest of the expression values and so we do not even have the true value of F through I captured in reporting; they all show as FALSE. This inflates our positive conversion numbers for conditions F through I like crazy, as we essentially cannot isolate to individual conditions for conversion reporting. 

I wish we had known this before we worked on and presented a bunch of reporting around this to our leadership team.

    1 reply

    darkknight
    darkknight
    Expert ⭐️
    June 30, 2022

    Wow.  Reporting around Journey Orchestrator is terribly complicated enough already.  

     

    I typically advise against using JO (if you can help it) except for very simple, basic outreaches coming from a CS resource.  It’s way too complex to build, manage, troubleshoot AND report on - especially without a dedicated resource/team to own it. Other tools are better for email campaign targeting and we can ingest data from those tools into GS.

    Jeff Kirkpatrick
    Terms & ConditionsAccessibility statement