What do attorneys actually find when they run a background check on an expert witness — and what do experts find when they run one on themselves? In this episode, Dr. Brian Woodruff talks with Ashish Arun, founder and CEO of Exlytem and principal owner of Expert Witness Profiler, which has spent over a decade digging through court records to compile background intelligence on testifying experts.
Ashish walks through how a profiler report comes together — pulling every court document tied to an expert’s name, from rulings to briefs to docket entries — and shares some of the more surprising things experts have found about their own records, including undisclosed case designations and forgotten Daubert challenges. He makes the case that a denied Daubert challenge is actually a credibility asset worth publicizing, and offers concrete advice for experts who have been excluded: get the full record, diagnose the real cause, and be ready to explain it.
The conversation also covers how expert marketing has evolved — LinkedIn and directories are no longer taboo, as long as the language stays defensible — and closes with a look at how courts are starting to treat an expert’s AI prompts as discoverable methodology, not privileged work product. Ashish previews Exlytem’s upcoming Expert Atlas platform, built to catch inconsistencies like conflicting CV dates automatically.
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