Skip to main content

I'm currently working on a zap that tracks meta ad leads converted into purchases via Klaviyo and Shopify. I understand I can filter in a second step to stop the zap from firing on a purchase that doesn’t qualify as a lead, but it still counts towards our monthly zap allowance. We have a large quantity of purchases in general and a much smaller number of purchases that come from leads, so it will get very expensive quickly for non-proportional return.

Is there a way to prevent triggering a huge number of zaps and driving up our costs?

Thank you

Hi ​@dlewis 

Help links for understanding Task usage in Zap Runs: https://help.zapier.com/hc/en-us/articles/8496196837261-How-is-task-usage-measured-in-Zapier

 

Help links for understanding which native Zap apps count as 0 Tasks in Zap Runs: 

 


Hi there ​@dlewis 👋

Did the help guides Troy shared some links to help to point you in the right direction?

If not, I’m pleased to share that if your Zap is triggered but a Filter (as the 2nd step) prevents the Zap from continuing, then 0 tasks would be used for that run of the Zap. This is because both triggers and Filter actions do not count towards your task usage. 😁

Happy to help see if there are any ways you can reduce task usage for the Zap runs that do pass the filter. Just send over some screenshots of the Zap’s setup so we can see exactly what actions it’s using to be able to make some recommendations. Remember to use a tool like Zappy to remove any personal info like names, emails etc. before sharing as this is a public space.

Looking forward to hearing from you!