FAQ

Quick answers about what Launch Approved does, who it is for, and how it works.

Help section

Everything people ask about Launch Approved, in two groups: general questions about what it does and whether it fits your agency, and technical questions about how it works behind the cockpit. For topics that need more room, the Guides go deeper.


24 general questions and 18 technical questions — last update: 2026/10/29

A WordPress plugin that runs your acceptance tests from start to finish: a test plan, invited testers in a three-panel cockpit, expert audit tools, heatmaps, videos, a findings board and a report signed by your client, all on your own site.

Web agencies, freelancers and product teams who deliver sites or apps and want them approved before launch. It also suits trainers and consultants who audit sites, and companies that test a product with their own users.

Websites and web apps first, but also documents and deliverables (PDF, images, videos, HTML mock-ups, e-mails), desktop software and physical products, with measures and photos taken by the testers.

No. Ready-made plans are added in one click, every option has a switch and a line that explains it, and an example project shows every screen filled in before you start.

No. One licence per site, whatever the number of testers, campaigns and rounds. See Pricing & licence.

Each WordPress where Launch Approved is installed: your agency site, and each client site you link with the connector. An outside site you audit without installing anything does not count.

No. Each tester receives a personal link by e-mail: no account, no password. Once the test starts, the link works on that computer only.

Anyone you invite: colleagues, the client’s staff, real users you recruit yourself. You can also open an application form on your site and pick the best candidates.

Launch Approved keeps the pay statements: an amount per validated test, a bonus per confirmed finding, a cap and a budget. It never pays anyone itself: you pay them your way and mark what you paid.

An acceptance test uses invited testers and ends with the client’s decision. An audit is done by your experts. A pilot lets real users try the product over time. A quick test uses one shared link that anyone can open.

You sign first for the agency, then send the report by e-mail. The client opens the private link, reads it and signs online: accepted, accepted with reservations or refused, or « read and acknowledged » for an audit.

It is a simple electronic signature, which has the value of evidence. Launch Approved strengthens it with a signed copy, its SHA-256 fingerprint and a dated journey of every step. For high-stake contracts, ask your lawyer.

Yes. In the report, the client comments each finding and marks the ones to fix first. The votes show on your board and can sort it.

Yes. In the Report tab, untick the findings the client does not need to see. Nothing is deleted: the board keeps them all. Refused findings are never in the report.

Yes. Create the next round in one click: the same steps or only the failed ones, the same testers. The report compares both rounds, step by step.

Only if the campaign records videos and the tester accepts in the start window. The video shows the shared tab, never the camera, and is kept for the time you set.

Yes, with heatmaps of clicks, scrolling and mouse moves, on the pages of your WordPress or of a client site linked by the connector. See Heatmaps, videos & behaviour.

It is built for it: everything stays on your server, testers are told what is measured, nothing typed is recorded, and WordPress’s export and erase tools work with it. See Privacy & GDPR.

Yes. Your logo, colour and name appear in the cockpit, the e-mails and the report, and each project can carry its own brand. The small credit line of the report can be rewritten too.

The admin speaks English, French and Spanish. The cockpit, the e-mails and the report speak any language you add, and every word can be rewritten.

Yes. Give the roles of project manager, expert or client in WordPress Users. Each person has their own name, findings can be assigned, and the team gets a summary by e-mail.

Yes, from the outside: the expert tools, the analysis mode and the site health work on any public site. Clicks and heatmaps need the connector, so the owner’s agreement. Always audit with the owner’s permission.

Everything keeps working: your projects, findings, videos and signed reports stay on your site. You simply stop receiving updates and support.

Yes. The invitation can offer a practice run first: the same cockpit, with nothing recorded, so testers discover the screen before the real test.

WordPress 6.2 and PHP 7.4 or newer. The PHP « zip » extension is needed for the Word, Excel and archive exports. See Requirements & compatibility.

Yes. The cockpit opens your pages as they are, whatever the theme or the builder: Bricks, Elementor, Gutenberg, Divi… The admin of Launch Approved runs on its own screens.

In your WordPress database, and the files (screenshots, videos, signatures) in wp-content/uploads/launch-approved/, served by signed links only.

Nothing by default. Only optional checks, all off by default, call outside: spam blacklists and the update check with wordpress.org. The licence checks your site address and key to bring the updates.

You make a key on your agency site and paste it on the client’s site. The two sites then talk to each other with signed calls, and the client’s pages accept to be shown only in your cockpit. See Connector & client sites.

Browsers forbid reading what happens inside another site. Clicks are recorded on your own WordPress and on client sites linked by the connector, which must run a recent version of Launch Approved.

The page draws itself in the cockpit, once per page and screen family, with form fields left empty. If it cannot, the Behaviour tab says why, and you can capture the page by hand in the expert tools.

Recent Chrome, Edge and Firefox on a computer: they share the screen once for the whole test. Chrome and Edge offer the tab of the test first; on Firefox, the browser’s bars are cut off the video. Phones cannot share their screen.

About 2 MB a minute, enough to read the text and follow the mouse. You set the longest video per test (30 minutes by default) and how long videos are kept.

No. Once started, the link works on one computer only, and a test done cannot be opened again. You can give a new link, or let a tester take the test again from the Testers tab.

The browser warns first. If the page is reloaded anyway, the test goes on where it was or is stopped, as the campaign decides; the time of the reloaded step is never counted.

With WordPress’s scheduled tasks: reminders, summaries, clean-up of old data. On a site with few visits, set a real server cron so they run on time.

Yes, in Launch Approved > Texts and languages: every button, message, e-mail and line of the report, in each language. An empty field keeps the text provided.

As PDF (printed by the browser), Word, Excel and CSV. A whole campaign can also be downloaded as a ZIP archive, with its report, figures and screenshots.

At the client’s signature, a frozen copy of the whole report is kept with its SHA-256 fingerprint. The Journey tab checks it each time: any change to the file shows at once.

With an active licence, updates arrive in WordPress > Plugins, in one click, like any other plugin. Update the agency site and the client sites linked by the connector together.

Yes. Download the archive of a campaign (ZIP), then use Import a campaign on the new site.

No. The recording script loads only in the test zone, the pages opened by the cockpit. Real visitors download nothing more.