Feature Requests

Got an idea for a new feature or integration? We’d love to hear it! You can find our roadmap here.

1 vote

If ActiveCampaign "no contact found" do not delete User tags

Recently ActiveCampaign had a misconfiguration on their end with Cloudflare resulting in a 511 Network Authentication error between WPFusion and ActiveCampaign. (This is not an outage of the type their system status would display or alert about it, since it was specific to their Cloudflare setup.) With “Sync tags on User Login” enabled, the (false) “No contact found” results from ActiveCampaign caused WPFusion to delete all tags from the User’s WordPress profile. Since our site uses these ActiveCampaign tags for Menu Access and Content Access on our Membership site, the 50+ users who logged in from the time ActiveCampaign’s misconfiguration began until the time our admin disabled WPFusion sync on login were very confused! Once the issue was identified I was able to disable sync on login while waiting on ActiveCampaign to fix the issue, but would like to request as a feature: >> A checkbox that would allow sites to choose NOT to have user tags deleted IF ActiveCampaign returns “no contact found” to prevent tag changes resulting from temporary ActiveCampaign outages, API connection issues, or in this case, not an outage but an authentication/firewall issue on their end.

Completed Category: Core Feature Enhancements Bryan Griffin shared this idea Updated: December 30, 2025

2 thoughts on “If ActiveCampaign "no contact found" do not delete User tags”

  1. I see what happened there…

    We check for various ActiveCampaign error codes and if one is found, it’s treated as an API error and the contact’s ID and tags are left alone.

    But we didn’t have anything in place to handle a 511 error, or any unexpected response that didn’t contain a contact. In those cases it acted like the contact was deleted, and removed their cached tags.

    We have an update coming out for later today… what I’ve done is made it so that if *any* unexpected response comes back from AC (i.e. it’s not structured like the usual response for that endpoint), we’ll treat it as an “Unknown error” as a fallback, even if we haven’t seen that error before.

    That will prevent this from happening again ✅

Leave a Comment

Your email address will not be published. Required fields are marked *