> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact support

> Send the information needed to investigate your AutoAdy issue.

Email [contact@autoady.io](mailto:contact@autoady.io) for product support, general questions, or partnerships. You can also use the [AutoAdy contact page](https://www.autoady.io/contact).

## Include the failed step

A useful request explains what you tried, what you expected, and what the product showed. Add the reference that identifies the work:

* **Connection:** provider, intended account or property ID, and the displayed error.
* **Report:** account ID, dates, timezone, currency, result definition, and fetch time or coverage warning.
* **Ad change:** entity ID, intended change, original request or receipt reference, and current provider state.
* **Creative or scheduled job:** job or run reference, outcome, and any reservation or delivery issue.
* **Billing:** receipt or invoice reference, selected plan, displayed subscription state, and approximate purchase time.
* **Website:** domain, environment, ownership state, and last received event or delivery error.

If you attach a screenshot, redact unrelated account information and secrets. Never send a password, API key, Meta token, payment-card details, or private authentication link.

## Example request

> I tried to refresh Meta Ads for account \[account ID] for \[dates]. The page shows \[exact error] and retains a report fetched at \[time]. I expected \[specific result]. I have already checked \[relevant connection or reporting setting].

For an unresolved write or payment, preserve the original attempt while waiting for help. Starting several new attempts can make the provider state harder to interpret.

## Find an immediate next step

Use [Troubleshoot by symptom](/help/troubleshooting) for connection, data, approval, website, and payment recovery. If you are a workspace member and a control is owner-only, ask your workspace owner to handle that setting.

Support cannot infer a new account grant from a report screenshot or bypass the provider's permissions. Include the identity and access context when it is relevant, with sensitive details redacted.

[Open AutoAdy](https://app.autoady.io/dashboard) · [Developer reference](/developers/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.