Everything *looks* like it should work, and I’m not sure why the trigger isn’t already taking care of this, but in the filter, it may be possible that the ActiveCampaign list id is a number and not text.

I would add an “OR” condition in the filter and set it up as: 

• List ID is less than 38
  AND
• List ID is greater than 36

Hi ​@AJTTDK 

TIP: You should move your Filter step to be step 2.

You can check your Zap Runs history details to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/

This shows the Filter condition would have worked as expected because the yellow warning box indicates List ID 12 does not exactly match 37.

Hi there ​@AJTTDK!

Just wanted to check in to see how things are going with this—did David’s or Troy’s replies help to point you towards a solution?

Want to ensure this gets sorted so please let us know whether you need any further help at all. 

Looking forward to hearing from you! 

​@DavidLGS Thank you for the suggestion! I removed my text condition and just added this:

• List ID is less than 38
  AND
• List ID is greater than 36

A really good idea, but unfortunately that didn’t work. When I checked the data in the Zap history, I could see that it would let all unsubs pass because for some reason it was marking all the List IDs as 37 (even when they were not). For example, someone would unsub from a list with the ID 99, but in Zapier the data output would show that the List ID is 37. 

​@Troy Tessalone Thanks for the tip! I have already checked my data in/ out in the Zap history, but as I mentioned in my reply to David, there seems to be a problem with what Zapier outputs. 

The List IDs don’t match in that screenshot because that was a test record. There’s no way to get the actual latest unsub when testing for some reason, so by default the List ID when testing is always 12. Hope that makes sense. 

​@SamB Hi, thanks for the follow-up.

Unfortunately those solutions did not work. I came up with a band-aid solution, but that doesn’t work optimally either. Since Zapier couldn’t assign the correct List IDs, I decided to try using the Campaign ID instead. I used the Filter again with the following condition:

• Campaign ID is less than 483
  AND
• Campaign ID is greater than 481

Obviously this is not ideal, because I have to manually go in and add a new OR condition every time we send a new campaign - I have multiple of these unsub zaps for many different lists, so having to go into each one is quite time consuming. 

So far this solution does work sometimes, but I’ve noticed that it doesn’t work all the time. Even though all my unsub zaps are made exactly the same (with the exception of the Campaign ID), some of them will register the unsubs correctly, whilst others don’t register anything at all. Very confusing.

​@AJTTDK 

Post screenshots from Zap step 1 in the TEST tab, showing the DATA OUT for the List ID field you are using in the Filter step.

This is really strange ​@AJTTDK. That New Campaign Unsubscribe trigger shouldn’t be running on unsubscribes across all lists when a specific list is selected. And it definitely shouldn’t be showing all the lists as having an ID of 37 even when they are an unsubscribe for a list with a different ID number. So I suspect this could well be a bug you’re running into here.

In which case your best course of action here will be to reach out to our Support team to have them investigate this further—you can contact them here: https://zapier.com/app/get-help. 

I’m glad you were able to get a workaround by filtering out the different Campaign IDs for now at least. I’m not sure how long it will take for this to be resolved so if the Support team determine that it is a bug, then you might want to try a slightly different workaround for those Campaign IDs. Just thinking that if you have a large number of campaign IDs to be filtered out, or have multiple Zaps that need to filter out the same Campaign IDs, then it might be worth building a list in a Zapier Tables of all the campaign IDs that you’d want to filter out—suggesting Tables here as it would not count towards your task usage. Then, you could have a Find Record search action to look for the campaign ID in the table, and set up the filter to check whether it found one.

For example:

I made a quick table that just stores a list of different campaign IDs:

Then added a Find Record search action that checks the Campaign ID column across all the records in the table to see if there are any matches for the Campaign ID supplied by the New Campaign Unsubscribe trigger:

Here you can see that it found a match for that ID of 98:

The filter could then be set up to check that Zap Search Was Found Status field to see if it had a value of false—false means that it’s a campaign ID that isn’t in that Zapier Table, true would indicate that the ID is in the table:

And as you can see below, the filter would have correctly stopped the Zap from continuing as the campaign ID was found in the Zapier Table:

NOTE: If you want to only allow the Zap to continue for campaign IDs that are listed in the table then you’d just need to change the filter slightly so that it looks for a value of true instead of false, like so:

With this approach if you have multiple Zaps that need to filter out the same Campaign IDs you can just add the new Campaign IDs to the table instead of having to add new filter conditions across all the Zaps.

If you give that approach a try and get stuck at all just let us know. And please do keep us updated on how you get on with the Support team—curious to know whether it is indeed a bug or if there’s a different underlying issue! 

​@Troy Tessalone 

​@SamB Thank you for the suggestion! I was finally able to test this method today on a larger scale as we sent a newsletter and it worked!!! I really appreciate your help, it is a great workaround. 

I have written to support as you suggested - I will keep you posted when they respond :)

That’s awesome news, ​@AJTTDK! I’m so glad it was helpful  Thanks for doing that, I look forward to hearing your update on this!