Why does Chat fail when I use a custom date range?
For Google Ads and Microsoft Ads, ad group and keyword data is only available using preset date ranges — the last 30, 90, 180, or 365 days. Custom date ranges work for campaign and account-level data only.
If you're running a broad prompt — such as an account health check — Chat will try to pull data from campaigns, ad groups, and keywords at the same time. A custom date range will cause the ad group and keyword parts of that request to fail with a "Failed to fetch account" error.
To fix it, re-run your prompt and switch to one of the preset date ranges.
Why isn't Chat working on my new ad account?
Chat analyses performance history — spend, clicks, conversions over time. If an ad account is brand new, there may not be enough data for Chat to work with. This is especially likely with broad prompts that pull across multiple data types at once.
This isn't a bug — it reflects the absence of data rather than a connection problem. Come back once the account has a few weeks of history.
Chat says "Failed to fetch account" but my ad account is linked — what should I check?
First, confirm the date range isn't the issue (see above). If you're using a preset range and the error persists, go to Linked Accounts and check the account is still connected. Accounts can become unlinked if permissions change or access is revoked on the platform side.