Moving forward/Backward in program status instead of progressing | Community
Skip to main content
N
Neelam1991
New Participant
August 9, 2023
Question

Moving forward/Backward in program status instead of progressing

  • August 9, 2023
  • 1 reply
  • 3267 views

Hi,

 

Can we move program status in forward/backward ? 

 

In my scenario, data is received twice a week, and there's a possibility that the next batch of data may include individuals already present in the previous batch. Such common records also must be targeted. The client requires a report that tracks sent, delivered, opened, clicked, and purchased counts. To achieve this, I've established a four-step channel with designated sequential step numbers. The campaign activity reports allow the client to observe counts based on trigger campaigns.

 

However, in cases where a person's status changes to "clicked checkout page" in the first round, but in the subsequent round, they didn't click the checkout page only opens the email, then it should be reclassified as "Opened." I researched in the community and discovered that we can navigate forward and backward by maintaining the same step number like below across different statuses. So I tried it but I haven't observed any change in status.

Pls advise on this .

 

Regards,

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

1 reply

C
ChristianeRo1
Community Manager
August 9, 2023

You are correct in that you can only progress (higher step ##) or move laterally (same step#). 

 

However, with your setup the way it is, you will be erasing the historical program activity. So, if you're just looking at program status as a means of a person's activity, if they clicked in the first email, but were only delivered the second email, then you erase their previous progress. 

 

Is there a reason you don't have these set up as different programs to retain this data?

 

Additionally, I do caution using "delivered" and "opened" as statuses. Just because someone was delivered that message doesn't mean that it was actually delivered to them (I've even had messages trigger a delivery but then later bounce). And, given the way that the tracking pixel could either automatically load with MPP or image prefetching, or won't load if images are turned off, this status may also prove to be unreliable.

    N
    Neelam1991Author
    New Participant
    August 9, 2023

    Hi @christianero1 ,

     

    Thank you for the quick response.

     

    I had also been considering the idea of creating separate programs for each execution to maintain individual status data for every member. However, before proceeding, I wanted to confirm whether it's feasible to backtrack within the same program or not.

     

    Based on your explanation, it appears that moving backward within the same program is not achievable unless you completely clear the existing status and then update it anew. Unfortunately, this approach poses challenges from a reporting standpoint, as the initial status would not be reflected in the reports of prior executions, leading to inaccurate analyses.

     

    So it would be preferable that I should create a separate programs for each execution round.

     

    Regards,

      Darshil_Shah1
      Darshil_Shah1
      Community Manager
      August 9, 2023

      Agreed with @christianero1!

       

      Additionally, program channel statuses were never intended to be used in use cases where you'd need to move people to backward stages. Ideally, a person can be a member of a program with a particular status, and their status could only move to any of the next higher statuses, as the highest order status determines the maximum level of expected channel interaction the person has had, and it won’t make sense to demote a member to a lower status value. Also, are the interactions you receive from the different marketing campaigns or just a single large marketing campaign?

      Terms & ConditionsAccessibility statement

      Loading footer...