Episode 8 breaks down how attorneys actually find and evaluate expert witnesses. Brian explains that lawyers commonly use expert directories like SEAK (and similar platforms) and also lean heavily on referrals from other attorneys. A simple move is to ask every new contact, “How did you find me?” so you can identify which channels are producing real inquiries and focus your efforts there.
A key theme is that your website is often the first credibility check. It should function like a clear, professional business card that quickly communicates your niche, what matters you will and will not take, and how to reach you. The hosts stress that attorneys working under deadlines want a direct phone number and email, not friction from a contact form. They also warn that website content can become evidence, so avoid salesy language, advocacy, or any claims you cannot defend under oath.
The episode closes with practical guidance on reputation building and marketing traps. Speaking at attorney conferences and relevant professional events can accelerate trust because lawyers can see how you communicate and think. LinkedIn is positioned as a verification layer rather than a primary lead engine, so keep it current and assume anything you post could be reviewed by both sides. Brian is skeptical of paid mailers, generic advertising, and unfocused content efforts, while noting that expert-witness training can help you learn the process and build a useful network.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked