docs/CustomerProfileIntegrationRequestV2.md in talon_one-2.5.1 vs docs/CustomerProfileIntegrationRequestV2.md in talon_one-3.0.0

@@ -2,19 +2,21 @@
 
 ## Properties
 
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**attributes** | [**Object**](.md) | Arbitrary properties associated with this item | [optional] 
+**attributes** | [**Object**](.md) | Arbitrary properties associated with this item. | [optional] 
+**evaluable_campaign_ids** | **Array<Integer>** | When using the `dry` query parameter, use this property to list the campaign to be evaluated by the Rule Engine.  These campaigns will be evaluated, even if they are disabled, allowing you to test specific campaigns before activating them.  | [optional] 
 **audiences_changes** | [**ProfileAudiencesChanges**](ProfileAudiencesChanges.md) |  | [optional] 
-**response_content** | **Array<String>** | Optional list of requested information to be present on the response related to the customer profile update.  Currently supported: \"customerProfile\", \"triggeredCampaigns\", \"loyalty\", \"event\", \"awardedGiveaways\", \"ruleFailureReasons\".  **Note:** `ruleFailureReasons` is always part of the response when the Application type is `sandbox`.  | [optional] 
+**response_content** | **Array<String>** | Extends the response with the chosen data entities. Use this property to get as much data as you need in one _Update customer profile_ request instead of sending extra requests to other endpoints.  | [optional] 
 
 ## Code Sample
 
 ```ruby
 require 'TalonOne'
 
 instance = TalonOne::CustomerProfileIntegrationRequestV2.new(attributes: {"Language":"english","ShippingCountry":"DE"},
+                                 evaluable_campaign_ids: [10, 12],
                                  audiences_changes: null,
                                  response_content: [triggeredCampaigns, customerProfile])
 ```