How would you setup Smart Campaign for all Canceled Accounts BUT not in past 30 days? | Community
Skip to main content
R
RonnBu
New Participant
June 14, 2019
Solved

How would you setup Smart Campaign for all Canceled Accounts BUT not in past 30 days?

  • June 14, 2019
  • 1 reply
  • 4606 views

This Company has never sent marketing to former clients or implemented any sort of re-engagement campaigns for 20 years. I'm building a Nurture Program to do so.

My Goal is for all Canceled Accounts to enter Stream 1 so long as and/or after 30 days have passed since they Canceled. This is only a one-time issue because once this initial batch is in motion the conditions are set up as such so they won't re-enter the Program for another 30 days.

Entry conditions to enter Stream 1 is basically these groups but I may be over complicating it.

1. (Batch) Canceled Accounts on or Before 30 Days Ago
2. (Batch) Canceled Accounts in the Past 30 Days
3. (Trigger) Data Value Changes: Account Status value become 'Canceled'. A 30 day wait in the Flow step. This one is easy.

The smart campaign batch is tricky because Account Status = Canceled provides the total of Canceled Accounts which will include all of those within the past 30 days. I should also note that it is not as easy as using "Data Value Changed" filter as our custom CRM indicates 28,958 Canceled Accounts but only 2000 as a results of "Data Value Changed" so that data is not usable for this.

What is the best way to set this up?

I feel like this can be done any number of ways such as Nested Program, Add to List (Exclusion), Member of Smart Campaign (Not in) just off the top of my head.

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 Jay_Jiang

Data value changes is limited to 3 months of history. 

You achieve what you need by

1. create a smart list/smart campaign and add the filter Data Value Changed, Status is Cancelled Account, Date of Activity is In past 30 days. These meet your criteria of cancelled in the last 30 days or less. 

2. create a smart list/smart campaign and add filters

   i) Status is Cancelled Account and;

   ii) Not Data Value Changed, Status is Cancelled Account, Date of Activity is In past 30 days

   These meet your criteria of cancelled greater than 30 days ago.

3. I recommend creating a datestamp field that is date stamped when status changes to 'Cancelled Account'. Instead of creating a trigger campaign with 30 day wait step, create a daily/weekly batch campaign that runs if the Cancelled Account datestamp is within range (i.e. same day for daily batch or within last 7 days for weekly batch). It's up to you if you wish to manually datestamp existing data with a fictitious date

1 reply

Jay_Jiang
Jay_JiangAccepted solution
New Participant
June 17, 2019

Data value changes is limited to 3 months of history. 

You achieve what you need by

1. create a smart list/smart campaign and add the filter Data Value Changed, Status is Cancelled Account, Date of Activity is In past 30 days. These meet your criteria of cancelled in the last 30 days or less. 

2. create a smart list/smart campaign and add filters

   i) Status is Cancelled Account and;

   ii) Not Data Value Changed, Status is Cancelled Account, Date of Activity is In past 30 days

   These meet your criteria of cancelled greater than 30 days ago.

3. I recommend creating a datestamp field that is date stamped when status changes to 'Cancelled Account'. Instead of creating a trigger campaign with 30 day wait step, create a daily/weekly batch campaign that runs if the Cancelled Account datestamp is within range (i.e. same day for daily batch or within last 7 days for weekly batch). It's up to you if you wish to manually datestamp existing data with a fictitious date

    R
    RonnBuAuthor
    New Participant
    June 17, 2019

    Thank you, Jay! Makes perfect sense. Funny how much it makes sense and how easy it becomes once you know the answer. Like reading it is easier than writing it. The Inactivity Filters are so confusing I rarely utilize them out of lack of trust. I've never hear or read the "look at them like this..." perspective trick to make sense of them and therefore use them with confidence.

    A couple quick questions for clarity.

    1. Do tokens work in the flow of Batch Campaigns? I thought it had to be a trigger campaign.

    2. Are saying I'll have I'll have these 4 Smart Campaigns: 1. Cancelled Greater then 30 days 2. In Past 30 Days 3. Date Stamp Account Cancellations (screenshot below) and...

    ..... 4. Batch New Cancels rather than Trigger: But How do I do this one exactly?  The daily batch provides me with the total number of Cancelled Accounts over the past 24 hours but how do I get them to enter the program 30 days after they canceled their account?

    Instead of creating a trigger campaign with 30 day wait step, create a daily/weekly batch campaign that runs if the Cancelled Account datestamp is within range (i.e. same day for daily batch or within last 7 days for weekly batch). It's up to you if you wish to manually datestamp existing data with a fictitious date

    3. How would you suggest I add the fictitious date value for all existing records?

    4. Is this correct for the Date Stamped record moving forward?

    Thank you so much for your help with this!

    Jay_Jiang
    Jay_Jiang
    New Participant
    June 18, 2019

    Correct, you'll have 4 smart campaigns

    Do tokens work in the flow of Batch Campaigns? I thought it had to be a trigger campaign.

    Yes tokens work in batch campaigns. You're probably thinking of the {{trigger.}} ones that don't

    The daily batch provides me with the total number of Cancelled Accounts over the past 24 hours but how do I get them to enter the program 30 days after they canceled their account?

    Is this correct for the Date Stamped record moving forward?

    I didn't think through the answer in as much detail as I should have. In response, you may decide to create 2 datestamp fields. 1 to record the cancel date (this is the optional one) and 2 to calculate the nurture start date (this is used in the daily/weekly batch campaigns). 

    To calculate the nurture start date you can use either a trigger or batch campaign like in your screenshot, but the change data value in the flow should be               New Value: {{system.date}} + 30 days         

    Then, in your daily/weekly add to nurture batch campaign, you can use the start date's filter with              In Past: 1 day             but most importantly schedule so lead can only run through once

    How would you suggest I add the fictitious date value for all existing records?

    The suggestion to create a fictitious cancel date wasn't anything sophisticated, the reasoning behind it was so you could bucket accounts cancelled in the initial set up by setting their cancel date as e.g. 1/1/2019, which would be just a mass change data value

    Terms & ConditionsAccessibility statement

    Loading footer...