Can you use a range in filters?

[Chelsey_Davis]

I'm trying to create a campaign that will bucket people into three different categories based on how many times a certain field is populated within a three week period. For example, our users get triggered into a campaign that basically sets them to "Active." People will turn "Active" on a rolling basis, and three weeks after being "Active," we want them to receive a message based on a bucket they are in:  good, ok, or bad.

The buckets are based on a field (OE_QUIT_TIME) that populates and then nulls out every night at midnight via our own API push. The field is populated by user behavior.

For example:

OE_QUIT_TIME populates 0-5 times = Good

OE_QUIT_TIME populates 6-15 times = OK

OE_QUIT_TIME populates 16+ times = Bad

The Bad one listed above is fine; I can set "Data Value Changed" with a constraint of a min. number of times = 16. But the other two is what I'm having trouble with. If I set a min. number of times, they will still qualify for, say Good, if the quit time populates 7 times because they only have to meet the requirement of 5. I've tried messing around with inactivity filters, but I think the logic is a little weird...at least to me.

The OE_QUIT_TIME is the only way I can determine if a user did this particular behavior, and having it populate is how we know how many times users are doing this behavior.

If anyone has any ideas on how to get these ranges in place using filters, I would appreciate it!

[SanfordWhiteman]

Nested Smart Lists.

If they're in SL "Min. 0" but not in SL "Min. 6" == between 0-5.

You can also use a score field. Have choices in descending order and only the first one will match: if score > 16 | if score > 6 | default choice.

[Chelsey_Davis]

I tried using the smart list option, but when I include in the smart list for the smart campaign "member of SL Good" but "not member of SL OK" it doesn't recognize it and no one goes through the flow for some reason.

I'm not sure how I can use a score field for this one...

[SanfordWhiteman · Accepted solution]

You'd have to show some screenshots of the setup for us to look at it further. The SL-with-exclusion-SL concept is pretty common. If each SL is right otherwise then the combination will work.

With the score option I mean you bump a score every time the value changes (and reset it every night, just like you reset the OE_QUIT_TIME nightly). The score is then the same as the number of times. By adding choices in a flow step you can conditionally add them to more than one bucket. You put the higher buckets in descending order, since when they match one they won't match the ones lower down.

[Chelsey_Davis]

Oh man... I didn't think to use the score in that way, but that works for this campaign.

Thank you so much!!!