What ZRD actually is
ZRD is the request for identity verification that Meta surfaces when its automated systems flag a profile as potentially fraudulent or as belonging to someone other than the listed identity. The acronym is shorthand inside the buyer community; Meta's own product copy refers to it as a confirm-your-identity prompt or, in more recent revisions, as a request to upload identification documents.
Importantly, ZRD is not a permanent ban. It is a verification gate. Profiles that pass it return to normal operation with no permanent restriction. Profiles that fail it can lose advertising privileges, and profiles that ignore it for more than the grace period are typically suspended pending response. The recovery flow below assumes the buyer wants to pass the gate cleanly, not appeal a permanent ban.
What makes ZRD a bigger deal in 2026 than it was two years ago is the rate at which Meta surfaces it. Tier-1 GEO buyers in our sample see ZRD on roughly six to ten percent of fresh-account launches, and on roughly two percent of aged-account launches. Those are uncomfortable numbers if your buying volume is high. Knowing the recovery flow turns ZRD from a campaign-killer into a temporary delay.
Conditions that trigger it
Meta does not publish the trigger conditions, but the empirical pattern from our sample is consistent. Profiles trigger ZRD more often when they exhibit any of the following: a recent country change in the IP-resolved location, a sudden budget jump that breaks the historical pacing curve, a creative whose copy includes high-risk keywords (financial promises, medical claims, gambling-adjacent language), a failed payment-method verification, or a friend-graph that does not match the registration country.
The country-change trigger is the one buyers underestimate most often. Logging in from a residential proxy in country A on Monday and a different proxy in country B on Wednesday looks suspicious to Meta even if both proxies are residential. The fix is operational: pin one proxy GEO per account and stay there.
The budget-jump trigger is also common. An account that spent fifty dollars yesterday and is suddenly trying to spend five hundred today triggers a verification request roughly thirty percent of the time in our sample. Smooth scaling — multiplying the prior day's spend by no more than 1.5 — keeps that rate near baseline.
Submission stage: doing it right
When the prompt appears, do not click through immediately. Wait at least an hour, ideally six. Meta sometimes surfaces ZRD as a soft prompt that resolves itself after a normal-looking activity period. Buyers who immediately click into the verification flow forfeit that resolution path.
If the prompt persists after six hours, the verification flow is unavoidable. Open it. Read carefully what Meta is asking for. There are three flavours: identity-only (government ID), identity-plus-billing (ID plus a payment method statement), and identity-plus-business (ID plus business documentation). The flow you get depends on what Meta thinks it needs to verify, and submitting the wrong flavour is a rejection.
Prepare the documents on your end before submitting. Both sides of the ID document. Image quality at least 1500 pixels on the long side. No glare, no cut-off corners, no glamour-shot backgrounds. The ID's name must match the profile's name exactly. If the profile name is a variation of the legal name (a nickname, a different transliteration), the verification will fail even with a real ID. Fix the profile name first if needed and wait twenty-four hours before submitting.
Documentation quality matters more than people think
Meta's verification pipeline runs OCR on whatever you submit. Low-resolution images get rejected silently. Documents photographed under fluorescent lighting often fail OCR even if a human eye reads them fine. Take the photo in soft daylight, against a plain background, with the document flat and fully in frame.
The second-order issue is metadata. Some smartphones embed location data in photo EXIF. If your ID photo's EXIF says it was taken in country A, but Meta has the profile registered in country B, that mismatch triggers an automatic rejection. Strip EXIF before uploading. Most buyers do this anyway. The ones who do not see verification rejection rates twice the baseline.
Meta also rejects documents that look digitally altered, even when they are not. Cropping the document to remove a corner, adjusting brightness aggressively, or running the image through a generic photo enhancer can all push the document into a borderline rejection range. Submit the photo as raw as possible, with only the minimum cropping needed to fit the upload requirements.
The waiting period
Once submitted, the verification typically resolves within two to seventy-two hours. Most cases resolve within twenty-four. Cases that drift past seventy-two are usually being routed to manual review, which can extend the timeline to a week or more.
Do not log into the account during the waiting period. Each login Meta records during a verification flow is treated as an event that may be relevant to the verification decision. Buyers who babysit the account during verification — checking it every few hours — see slightly longer resolution times in our sample, suggesting the extra activity nudges the case toward manual review.
Do not submit a second verification while the first is pending. Some buyers, anxious about the wait, submit a fresh document set thinking it will speed things up. The opposite happens: Meta queues the second submission behind the first, and the case is now in a more conservative review track.
When rejection happens
Rejection arrives as a notification that the verification was unsuccessful. The notification rarely says why, which is the most frustrating part of the flow. Without explicit feedback, the buyer is reduced to inferring the cause.
The single most common cause of rejection is name mismatch between the document and the profile. Fix the profile name to match the document exactly, wait twenty-four to forty-eight hours, then re-submit. Most rejections that follow this fix succeed on the second attempt.
The second most common cause is image quality. If the rejected submission was a photo taken in poor lighting, retake it under better conditions and resubmit. If the rejected submission was already high quality, the cause is likely something other than the document — most often a mismatch between the IP GEO and the document GEO.
After two rejections, escalate to the appeal flow. Appeals are slower (one to three weeks) but bypass the OCR pipeline and route to a human reviewer. We have seen accounts recovered through appeal that two automated rejections had given up on. The appeal text matters; keep it short, factual, and specific to the documents you submitted.
Post-recovery operating posture
An account that survived ZRD verification carries higher trust afterward, paradoxically. The pass-through marker is one of the stronger trust signals Meta records. We see post-ZRD accounts survive subsequent campaigns at noticeably higher rates than pre-ZRD baselines.
That said, the recovery does not erase the trigger condition. If the ZRD was triggered by a country mismatch, the account will trigger again the next time the country mismatches. Identify the trigger and stop reproducing it.
Post-recovery, give the account a low-pressure week. Run only the campaign that was active before ZRD, at the same budget and audience. Do not introduce new creatives, do not scale, do not add new payment methods. The recovered account is back in operational state, but Meta's review pipeline still has it tagged as a recently-verified profile, and additional changes during this tagging window draw scrutiny.
From the comments (32 total)
The EXIF point is the one I never see in any vendor doc. Stripped on next submission, passed first try.
Six-hour wait before clicking through resolved it for me. I would have clicked immediately on every account before reading this.