Troubleshooting
If you run into problems while using the Search Ads 360 API, take a look through this
troubleshooting section.
If there's a problem that you can't solve after reading the resources on this site,
contact support and have the
following information ready:
Search Ads 360 Agency ID and Advertiser ID you are trying to access
Project Number from Google API Console
The username of the Google Account that you’re using to access the API.
This is the account that has been given
permission to access Search Ads 360, which is the same account you use to
set up authorization.
Code snippet of your request
JSON response
If the response is an error, be sure to include the error message, not just the
numeric error code.
Authorization errors
Here are some commonly encountered authorization errors:
| Message |
Description |
Access Not Configured. Please use Google API Console to activate the API for your project.
|
This error occurs if you haven't enabled the Search Ads 360 API for your account. Make sure you've done the following:
Go to the Google API Console.
Select your project. If you haven't created a project yet, see
Create a project for your client. In the sidebar on the left, expand APIs & auth. Next,
click APIs. In the
list of APIs, make sure the status is ON for the Search Ads 360 API.
|
Invalid grant
|
This error occurs when your refresh token isn't valid. You can obtain a refresh token
by invoking the Search Ads 360 utility
script as follows:
sa360Api.py --login
Learn more about the
recommended workflow for authorization.
|
Invalid client
no application name
|
This error occurs if you haven't specified a product name when setting up your
project in the Google API Console. To fix this error,
enter the name of
your product on the Consent screen of the Google API Console.
|
Other types of authorization errors |
Make sure to use a Google Account
that has been granted access to Search Ads 360 when you sign in to the Google API Console
to retrieve your client ID and client secret, and when you obtain a refresh token.
|
Conversion upload errors
The following table lists the errors you may encounter when uploading conversions. Note that the
hexadecimal error codes are immutable, so you can use them in your own scripts to identify errors.
| Error code |
Message |
Description |
0x00000101 |
Click ID '{ID}' is not found
|
The
click id you specified in an
update request is not valid. Reupload conversions after you've done the
following:
Verified that the click ID was generated 6 hours before conversions were uploaded. Activated
the API conversion service. If you're
attributing conversions to specific visits, wait at least 6 hours after
the visit before you upload the conversion. Search Ads 360 might not recognize the visit's clickID if
you upload sooner than 6 hours after the visit. In rare instances, you might need to
wait up to 24 hours before Search Ads 360 could recognize the clickId. Confirmed that the click is from a valid source as
indicated
by the gclsrc parameter. Confirmed that you've specified the correct advertiser in the
advertiserId column. Verified your click ID was generated within the last 90 days.
|
0x0000010E |
Floodlight activity name '{name}' is not found |
The name of the Floodlight activity specified in the
segmentationName
column is incorrect or not yet available. If you see this error, check for
the following common problems:
- Names are case-sensitive, so make sure your request matched the case exactly.
- Make sure you didn't include any unprintable Unicode character or double spaces in
the Floodlight activity name.
- Make sure you specified the name of a
Floodlight activity, not a
Floodlight column.
- Check that the Floodlight activity exists for the advertiser you specified in the
advertiserId column. (It's possible you specified the wrong advertiser.)
- After you create or edit a Floodlight activity, wait a couple of hours before uploading
conversions for the activity.
|
0x00000115 |
Custom dimension '{name}' is not found |
Make sure the custom Floodlight variable you specified has been
set up as a
dimension (not a metric) for the advertiser associated with the
clickId,
criterionId,
or productGroupId
you're attributing for the conversion.
|
0x00000116 |
Custom metric '{name}' is not found |
Make sure the custom Floodlight variable you specified has been
set up as a
metric (not a dimension) for the advertiser associated with the
clickId,
criterionId,
or productGroupId
you're attributing for the conversion.
|
0x0000011A |
The advertiser conversion ID is already specified for a conversion with Search Ads 360
conversion ID {ID} |
Someone has already uploaded a conversion for the same scope and advertiser conversion
ID specified in the
conversionId column.
The "advertiser conversion ID" is an ID you generate. Search Ads 360 requires this ID to be unique
for a given scope. The
Search Ads 360 conversion ID is generated by Search Ads 360 and is guaranteed to be unique.
|
0x0000011B |
Advertiser conversion ID '{ID}' is not found |
Your
update request tried to update an advertiser conversion ID that doesn't
exist. Make sure you specified the right ID. |
0x0000011D |
User does not have permission to view advertiser {advertiser ID} |
The Google Account your client is using doesn't have permission to view the advertiser
specified in the request.
When you sign in to the Google API Console to retrieve your client ID and client
secret, and when you obtain a refresh token, make sure to use a Google Account that has
been granted access to the
advertiser you specified.
|
0x0000011F |
Advertiser conversion ID is already specified in this request |
Two or more conversions in the request specify the same scope and
advertiser conversion ID.
The advertiser conversion ID is an ID you generate and specify in the
conversionId column. Search Ads 360 requires this ID to be unique for a given scope.
|
0x0000011E |
The requested Floodlight activity '{name}' does not match the conversion type (ACTION/TRANSACTION) |
The Floodlight activity ID or name that you've provided doesn't match the conversion type you've specified.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-12-16 UTC.
[null,null,["Last updated 2024-12-16 UTC."],[[["This page provides troubleshooting information for common issues encountered while using the Search Ads 360 API, including authorization and conversion upload errors."],["If the provided resources don't resolve your issue, contact support with specific information about your problem, including your Search Ads 360 and Google API Console credentials, code snippets, and JSON responses."],["The page lists common authorization errors such as `Access Not Configured`, `Invalid grant`, and `Invalid client`, with explanations and solutions."],["It also includes a table of conversion upload errors, detailing their hexadecimal error codes, descriptions, and troubleshooting steps."],["For report discrepancies, refer to the Response Codes and Standard Error Responses documentation and ensure the `includeRemovedEntities` setting in your request matches the \"Show removed\" checkbox selection in the Search Ads 360 UI."]]],["When troubleshooting the Search Ads 360 API, consult the provided resources. If issues persist, contact support, providing your Agency/Advertiser ID, Project Number, API access username, code snippet, and JSON response (including full error messages). Common authorization errors include `Access Not Configured`, `Invalid grant`, and `Invalid client`, often resolved by enabling the API, refreshing tokens, or naming your project. Conversion upload errors relate to invalid click IDs, Floodlight activity names, or custom dimensions/metrics. Ensure correct permissions and data consistency between UI and API.\n"]]
