Skip to main content

For agencies that report to clients monthly

Testimonial Reports for Agency Clients

Clients who pay an agency to collect testimonials want to see what came in, not hear that "it went well". StoryProof can send every new review to your own tools by webhook. Log each delivery as a row in a sheet per client, and the monthly report becomes a count of real rows plus a few approved quotes, prepared on a fixed calendar.

  • One log sheet per client, filled by webhook
  • A dated monthly calendar from setup to send
  • Only approved quotes reach the report

The problem, solved

Why testimonial reporting is painful for agencies

  • Counting reviews by hand every month

    Someone scrolls each client’s list, counts by date and pastes a number into a slide. It takes an afternoon and nobody can check it later.

  • Client data getting mixed together

    One shared log for every client invites a row in the wrong report, which is the fastest way to lose a client’s trust.

  • An unapproved review ended up in a report

    The log holds everything that arrived, including reviews the client never cleared for use.

  • Clients ask where the testimonials are used

    A count is not enough; clients want to see their best quotes working on their site.

  • Junior staff can see every client

    Whoever builds the report needs one client’s data, not access to the whole agency account.

Flip the switch to see how StoryProof handles each one.

Reporting calendar

Your monthly client report, dated

Pick the first day of the reporting month. The logging step uses a Google Sheet with an Apps Script web app, following Google’s docs as read on 2026-11-17; Zapier or Make can write the same rows if you prefer.

  1. Day -7

    Set up one log per client

    Create a Google Sheet per client. In Apps Script, add a doPost(e) function that reads e.postData.contents and appends it as a row with the time it arrived, using appendRow. Deploy it as a web app and copy the /exec URL.

  2. Day -6

    Connect and test each client

    Add each client’s /exec URL where StoryProof lists webhooks, then submit one test review per client. Confirm it landed in that client’s sheet and nowhere else, and note which values the row holds.

  3. Day 0

    Month starts, rows accumulate

    Leave the logs alone. Each new review should add one row as it arrives.

  4. Day +14

    Mid month health check

    Compare each sheet with the client’s list in StoryProof. If reviews arrived but rows did not, fix the link now rather than in the report.

  5. Day +27

    Draft the report

    Count the month’s rows per client. Add two or three approved quotes and the widget they now appear in. Leave out anything not yet approved.

  6. Day +30

    Send and roll over

    Send the report, then start a new tab in each log for the next month so the count stays clean.

Dates are worked out in your browser. Nothing you pick is stored or sent.

A report section a client reads in a minute

Sample report, not a real client

New testimonials received this month: the number of rows in your log for the month.

Approved and now on your site: the quotes chosen for the homepage widget, listed by first name and company.

Waiting for your sign off: the number still pending, with a link to review them.

Next month: who we plan to ask, and when.

In StoryProof

Set up the reporting routine

  • You will need
  • StoryProof on Pro or above
  • A Google account that can own one sheet per client
  • An agreed report date with each client
  1. 1

    Give each client its own space

    Separate brand spaces keep testimonials, widgets and teammates apart. Check how many your plan includes.

  2. 2

    Log every new review by webhook

    Point a webhook at each client’s log and confirm with a test review that rows land in the right sheet.

  3. 3

    Tag what you report on

    Tag approved testimonials with the month you featured them, so the report and next month’s plan agree.

  4. 4

    Use the dashboard for context

    An analytics dashboard is on every plan. Use it alongside the log, and quote only numbers you can show the client.

What happens next: At the end of each quarter, read back three reports in a row. If the counts are flat, the next quarter’s plan should change who you ask, not the report.

Before you start

Where this routine stops

  • No built in client report

    StoryProof is not claimed to produce client reports. The log and the report are yours to build.

  • Payload contents are unknown here

    Field names, events, retries and signatures are not documented on this page. Store the raw delivery and read the real values from a test.

  • New reviews only

    The webhook sends reviews as they arrive. Approvals, edits and removals do not reach the log from anything on this page.

  • Google steps as of 2026-11-17

    The Apps Script details follow Google’s developer docs as read on 2026-11-17, not a test on a live account. Check access settings before sharing a URL.

  • Plan limits apply

    Webhooks start on a paid plan, and spaces and seats differ by plan. Check both before promising a setup to clients.

FAQ

Questions people ask

Short answers to what usually comes up next.

Can the client see the log directly?

You can share the sheet with them, but it holds unapproved reviews too. Many agencies share the report and keep the raw log internal.

Why store the whole delivery instead of chosen fields?

Because the payload format is not documented here. Storing the raw body with a timestamp means nothing is lost if you later find a field you need.

Does one webhook cover all clients?

Do not assume so. Test with a review from each client’s space and confirm where it lands before you rely on the routing.

What if a month has no new testimonials?

Report it plainly, with the requests you sent and what you will change. An honest zero keeps the later numbers believable.

Still have a question? Ask the StoryProof team or book a demo.

Report testimonials your clients can check

Collect for each client in its own space and log every new review as it arrives.

Sources

  1. Web Apps (doPost and deployment), Google for Developers. Checked 2026-11-17.
  2. Class Sheet: appendRow(rowContents), Google for Developers. Checked 2026-11-17.

Last updated 2026-11-17.