弃用时间表
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
通常情况下，系统会提供三种受支持的 Campaign Manager 360 API 版本
。每当发布新版本时，
先前版本。弃用日期过后，相应版本便会被视为“已弃用”
。
大多数版本的弃用期约为 7 个月。
虽然“已弃用”版本在预定的停用日期之前仍可使用，
我们建议用户利用弃用期迁移到较新的
版本。弃用日期之后，将不再提供已弃用的版本。
<ph type="x-smartling-placeholder">
</ph>
停用某个版本后会出现什么情况？
停用某个版本后，系统会拒绝所有收到的请求并返回 HTTP 403: Forbidden 错误响应。这些错误还伴随着一条消息，提醒用户该版本不再受支持：
{
"error": {
"errors": [
{
"domain": "global",
"reason": "forbidden",
"message": "3140 : Version v2.x of the DCM/DFA Trafficking and Reporting API is no longer supported. Please upgrade to the latest version of the API."
}
],
"code": 403,
"message": "3140 : Version v2.x of the DCM/DFA Trafficking and Reporting API is no longer supported. Please upgrade to the latest version of the API."
}
}
一段时间后，该版本会完全停用，无法访问。届时，针对该版本的所有请求都会收到常规的 HTTP 404: Not Found 错误响应。
提供了当前宣布的弃用日期和停用日期的时间表
如下：
| API 版本 |
下架日期 |
停用日期 |
| v3.5 |
2022 年 6 月 15 日 |
2023 年 5 月 1 日 |
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-31。
[null,null,["最后更新时间 (UTC)：2025-08-31。"],[[["\u003cp\u003eCampaign Manager 360 API typically supports three versions concurrently, with older versions being deprecated and eventually sunsetted.\u003c/p\u003e\n"],["\u003cp\u003eDeprecated API versions are announced with a sunset date, offering a 7-month deprecation period for users to migrate to newer versions.\u003c/p\u003e\n"],["\u003cp\u003eAfter the sunset date, requests to deprecated versions will result in errors, initially an HTTP 403 Forbidden error and later an HTTP 404 Not Found error.\u003c/p\u003e\n"],["\u003cp\u003eVersion v3.5 of the Campaign Manager 360 API was deprecated on June 15, 2022 and sunset on May 1, 2023.\u003c/p\u003e\n"]]],[],null,["# Deprecation Schedule\n\nThere will generally be three supported versions of the Campaign Manager 360 API at any\ngiven time. When a new version is released, a sunset date is announced for the\nprevious version. A version is considered deprecated once a sunset date has been\nannounced for it.\n\nThe deprecation period for most versions will be approximately 7 months.\nWhile deprecated versions remain available until the scheduled sunset date,\nusers are encouraged to use the deprecation period to migrate to a newer\nversion. After the sunset date, deprecated versions will no longer be available.\nWhat happens when a version sunsets?\n\nWhen a version is sunset all incoming requests are rejected with an `HTTP 403: Forbidden` error response. These errors are accompanied by a message alerting users that the version is no longer supported: \n\n```text\n{\n \"error\": {\n \"errors\": [\n {\n \"domain\": \"global\",\n \"reason\": \"forbidden\",\n \"message\": \"3140 : Version v2.x of the DCM/DFA Trafficking and Reporting API is no longer supported. Please upgrade to the latest version of the API.\"\n }\n ],\n \"code\": 403,\n \"message\": \"3140 : Version v2.x of the DCM/DFA Trafficking and Reporting API is no longer supported. Please upgrade to the latest version of the API.\"\n }\n}\n \n```\n\nAfter some time, the version is fully deactivated and becomes unreachable. At that point, all requests against the version receive a generic `HTTP 404: Not Found` error response.\n\n*** ** * ** ***\n\nA schedule of the currently announced deprecation and sunset dates is provided\nbelow:\n\n| API Version | Deprecation Date | Sunset Date |\n|-------------|------------------|--------------|\n| v3.5 | Jun 15, 2022 | May 01, 2023 |"]]
