發佈日期:2024 年 1 月 23 日 | 有效期限:2026 年 5 月 21 日 | 網誌文章
適用於 v19.0。於 2024 年 4 月 22 日起適用於所有版本。
已停用以下群組 API 權限和功能:
您可以透過向端點(https://graph.facebook.com/v19.0/...
)發出版本 19 要求,驗證指定的群組 API 端點是否需要這些權限或功能之一。
此外,我們已停用群組管理員在群組中安裝應用程式的功能,即使他們在應用程式擁有管理員或開發人員角色也一樣。
上述權限和功能將於 2024 年 4 月 22 日移除。
請參閱 WhatsApp Flows 變更記錄。
發佈日期:2024 年 1 月 23 日 | 有效期限:2025 年 2 月 4 日 | 網誌文章
Applies to v19.0+.
age_targeting
, gender_targeting
, labels
, and location
insights metrics will no longer be available.estimated_ad_recall_rate_lower_bound
, estimated_ad_recall_rate_upper_bound
, estimated_ad_recallers_lower_bound
, and estimated_ad_recallers_upper_bound
insights metrics will no longer be available.The following endpoints are affected:
GET /{ad-set-id}/insights
GET /{ad-account-id}/insights
GET /{ad-id}/insights
GET /{campaign-id}/insights
POST /{ad-set-id}/insights
POST /{ad-account-id}/insights
POST /{ad-id}/insights
POST /{campaign-id}/insights
Applies to v19.0+.
When creating a copy of an ad you must only use Outcome-Driven Ad Experience objectives. Attempting to use legacy objectives will result in an error.
The following endpoints are affected:
Applies to v19.0+. Will apply to all versions on April 22, 2024.
targeting_optimization
field will not be accepted for campaigns that are optimized for link clicks or landing page views. This also applies to previous optimizations that were included in Advantage Detailed Targeting with no option to opt-out including conversions, value, app installs, app events and conversations.targeting_as_signal
field to either 1 or 3 based on the set of objectives and optimizations.targeting_as_signal
field should be either null or 0 for campaigns that are optimized for impressions, video views, reach, engagement, ad recall lift or lead, otherwise an error will be received.The following endpoints are affected: