Caution: You are viewing documentation for the API's REST interface. Most of our official client libraries use gRPC. See the REST Introduction for details.
Required. The data type for the customizer value. It must match the attribute type. The stringValue content must match the constraints associated with the type.
stringValue
string
Required. Value to insert in creative text. Customizer values of all types are stored as string to make formatting unambiguous.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-06 UTC."],[[["CustomizerValue is used within entities like CustomerCustomizer and CampaignCustomizer to manage customizer values."],["It's represented in JSON format with a required \"type\" field specifying the data type and a required \"stringValue\" field containing the actual value."],["All customizer values, regardless of their actual data type, are stored as strings in the \"stringValue\" field for consistency."],["The \"type\" field must correspond to a valid CustomizerAttributeType, ensuring data integrity and compatibility."],["The content of the \"stringValue\" field should adhere to any constraints associated with the specified data type in the \"type\" field."]]],["The content defines the structure and components of a customizer value, used in linkage entities like CustomerCustomizer. It's represented in JSON with two key fields: `type` and `stringValue`. `type` specifies the data type, which must match the attribute type, while `stringValue` holds the actual value as a string, irrespective of the data type for formatting. Both fields are required for defining the customizer value.\n"]]
