AI-generated Key Takeaways
- 
          This document outlines the request message for the ReachPlanService.ListPlannableUserInterests method. 
- 
          The request requires a customer_idand optionally includes filters for user interest taxonomy types, application information, name, and path.
- 
          Supported user interest taxonomy types are AFFINITY and IN_MARKET. 
Request message for ReachPlanService.ListPlannableUserInterests.
| Fields | |
|---|---|
| 
 | 
 Required. The ID of the customer. | 
| 
 | Optional. A filter by user interest type. If set, only user interests with a type listed in the filter will be returned. If not set, user interests of all supported types will be returned. Supported user interest types are AFFINITY and IN_MARKET. Each type must be specified at most once. | 
| 
 | Optional. Additional information on the application issuing the request. | 
| 
 | 
 A filter by user interest name. If set, only user interests with a name containing the literal string (case insensitive) in the filter will be returned. Maximum length is 200 characters. | 
| 
 | 
 A filter by user interest path. If set, only user interests with a path containing the literal string (case insensitive) in the filter will be returned. Maximum length is 200 characters. |