AI-generated Key Takeaways
- 
          The CustomTargetingErrorin the Ad Manager API (v202508) signifies issues withCustomTargetingKeyandCustomTargetingValueobjects and inherits standard error fields likefieldPathandtriggerfromApiError.
- 
          CustomTargetingKeyerrors can occur due to issues such as the key not being found, exceeding count limits, duplicate or invalid names, incorrect status, missing values, or improper usage.
- 
          CustomTargetingValueerrors arise from problems like the value not being found, exceeding count limits for a key, duplicate or invalid names, invalid length or characters, incorrect match types, incorrect status, or improper usage.
- 
          Additional CustomTargetingErrorreasons include invalid targeting expressions, issues with targeting audience segments, and errors related to mapped metadata or unknown causes.
Lists all errors related to CustomTargetingKey and CustomTargetingValue objects.
- Namespace
- 
               https://www.google.com/apis/ads/publisher/v202508
| Field | |
|---|---|
| ApiError(inherited) | |
| 
                            | 
                            The OGNL field path to identify cause of error. | 
| 
                            | A parsed copy of the field path. For example, the field path "operations[1].operand" corresponds to this list: {FieldPathElement(field = "operations", index = 1), FieldPathElement(field = "operand", index = null)}. | 
| 
                            | 
                            The data that caused the error. | 
| 
                            | 
                            A simple string representation of the error and reason. | 
| CustomTargetingError | |
| 
                            | 
 Enumerations 
 |