Proofloop documentation
Ask for proof, route it, display it. This documentation covers everything from unzipping the archive to running your first campaign, and it opens offline — nothing on these pages loads from the internet.
What Proofloop does
You ask a customer for proof by email, SMS, WhatsApp or a QR code. They land on a page you branded, give a star rating, and write or record a testimonial. The routing engine then decides where to send them next: to your Google review form, to another public platform, or into your own testimonial library. What you collect is displayed back on your site through an embeddable widget.
It is built for agencies as well as single businesses, so it separates the company that owns the account from the client brands it collects for. If you are collecting for yourself, you will never notice the distinction.
Read these first
Installation
The browser installer, requirements, the one cron job, and what to do when something on your host is unusual. No terminal needed at any point.
Email, SMS & WhatsApp
Connect a sending provider and get past spam filters. The domain verification section is the difference between a campaign that lands and one that does not.
Place IDs & destinations
Five minutes, no API, no approval: find your Place ID and Proofloop can send happy customers straight into your Google review form.
Routing & ask-all
How Proofloop decides where a customer goes next, and why the default asks everybody rather than filtering by rating.
About Google, before you start
This is the single most common source of confusion in this category, so it is stated here rather than buried in a FAQ.
Everything in Proofloop works without any Google credentials — including sending review requests and deep-linking customers to your Google review form. Adding a Places API key (instant) displays your rating and the 5 most recent reviews Google exposes publicly. Full review history, new-review notifications and replying from the dashboard require Google Business Profile API access, which you apply for directly from Google — approval typically takes around two weeks and is granted at Google’s discretion. Proofloop guides you through the application, but we cannot grant it.
In practice: set up Proofloop today, find your Place ID, and start collecting. If you later want Google reviews pulled back into the dashboard and answered from there, follow the Google API application guide. If Google turns your application down, nothing you have built stops working.
The rest of the documentation
| Page | What is in it |
|---|---|
| Installation | Requirements, the web installer, cron per hosting panel, updating, moving hosts, troubleshooting. |
| Email, SMS & WhatsApp | SMTP, Mailgun, Postmark, Resend, Amazon SES, Twilio SMS and WhatsApp. SPF, DKIM and DMARC. Costs and quiet hours. |
| Embedding widgets | Script embed, iframe embed, WordPress, styling, and what the widget deliberately does not do. |
| Place IDs & destinations | Three ways to find a Place ID, building the review link, and non-Google destinations. |
| Routing & ask-all | Rules, conditions, the private feedback path, and the reasoning behind the default. |
| Google API application | Places API versus Business Profile API, the application step by step, why 0 QPM is not an error, and the rejection reasons that come up most. |
| Compliance | What you may and may not do with Google reviews, incentives, structured data, and customer data requests. |
| FAQ | The questions asked before and after purchase. |
| Changelog | What changed, and when. |