# CtwaMultiResponse
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**ad_type** | **AdType** | (enum: multi) |
**ads** | **Vec<serde_json::Value>** | The persisted Ad documents (one per creative), all sharing the same `platformCampaignId` and `platformAdSetId`. |
**platform_campaign_id** | **String** | |
**platform_ad_set_id** | **String** | |
**message** | **String** | |
**recovered_writes** | Option<[**Vec<models::MetaRecoveredWritesInner>**](MetaRecoveredWritesInner.md)> | Meta only, present only when needed. Every object this request did not get confirmed by its first POST: found by name after Meta lost or failed its answer (`adopted`), or created by a second POST after a Meta 5xx (`repostedAfter`). A re-POSTed object may have a twin from the first POST that Meta wrote late: check its parent for a duplicate name. Send `retryOnServerError: false` to never re-POST. | [optional]
**warnings** | Option<**Vec<String>**> | Present when Meta created the ad set differently from the request: - A multi-destination ad set (`destinations` including whatsapp) that Meta kept without the requested `whatsappPhoneNumber` in its promoted_object, which an existing ad set cannot change. A WhatsApp-only ad set returns no such warning, because every ad routes conversations by the number on its WhatsApp button. - The ad set joined a CBO campaign (`existingCampaignId`) whose own bid strategy applies, so a different `bidStrategy`, or a `roasAverageFloor` that strategy cannot take, was not applied. - An entry starting with `activation_failed:` when Meta refused the final switch to ACTIVE. Nothing was deleted; the entry names what was kept PAUSED and what was switched ACTIVE, and quotes Meta's error and the status calls that switch the PAUSED ones on later. | [optional]
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)