Public report sharing

What it is

Every AdRevila report can be published to a unique URL at /r/<token>. That link opens the complete teardown — hook archetype, Schwartz stage, Cialdini levers, Hormozi scores, A/B hypotheses, letter grade — in a clean public view with no login gate. Share the URL with a teammate, a client, or a Slack thread. Revoke it whenever you're done.

It is not a screenshot and not a summary. It is the full report, rendered in the same interactive HTML your in-app view uses, served at a stable public URL you control.

How it works

After a report completes, click Share. AdRevila mints a random token and activates the /r/<token> route. From that point the URL is live and fully open — no cookie required, no referral gating. The page loads the structured report JSON and renders every section: the scored tags at the top, the body breakdown, the hypothesis table at the bottom.

To revoke, open the report, click Revoke link. The token is deactivated immediately. A new token can be minted for the same report at any time — the report data is not affected by link state.

The public view has no edit controls. Viewers read; they don't score, annotate, or regenerate. That boundary keeps client-facing links stable — a client can't accidentally trigger a re-analysis on a link you sent them.

How to use it

The sharpest use case is async creative review. A strategist runs a teardown on an Olipop or Athletic Greens Meta ad, mints the link, and drops it in a Slack thread or client brief. The client opens the full scored report — Schwartz stage, hook archetype, the A/B hypotheses — without needing an account. They leave a comment in Slack with their reaction. The strategist never had to write an explainer.

For agency teams the link replaces the "here's what I found" doc. A teardown of a competitor's top-spending ad, shared as a /r/<token> link before a strategy session, gives the room a common vocabulary before anyone opens their laptop. The report already names the mechanism; the meeting is about what to do with it.

Compare this to the PDF export: the PDF is for the deck and the inbox. The public link is for async collaboration — it's live, it loads fast, and the viewer gets the full interactive layout instead of a paginated document.

Why it matters

Analysis that stays inside your tool account has a short half-life. The insight that Liquid IV's current Meta creative is running a Proof-First hook against Solution-Aware traffic at a B+ grade is only useful if it reaches the people writing the next brief.

The public link is how a teardown leaves the tool and enters the conversation. No export step, no attachment, no "let me screen-share this real quick." One URL. The viewer sees what you see. The link dies when you say it dies.

That combination — zero-friction sharing, full data, revocable — is what makes competitor teardowns useful as a team sport rather than a solo research habit. Steal the strategy, share the evidence.