tracking_googleads_feedback_run
Manually run one conversion-feedback upload pass for the current product now (uploads newly-attributed conversions across all enabled rules since the last run).
Manually run one conversion-feedback upload pass for the current product now (uploads newly-attributed conversions across all enabled rules since the last run). Useful for testing; the daily cron runs this automatically.
Behavior
- HTTP
POST /tracking/googleads/feedback/run
Arguments
No arguments.
Response
Field | Type | Always | Description |
|---|---|---|---|
runId | string | • | This one upload pass. Match the completion event back to this step on it, not on productId: the daily cron pass and a manual run on the same day are two passes of the same product. |
failed | number | • | Rows Google rejected in this pass. |
matched | number | • | Of those, the ones that had a usable click id and a value, so a payload was actually built for them. |
noGclid | number | • | Conversions dropped because no Google click could be tied to the person. A high count here is a tagging problem, not a Google one. |
skipped | string | — | Present only when the pass did no work, and says why: feedback is switched off, no rule is enabled, or no Google Ads account is connected. Absent on a pass that ran. |
selected | number | • | Conversions in the lookback window that an enabled rule applied to. |
uploaded | number | • | Rows Google accepted in this pass. |
productId | string | • | The tenant whose conversions this pass uploaded. |
zeroValue | number | • | Conversions held back because their money value had not landed yet. They are retried on a later pass. |
partialFailureError | string | — | Google's own rejection detail, passed through unchanged, when it refused part of the batch. Absent when it accepted everything. |
Try it
Manually run one conversion-feedback upload pass for the current product now (uploads newly-attributed conversions across all enabled rules since the last run).