一键在 Manus 中运行任何 Skill

troubleshoot-conversions

星标89

分支11

更新时间2026年6月10日 13:56

Investigates conversion upload issues and generates a structured diagnostic report based on Google Ads API conversion summaries and alerts.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

googleads

googleads/google-ads-api-developer-assistant

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Troubleshoot Conversions

This skill investigates conversion upload issues and generates a structured diagnostic report by executing the mandatory conversion troubleshooting workflow.

1. Execution Instructions [MANDATORY]

When invoked to troubleshoot conversions:

Locate the required customer_id (from context or customer_id.txt). If missing, prompt the user.
Execute the mandatory diagnostic collector script within the sequestered virtual environment. As it runs, it will output high-level client and action summaries to stdout to inform your analysis:

./.venv/bin/python3 .agents/skills/troubleshoot_conversions/scripts/troubleshoot_conversions.py --customer_id <customer_id> --api_version <api_version>

Note the consolidated troubleshooting report path returned by the script (e.g., saved/data/conversion_troubleshooting_report_<epoch>.txt).

2. Diagnostic Queries & Calculations

When analyzing conversion data directly:

Diagnostic Summaries: Query both offline_conversion_upload_client_summary and offline_conversion_upload_conversion_action_summary.
Attributes & Totals: Use successful_count and failed_count. Calculate daily total as successful_count + failed_count + pending_count (top-level total_event_count is only available on parent resources).
Alert Inspection: Access alerts (OfflineConversionAlert) at the top-level resource. Inspect alert.error oneof via WhichOneof("error_code") and report error_percentage. If summaries are empty, append exactly: Reason: No standard offline imports detected in last 90 days.

3. Pre-Upload CSV Validation

Before uploading any conversion CSV data file, execute the programmatic validation utility to statically check formatting and timestamp rules:

./.venv/bin/python3 .agents/skills/troubleshoot_conversions/scripts/validate_conversion_upload.py --csv_path <path_to_csv> --api_version <api_version>

同仓库更多 Skills

同仓库

explain

googleads/google-ads-api-developer-assistant

Explains Google Ads API concepts, code snippets, or queries in plain English using real-world analogies.

2026-06-1089

get-extension-version

googleads/google-ads-api-developer-assistant

Extracts the version from agent.json and makes it available during the session.

2026-06-1089

get-cids-under-mcc

googleads/google-ads-api-developer-assistant

Retrieves a list of all child customer account IDs (CIDs) under a given Manager Account (MCC).

2026-06-1089

inspect-object

googleads/google-ads-api-developer-assistant

Inspects any Google Ads API Protobuf resource, nested message or Enum structure.

2026-06-1089

pmax-listing-filter

googleads/google-ads-api-developer-assistant

Configures Asset Group URL expansion filters (listing group webpage exclusions) for Performance Max campaigns.

2026-06-1089

step-by-step

googleads/google-ads-api-developer-assistant

Presents a response as a step-by-step process for the user to follow.

2026-06-1089

name	troubleshoot-conversions
description	Investigates conversion upload issues and generates a structured diagnostic report based on Google Ads API conversion summaries and alerts.

Troubleshoot Conversions

This skill investigates conversion upload issues and generates a structured diagnostic report by executing the mandatory conversion troubleshooting workflow.

1. Execution Instructions [MANDATORY]

When invoked to troubleshoot conversions:

Locate the required customer_id (from context or customer_id.txt). If missing, prompt the user.
Execute the mandatory diagnostic collector script within the sequestered virtual environment. As it runs, it will output high-level client and action summaries to stdout to inform your analysis:

./.venv/bin/python3 .agents/skills/troubleshoot_conversions/scripts/troubleshoot_conversions.py --customer_id <customer_id> --api_version <api_version>

Note the consolidated troubleshooting report path returned by the script (e.g., saved/data/conversion_troubleshooting_report_<epoch>.txt).

2. Diagnostic Queries & Calculations

When analyzing conversion data directly:

Diagnostic Summaries: Query both offline_conversion_upload_client_summary and offline_conversion_upload_conversion_action_summary.
Attributes & Totals: Use successful_count and failed_count. Calculate daily total as successful_count + failed_count + pending_count (top-level total_event_count is only available on parent resources).
Alert Inspection: Access alerts (OfflineConversionAlert) at the top-level resource. Inspect alert.error oneof via WhichOneof("error_code") and report error_percentage. If summaries are empty, append exactly: Reason: No standard offline imports detected in last 90 days.

3. Pre-Upload CSV Validation

Before uploading any conversion CSV data file, execute the programmatic validation utility to statically check formatting and timestamp rules:

./.venv/bin/python3 .agents/skills/troubleshoot_conversions/scripts/validate_conversion_upload.py --csv_path <path_to_csv> --api_version <api_version>