Skip to main content

Enhanced Scripts - Troubleshooting

Written by Geetanjali Tyagi

Preliminary Checks to Detect the Reason for Errors in Scripts

  1. Check if the Script has been Copied Correctly into Google Ads:

    • Ensure that the entire contents of the file you downloaded from Optmyzr are placed in the Google Ads Script, replacing the existing content. Your Google Ads Script should be identical to the code you downloaded from us.

  2. Verify Script Values (For Non-Enhanced Scripts™):

    • Check if all values that needed replacement in the script (such as campaign name, date ranges, etc.) have been replaced correctly.

Error When Creating Labels

  • Preview Mode Limitation:

    • If the script creates labels, you might encounter an error in preview mode. This occurs because Google Ads doesn't allow label creation in preview mode. When you run the script, it should work fine.

If Everything Looks Right but You're Still Seeing an Error

Collect and Send Details to Support:

  • Send an email to support@optmyzr.com with the following details:

    • Name of the script.

    • The exact error message you see (you can attach a screenshot of the error message).

    • A copy of the script code you are using in your Google Ads account.

    • A copy of the most recent script logs, which you can obtain by following these instructions:

      1. Click on the "log statements" for the relevant script under the Results column.

      2. Copy the entire log content located under "History."

      3. Paste the log content into a text (.txt) file or a Google Doc and share it with us.

    • If there are no logs, please run a Preview of the script and send us a copy of the preview logs.

Some Enhanced Scripts™ have a setting in the Optmyzr interface to include additional logging details. It's helpful to turn on this option, then run the script, and include the full logs generated by Google Ads in your message to us.

Logs Truncated: Length Exceeded Limit of 100,000

  • Understanding the Warning Message:

    • This warning appears on the Google Ads interface and indicates a restriction or issue originating in Google Ads for any script. It signifies that the console is not showing logs after the specified length limit (100,000 characters).

    • This error does not affect the script or its execution.

How do I make sure my script is working correctly?

Once you've run the script in Optmyzr, you should be able to see details like run time, run details, and summary in the "All Logs" tab under Enhanced Scripts.


If you see that the script is not working the right way, use the following steps to get your script log from the Google Ads API:

  1. Click on the "log statements" for the relevant script under the Results column.

  2. Copy the entire log content located under "History."

  3. Paste the log content into a text (.txt) file or a Google Doc and share it with us.


The Optmyzr team can help you investigate the issue. Please reach out to us and send us the following details:

  1. A screenshot of the error message

  2. A copy of the script code you're using in your Google Ads account

  3. The script log that you downloaded from Google Ads

Note: If there are no logs, please run a Preview of the script and send us a copy of the preview logs.

Troubleshooting Script Ownership & Email Visibility in Google Ads

When using Google Ads scripts installed via Optmyzr (like the Reach Target Monthly Spend script), you might notice that the email shown in Google Ads’ change history doesn’t match the one you originally used to set up the script. This can happen due to several reasons:

  • The script frequency is updated

  • Someone runs the script manually

  • The script is re-authorized by a different login

  • The script contents are edited

These actions make Google treat the new user as the one "executing" the script, even if they didn’t originally install it.

📝 Note: Google Ads does not provide a log of re-authorizations, so you won’t see when or who re-authorized a script unless you track it manually.

To avoid this:

  • Always create, authorize, and manage scripts from your dedicated whitelabel login.

  • Avoid running or modifying scripts from alternate emails unless necessary.

This helps ensure that the correct email identity appears in the change history, keeping things clean and consistent for client-facing accounts.

How to Fix or Prevent This: If you're seeing the wrong email in the change history and want to switch it back:

  1. Log into Google Ads using the correct email address (e.g., your whitelabel login).

  2. Open the script and re-authorize it.

  3. Optionally, adjust the script frequency (e.g., re-save the schedule) to reset ownership.

  4. Monitor the next few executions to confirm the email has been updated in change history.

Did this answer your question?