Troubleshooting and account help

Check that you entered the product's public website, not an unsupported store page, private dashboard or local address. Retry once if the error is temporary. A site that blocks automated reads or returns an incomplete response may need manual entry.

Choose Edit manually or Add details manually and review the required fields. Do not publish a duplicate if Rocket identifies an existing app. A failed website read is not evidence that your app was rejected. For help, send the submitted URL, error text and approximate time through Contact.

Check the exact challenge values and domain shown by Rocket. DNS changes may need propagation time; a website challenge must be reachable publicly at the specified HTTPS location.

An open claim is not domain verification. A manual-review request must be reviewed before ownership changes. Contact Rocket with the app listing and visible claim status if the next step is unclear; never send DNS-account credentials.

Check each stage: authorization, matching source selection, app-specific mapping, last successful sync, selected provider and public visibility. Connecting alone does not complete the remaining steps.

Wait for a completed reporting day where required. Reconnect if provider access was revoked. Test revenue, unsupported configurations and stale evidence cannot establish public live revenue. If changing sources, confirm the switch and recheck visibility.

Use the same Google, X, GitHub or email identity you used for the account, where offered. For email/password access, use the password-reset flow rather than sharing a password. If a confirmation link has expired, request a fresh link through the account flow.

For a payment question, first identify whether it concerns Rocket Developer, Create, advertising or an independent app. Check the existing receipt before paying again. Contact Rocket with the relevant URL, receipt reference, approximate time and error. Do not include passwords, API keys, authorization codes or card details.