Latest / Found, Trusted, Booked / How an RIA Connects Its CRM to Its Content System
Transcript
- Your content system and your CRM are separated by a compliance wall. You see which pages bring inquiries, but never learn whether those inquiries turn into clients. Here's why that happens, and how an RIA can build a loop that connects them without crossing the line. In my latest piece, I wrote about how a registered investment adviser, or RIA, can link content, compliance review, and the customer relationship management system—the CRM—so that each new client traces back to the pages that helped. The trick is that the CRM records an identifier, not the person's data. The content team sees counts, not names. The loop has three parts. Your content system assigns an identifier to every published piece when it's created. That identifier stays the same even if you revise the piece later. Then the review gate—the compliance approval step that already exists under the SEC, or Securities and Exchange Commission, Marketing Rule—adds one new field to its approval record: that identifier. Now the approved version, the reviewer, the date, and the live web address all point to the same identifier. Finally, your CRM gets two new fields on each contact. One holds the identifier of the first page the person engaged with. The other holds the identifier of the page they were on when they submitted a form. Both fill in automatically. Why does this matter? Because right now, the gap between content and client records is a data problem and a compliance problem rolled into one. An owned media plan often ends at the booking. The firm publishes, the page ranks, a form submission arrives. After that, the trail goes cold. The advisor books a meeting. The meeting becomes an engagement or it doesn't. Nobody connects that outcome to the page that started it. So the content team keeps guessing about which topics matter, and the sales process has no view of which pages prepare a reader well. The loop is narrow by design. The CRM stores the source of the contact and which pages they touched. It does not store what the person read in detail or any financial information they typed into a form. The content team receives aggregated counts by identifier and stage—inquiry, meeting held, engagement signed—not access to the CRM itself. Small counts are suppressed so no single person can be inferred. Client comments in CRM notes do not flow back into content. An adviser that uses testimonials in an advertisement has to put them through the review gate just like any other piece. Take a worked example. Dana is a composite, an invented advisor, not a client of ours. The firm publishes a guide for business owners planning a sale and a page about how it onboards new clients. Each piece has an identifier in the content system. When a visitor fills in a request form, a hidden field copies the identifier and the UTM source—that stands for Urchin Tracking Module, a tag added to a web address—into the form submission. The CRM creates a contact with those two values attached. Each quarter, Dana's operations lead runs a report grouped by identifier and counts how many contacts reached each stage. Suppose the sale-planning guide drew many inquiries but few meetings. Suppose the onboarding page drew fewer inquiries and a larger share became meetings. That pattern would suggest a decision. The firm could revise the guide to explain its process more clearly, or point readers toward the onboarding page. After a few quarters of data, the content team can make three kinds of decisions. Revise a piece that draws many inquiries but few meetings, because the mismatch often means the page set the wrong expectation. Extend a topic where meetings held are strong, with a related guide that goes through the review gate. Retire or merge pages that draw neither inquiries nor engaged clients, so the site carries fewer and clearer pages. Each change gets a new approval record under the same identifier, so the history stays intact and the next report compares like with like. One real warning: attribution is never complete. Many prospects read a page and then call the office. Referrals from existing clients and other professionals often arrive with no content touch at all. Visitors who decline tracking cookies won't carry a first-touch identifier. The form-page identifier still works because it comes from the form itself. And the "how did you hear about us" field is self-reported. So the loop gives a directional view. Use it to compare pieces against each other, not to assign exact credit. So: the compliance wall stays in place, but the content and client records now speak to each other. Read the full article linked in the show notes. This episode was produced by the ChoiceDigital™ Engine — reviewed for accuracy, editorial quality, and compliance, then approved by Dr. Adrian McMillian, whose voice you have been hearing as an AI-generated replica.