AI-generated Key Takeaways
-
This document describes possible errors that can occur with conversion actions, including issues with duplicate names or app IDs, conflicts between different types of conversion tracking for the same app download, and problems related to setting data-driven or rule-based attribution models.
-
Errors can also arise from unsupported creation or update operations for specific conversion action types within the Google Ads API.
Enum describing possible conversion action errors.
Enums | |
---|---|
|
Enum unspecified. |
|
The received error code is not known in this version. |
|
The specified conversion action name already exists. |
|
Another conversion action with the specified app id already exists. |
|
Android first open action conflicts with Google play codeless download action tracking the same app. |
|
Android first open action conflicts with Google play codeless download action tracking the same app. |
|
The attribution model cannot be set to DATA_DRIVEN because a data-driven model has never been generated. |
|
The attribution model cannot be set to DATA_DRIVEN because the data-driven model is expired. |
|
The attribution model cannot be set to DATA_DRIVEN because the data-driven model is stale. |
|
The attribution model cannot be set to DATA_DRIVEN because the data-driven model is unavailable or the conversion action was newly added. |
|
Creation of this conversion action type isn't supported by Google Ads API. |
|
Update of this conversion action isn't supported by Google Ads API. |
|
Rule-based attribution models are deprecated and not allowed to be set by conversion action. |