📗 This content is the AI Max Analyzer user manual, the same one the script writes in the «Manual» tab of its spreadsheet. Here you can search it, listen to it, highlight it and save it to favourites.
14 days minimum: Before touching negatives, let AI Max learn.
Cost of incrementality: A CPA slightly above baseline is normal: you are paying for incremental volume.
Match priority: Your exact match keywords still take priority over AI Max for identical queries.
How to check that the script is working
These are the checks you can run in order to confirm the script is producing correct data. If the Dashboard to Combinations tabs add up, the script works; the Pre/Post Analysis tab is optional and depends on when AI Max was turned on.
1. Dashboard: The "ACCOUNT TOTAL" row of the "COST SPLIT" block should roughly match what you see in Google Ads for those campaigns in the analysed date range. If there are large deviations (>5%), first check whether every campaign with AI Max is being detected correctly.
2. Campaign Summary: Check that ALL the campaigns you have with AI Max enabled show up. The "AI Max start" column should show dates — if it is empty for one, the script is not detecting AI Max traffic for that campaign in the last 365 days.
3. Traffic Source: Each campaign should have at least one "AI Max - Broad expanded" or "AI Max - Keywordless" row with cost > 0. If all 3 sources (baseline included) have data, the split by source is working.
4. Top Search Terms: There should be at least some search terms with an AI Max origin. If it is completely empty but the previous tabs show AI Max traffic, the individual queries are being blocked by privacy thresholds.
5. Pre/Post Analysis: OPTIONAL. If it says "0/X analysable campaigns", read the DIAGNOSTICS block at the top — it will tell you why each campaign was discarded. The most common cause is that AI Max has been on for more than 365 days and we cannot compare with a PRE period. This does NOT mean the script failed.
6. Logs tab: If something does not add up, open the Logs tab and look for lines with "ERROR" (highlighted in red) or "AVISO" (in yellow). It is the first source of diagnosis when the script behaves unexpectedly — without having to open the manager account console.