I am facing an issue using the "Added to list" trigger in my smart campaign.
Basically, I run a Default program sending an email. People go in several lists I defined based on their behaviors on my landing page (they can download several documents). One of these lists is "Did not download xxxxxxx".
Then, I built another program sending email one week later to people who did not download a specific document. The first smart campaign of this program is built that way :
SMART LIST : Added to List " Did not download xxxxxxx" (I tried with or without past activity constraint, same result).
FLOW : WAIT 1 week then SEND EMAIL xxxxxx .
I have 30 people on my list "Did not download xxxxx". When I set my first smart campaign, It will only target 10 people instead of 30.
Have you ever experienced the same issue ?
Thanks a lot for your input.
The other 20 people are not in the Blocked Leads List, and I see the 10 in the status tab of the smart campaign summary (basically the members of this smart campaign).
I'm not sure Added to List is needed here, why don't you use Member of List:
Then set this up as a Recurring Batch Campaign that can go at a set time when you want.
This should give you the same result assuming the list you are pointing constantly gets new members.
I changed precisely because I got the same issue using a Recurring Batch Campaign. The recurring Batch campaign was launched this morning, only half of the list' members received the email.
Added to List will trigger everytime someone is added that list, that's the experience I assume you want. When the Recurring Batch campaign went today, was 20 people in the blocked list then. Do you have communication limits setup, that will stop people getting the email too?
Nobody was in the Blocked list, and our communication limits setup is not the issue.
When I set up my recurring batch campaign (that was my first reflex, I guess it is the right one), do I have to target a static list or a smart list?
I am wondering if each recurring batch takes into account the new members of the list if it is static (if its populated dynamically) ?
This is how I would set it:
People will only be allows to run through the flow once so the recurring batch will allow you to list out to new members of the list at a set time and run them through the flow. So if you run this today, 30 people will get it, then if 5 new people get added this week to Did not download xxxxxxx then next time the batch run, 5 people will then get the communication and so on. Double checking you do have 30 people in your static list?
Another solution is to just use a negative filter, this would eliminate the need for the static list, this looks for people who didn't click a link on the Landing Page too: