Koleksiyonlar ile düzeninizi koruyun
İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın.
Google Ads komut dosyaları, mümkün olduğunca iyi şekilde yürütülür: Google Ads verilerinde değişiklik yapmaya çalışır ancak belirli bir değişiklik başarılı olmazsa komut dosyası bunu Değişiklikler günlüğü'ne kaydeder ve yürütmeye devam eder:
// Attempt an invalid change.letamount=999999999999;campaign.getBudget().setAmount(amount);// Error is logged into Changes log, but the script keeps running.// Suppose we must know whether the change actually happened.if(campaign.getBudget()!=amount){// The current value of budget is not the one we expected.// The change must have failed.}
Benzer hatalar veren işlemler şunlardır:
Anahtar kelime teklifini kampanya bütçesinden daha yüksek belirleme
Kampanya adını, zaten var olan bir ad olarak ayarlama.
Reklam grubu kotasına ulaşmış bir kampanyada reklam grubu oluşturma.
Bu kodla, tarih aralığı belirtilmediğinden komut dosyası anlamlı bir keywords yineleyici oluşturamaz. Bu nedenle, komut dosyası yürütme işlemi durur ve metin günlüklerine bir hata mesajı kaydedilir.
Kotalar aşılırsa komut dosyası tarafından uyarılar kaydedilir. Komut dosyası yürütülmeye devam eder ancak uyarıları her zaman incelemeniz gerekir.
Yürütme günlüklerinde hatalar kırmızı, uyarılar ise turuncu renkte gösterilir. Ayrıca, sorun giderme ve izleme amacıyla bu günlüklerde özel mesajlar da oluşturabilirsiniz.
[null,null,["Son güncelleme tarihi: 2025-09-05 UTC."],[[["\u003cp\u003eGoogle Ads scripts will log errors when changes fail but continue running, allowing you to check if a change was successful and handle it accordingly.\u003c/p\u003e\n"],["\u003cp\u003eCertain errors, such as missing required parameters, will halt script execution and require fixing before the script can run.\u003c/p\u003e\n"],["\u003cp\u003eWhile scripts proceed even when exceeding quotas, warnings are logged and should be reviewed.\u003c/p\u003e\n"],["\u003cp\u003eScript execution logs provide valuable information through errors (red), warnings (orange), and custom messages for debugging and monitoring.\u003c/p\u003e\n"],["\u003cp\u003eSuccessfully returned objects from Google Ads scripts are safe to use, indicating the operation was successful.\u003c/p\u003e\n"]]],[],null,["# Errors and Warnings\n\nGoogle Ads scripts execute in best-effort fashion: They attempt to make changes\nto Google Ads data, but if a certain change is not successful, the script\nrecords it into the [Changes log](/google-ads/scripts/docs/concepts/execution-logs)\nand proceeds with the execution: \n\n // Attempt an invalid change.\n let amount = 999999999999;\n campaign.getBudget().setAmount(amount);\n // Error is logged into Changes log, but the script keeps running.\n\n // Suppose we must know whether the change actually happened.\n if (campaign.getBudget() != amount) {\n // The current value of budget is not the one we expected.\n // The change must have failed.\n }\n\nOperations that output similar errors include:\n\n- Setting a keyword bid larger than the campaign budget.\n- Setting a campaign name to one that already exists.\n- Creating an ad group in a campaign that has already reached its quota for ad groups.\n\nSome errors, however, cannot be ignored. Here is an example: \n\n let keywords = AdsApp.keywords()\n .withCondition(\"metrics.clicks \u003e 10\")\n // Forgot forDateRange().\n .get();\n\nWith this code, the script cannot produce a meaningful `keywords` iterator\nsince the date range is not specified. Thus the script execution will halt, and\nan error message logged to the text logs.\n| **Key Point:** When Google Ads scripts successfully returns an object, it is safe to work with. An error would occur if fetching of an object failed.\n\nWarnings are logged by the script if\n[quotas](/google-ads/scripts/docs/limits) are exceeded. The script\nexecution will still proceed, but you should always review warnings.\n\nErrors are red and warnings are orange in execution logs. You can also\n[output custom messages](/google-ads/scripts/docs/concepts/execution-logs)\nto these logs for troubleshooting and monitoring purposes."]]
