How should evidence be organised after rejection or restriction?
Preserve the original notice, affected asset, time, page version and retest outcome, with a before-and-after correction record. If difficulties continue, bring the evidence to BestCloak to discuss a suitable setup and scoped trial.
Establish one shared incident record
During a rejection or suspension, media, engineering, support and business teams may all change content independently. Without a common history, the case explanation can contradict the live destination. Preserve the original notice, affected asset, timestamp and release before assigning work. For internal triage, separate content, identity or eligibility, destination functionality, and account or payment issues. These labels organise investigation; they do not replace the platform’s actual notice. A failure that engineering cannot reproduce is not automatically a mistaken decision.
Use five evidence groups
The following is an internal template, not a platform-mandated form. Remove unnecessary customer data, credentials and unrelated sensitive material before sharing it.
| Record | Include | Avoid |
|---|---|---|
| Original issue | Exact notice, asset ID, timestamp | A paraphrase without the notice |
| Version | Creative, page, application and configuration | Only the corrected screenshot |
| Correction | Location, reason, owner and completion time | Many unexplained simultaneous changes |
| Retest | Device, market, steps and actual result | Only the words “fixed now” |
| Submission | Case, submitted explanation, response and next step | Contradictory accounts of the incident |
Connect each correction to the reported issue
Explain what was reported, what was observed, what changed and how it can now be verified. For a dispute, identify the evidence that contradicts the notice. For a genuine fault, describe the correction directly instead of labelling everything a system problem. A market-specific checkout failure is better explained by reproduction steps, the corrected delivery configuration and a successful retest than by a redesigned homepage. Identity or eligibility issues need genuine applicable evidence; technical screenshots do not replace it.
Keep platform procedures separate
Facebook, Google, TikTok and Kwai can provide different processes and available actions. Use the current account interface and official materials. A time limit, appeal count or button name from one platform should not be copied into every workflow. Read the Google investigation guide or TikTok investigation guide for the relevant context. Teams can share evidence standards without assuming identical support procedures.
Include routing changes in release history
If campaign issues recur, bring the organised evidence to BestCloak, discuss a suitable setup and consider a focused trial. Record configurations, customer journeys and business performance before and after the change. Review observations alongside platform feedback to assess which areas improved and whether to expand the trial. After resolution, preserve what helped, what did not and which checks should move into preflight. For Meta asset issues, continue with the Facebook guide.
Official references and scope
- Google Ads — Fix a disapproved ad or appeal a policy decision
- Google Ads — Account suspensions overview
- TikTok Ads Manager — Request account review
- Kwai for Business — Advertising Policies
Consult the current platform requirements for your business and market. References inform the discussion; the diagnostic frameworks and illustrative scenarios are editorial guidance.