網路追蹤
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
透過網路追蹤功能，您可以查看 Google Mobile Ads SDK 的相關網路活動，這有助於偵錯 Google 行動廣告的實作方式。
使用網路追蹤功能 (而非 Charles Proxy 等工具) 的主要原因是，這項功能適用於所有 iOS 版本和裝置，且不需要信任任何第三方安全憑證設定檔。但自 iOS 10.3 起，由於有憑證設定檔規定，因此 Proxy 工具不適用於這種情況。
本指南說明如何啟用網路追蹤功能，以利偵錯。
Enable tracing
如要啟用網路追蹤，請在 plist 檔案中將 GADEnableNetworkTracing 鍵設為 YES。
啟用網路追蹤功能後，Google Mobile Ads SDK 會將網路事件記錄到控制台中。然後在開發人員論壇上以私密回覆的形式，將記錄副本提供給我們的工程師進行分析。
記錄
系統會使用適合平台的標準控制台記錄，輸出網路記錄。
控制台記錄訊息一律以 GMA Debug BEGIN、GMA Debug CONTENT 或 GMA Debug FINISH 字串開頭，方便搜尋或篩除。每個網路記錄的第一則記錄訊息為 GMA Debug BEGIN，最後一則記錄訊息為 GMA Debug FINISH，網路記錄內容則以 GMA Debug CONTENT 開頭。如果網路記錄內容太長，無法放在一行，系統會將內容分成多行，每行開頭都是 GMA Debug CONTENT。
輸出範例
<Your App Name>[2710:30568] <Google> GMA Debug BEGIN
2017-12-06 09:47:09.268020-0800 <Your App Name>[2710:30568] <Google> GMA Debug CONTENT: {
"components" : [
"network_request_31107D12-E54E-45D6-AEA9-4A303C659EDF"
],
"timestamp" : 1512582429267.2629,
"event" : "onNetworkRequest",
"params" : {
"firstline" : {
"uri" : "<encoded text>",
"verb" : "<encoded text>"
},
"headers" : [
{
"name" : "<encoded text>",
"value" : "<encoded text>"
}
]
}
}
2017-12-06 09:47:09.275742-0800 <Your App Name>[2710:30568] <Google> GMA Debug FINISH
接著，您可以將記錄副本提供給我們的工程師進行分析。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-09-02 (世界標準時間)。
[null,null,["上次更新時間：2025-09-02 (世界標準時間)。"],[[["\u003cp\u003eNetwork tracing allows debugging of the Google Mobile Ads SDK by revealing network activities.\u003c/p\u003e\n"],["\u003cp\u003eIt works on all iOS versions and devices without needing third-party security certificate profiles, unlike proxying tools.\u003c/p\u003e\n"],["\u003cp\u003eTo enable, set the \u003ccode\u003eGADEnableNetworkTracing\u003c/code\u003e key to \u003ccode\u003eYES\u003c/code\u003e in your app's plist file.\u003c/p\u003e\n"],["\u003cp\u003eNetwork event logs are output to the console, starting with "GMA Debug BEGIN" and ending with "GMA Debug FINISH".\u003c/p\u003e\n"],["\u003cp\u003eShare the console logs with Google engineers for analysis to help with debugging.\u003c/p\u003e\n"]]],["Network tracing, used for debugging the Google Mobile Ads SDK, works on all iOS versions without needing third-party security certificates. To enable it, set `GADEnableNetworkTracing` to `YES` in your plist file. Network events are logged to the console, with messages starting with `GMA Debug BEGIN`, `GMA Debug CONTENT`, or `GMA Debug FINISH`. These logs can then be provided to engineers for analysis via the developer forum. Each network log includes content, timestamp, and event parameters.\n"],null,["Select platform: [Android](/admob/android/network-tracing \"View this page for the Android platform docs.\") [iOS](/admob/ios/network-tracing \"View this page for the iOS platform docs.\")\n\n\u003cbr /\u003e\n\nNetwork tracing lets you see network activities relating to the\nGoogle Mobile Ads SDK. This can be useful in debugging your Google Mobile Ads\nimplementation.\n\nA key reason to use network tracing instead of tools such as [Charles\nProxy](//www.charlesproxy.com) is that it will work on **all** iOS versions and\ndevices without trusting any third party security certificate profiles. This is\nnot the case with proxying tools due [certificate profile\nrequirements](https://support.apple.com/en-nz/HT204477) in place since iOS 10.3.\n\nThis guide explains how to enable network tracing for debugging purposes.\n\nEnable tracing\n\nTo enable network tracing, set the `GADEnableNetworkTracing` key to `YES` in\nyour plist file.\n\nWhen network tracing is enabled, the Google Mobile Ads SDK logs network events\nto the console. You can then provide copies of the logs to our engineers for\nanalysis as a private reply on the [developer\nforum](//groups.google.com/forum/#!forum/google-admob-ads-sdk).\n\nLogging\n\nStandard platform-appropriate console logs are used to output the network logs.\n\nConsole log messages always begin with the string `GMA Debug BEGIN`,\n`GMA Debug CONTENT`, or `GMA Debug FINISH` so that it can be searched for or\nfiltered out. For each network log, the first log message is `GMA Debug BEGIN`,\nthe last log message is `GMA Debug FINISH`, and the network log content begins\nwith `GMA Debug CONTENT`. If a network log content is too long to fit on a line,\nit is split among multiple lines, each line beginning with `GMA Debug CONTENT`.\n\nSample output \n\n \u003cYour App Name\u003e[2710:30568] \u003cGoogle\u003e GMA Debug BEGIN\n 2017-12-06 09:47:09.268020-0800 \u003cYour App Name\u003e[2710:30568] \u003cGoogle\u003e GMA Debug CONTENT: {\n \"components\" : [\n \"network_request_31107D12-E54E-45D6-AEA9-4A303C659EDF\"\n ],\n \"timestamp\" : 1512582429267.2629,\n \"event\" : \"onNetworkRequest\",\n \"params\" : {\n \"firstline\" : {\n \"uri\" : \"\u003cencoded text\u003e\",\n \"verb\" : \"\u003cencoded text\u003e\"\n },\n \"headers\" : [\n {\n \"name\" : \"\u003cencoded text\u003e\",\n \"value\" : \"\u003cencoded text\u003e\"\n }\n ]\n }\n }\n 2017-12-06 09:47:09.275742-0800 \u003cYour App Name\u003e[2710:30568] \u003cGoogle\u003e GMA Debug FINISH\n\nYou can then [provide copies of the logs to our\nengineers](//groups.google.com/forum/#!forum/google-admob-ads-sdk) for analysis."]]
