Marketing List Membership and Campaign Frequency Caps in the Authgnosis CRM

Published October 26, 2026Updated October 27, 2026

Each contact in the Authgnosis CRM now shows whether it is on a marketing list, and a campaign's frequency cap is copied onto each new campaign activity under it. A Yes/No field on each contact shows whether it is a member of any marketing list. A server plugin updates it on every way a contact […]

In this series · Part 29 of 34

1Dynamics 365 CRM: API integration + change-control repo 2Dynamics 365 CRM: Last Contact Engagement tracking on Accounts 3Turning a sales-intelligence export into a clean CRM data model 4Dynamics 365 CRM: contacts inherit their company’s website, and emails timestamp by send time 5Your SEO health now lives as a dashboard inside the CRM 6Contact form duplicate detection now reads the request, not just the address 7Marketing list members now show engagement and account fit 8Campaign responses now create leads behind a confirmation step 9Three CRM automations passed their tests without running the code that had just changed 10A signature defect that three mailboxes agreed was not there 11Asking whether a partner is involved, instead of inferring it 12Choosing what runs the AI layer in the CRM sales process 13A read-only CRM endpoint for scoring outside the desktop 14Why a corrected email signature kept sending the old one 15Two local dependencies, and only one was obvious 16Filing a generated document to the record automatically 17The rehearsal that guards every process change had been failing silently 18An email step in the sales process can now be excused, not only sent 19A one to one email from a lead left the engagement record blank 20One meeting that served two process steps, recorded as two 21A setting that stored correctly, read back correctly, and was never in force 22Generating a product catalogue from one canonical file 23Three date fields that existed on every row, and had never once been written 24Unused, unreferenced, and still not safe to delete 25A measure that could not record early 26A sales automation that runs as itself, not as an administrator 27A stage change that was refused, and reported as a success 28An Email Validation Gate for Campaign Sends in the Authgnosis CRM 29Marketing List Membership and Campaign Frequency Caps in the Authgnosis CRM 30A Send Guardrail for Unsubscribe Links in the Authgnosis CRM 31Automated Bounce Handling for Campaign Email 32Nurturing Cadence Automation and an Email Send Gate in the Authgnosis CRM 33A Hard Stop on Calendar Invites from AI Agents in the CRM 34Bounced Campaign Email Now Updates the CRM on Its Own

On this page

Free Revenue Lifecycle Assessment

Connect with Marissa Wright to receive a free Revenue Lifecycle Assessment Report on your own business.

Book a consult →

Each contact in the Authgnosis CRM now shows whether it is on a marketing list, and a campaign's frequency cap is copied onto each new campaign activity under it.

A Yes/No field on each contact shows whether it is a member of any marketing list. A server plugin updates it on every way a contact joins or leaves a list, including the list's own contact grid, which the platform handles without firing the usual membership events.
Deleting a list removes its members before the usual save step runs, so the plugin recalculates one stage earlier and leaves the deleted list out. Both behaviours were found by walking every path on test lists.
A Frequency Cap (days) field on the campaign is copied onto each new campaign activity created with no cap, so the cap is set once per campaign instead of once per activity. A cap set on the activity itself is kept.
Email validation gained a source for addresses already reached by a one-to-one email, which count as checked without a separate verification run.