Build a List from a List | Community
Skip to main content
derrickr8850025
derrickr8850025
Level 2
November 8, 2017
Solved

Build a List from a List

  • November 8, 2017
  • 3 replies
  • 2762 views

Hey

Has anyone done the following?
Built a list based off of X number of recipients.

So you have ListA.

You send out a campaign that goes out to ListA.

As recipients get open and click the emails, you build a list off of that.

So at the end of the month/campaign, you have:

ListB = people that opened the email

ListC = people that clicked on links in the email

What's the best way to handle that?

    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 Pabst_dk

    Hi Derrick,

    Giving that you are not on AC standard this is one way to do it:

    Create a WF taking the same target group (ListA) and add a segmented split to the WF set as below:

    • Both branches should have the delivery internal name (as it is a primary key) matching the email send
      • first branch has segmented on open = true
      • second branch should have clicked = true

    Each branch will go to a list update element for their designated list.

    I would recommend you to decide when the data should be extracted and run the WF once, or to have the WF running on a scheduler for a given time period to catch up the data.

    One issue here could also be how to differentiate on the clicks and opens due to that we can expect that some of the recipients will have opened and clicked in the email. As standard the segmented split will extract the recipients from the target in the order of the branches.

    Hope this gives you the idea of the setup

    Best, Jonas Pabst

    3 replies

    Pabst_dk
    Pabst_dkAccepted solution
    Level 2
    November 9, 2017

    Hi Derrick,

    Giving that you are not on AC standard this is one way to do it:

    Create a WF taking the same target group (ListA) and add a segmented split to the WF set as below:

    • Both branches should have the delivery internal name (as it is a primary key) matching the email send
      • first branch has segmented on open = true
      • second branch should have clicked = true

    Each branch will go to a list update element for their designated list.

    I would recommend you to decide when the data should be extracted and run the WF once, or to have the WF running on a scheduler for a given time period to catch up the data.

    One issue here could also be how to differentiate on the clicks and opens due to that we can expect that some of the recipients will have opened and clicked in the email. As standard the segmented split will extract the recipients from the target in the order of the branches.

    Hope this gives you the idea of the setup

    Best, Jonas Pabst

      derrickr8850025
      derrickr8850025Author
      Level 2
      November 13, 2017

      Hi I think that makes sense but let me make sure I understand the workflow

      Start

      Read List which pulls from the already established list

      Reconciliation to validate that the Read List exists in Recipients

      Segmentation split on Click/Open

      Create Lists based on results

      I just want to ensure that the List can be tied to recipients so I can track everything

      Pabst_dk
      Pabst_dk
      Level 2
      November 15, 2017

      Hi derrickr88500252,

      I had no possibility to add a screenshot on private messages so adding it in here.

      Below you can see a setup of the click branch.

      Change the Type and Internal name to match your delivery.

      I have set the status to only lookup the deliveries send to the recipient, but thats up to you which status to use. But I would recommend to use the send status so you don't have to look through data on deliveries there haven't been sent to the recipient.

      Regarding the list: Yes it will be updated with recipient data that you can refer to directly,

      Best,

      Jonas

        Terms & ConditionsAccessibility statement

        Loading footer...