Native integration

Send review requests automatically from Gingr

Gingr connects natively to ReviewNudger: when a reservation is checked out in Gingr, the event can create one neutral Google review request by SMS or email, subject to your sending rules — automatically, with no middleware in between.

Start free — 14 days

$29/mo per location after your trial · $0 today · cancel anytime

How it works

  1. 1
    Connect Gingr to ReviewNudger by pasting one web address and one signature key into Gingr's Admin » Custom Configurations screen — no API keys, no password sharing, no plan upgrade. Your pet parents, pets, and reservations stay in Gingr; ReviewNudger only listens for checkouts.
  2. 2
    When a boarding, daycare, grooming, or training reservation is checked out, Gingr sends the checkout to ReviewNudger with the pet parent's name, email, and phone. ReviewNudger applies your sending rules and can send one neutral Google review request by SMS or email after the delay you choose — an hour after pickup, or that evening.
  3. 3
    A family checking three dogs out at once is asked once, not three times: ReviewNudger keeps one review request per pet parent per checkout day, and your cooldown decides how soon a regular daycare client can be asked again. Every send is tracked with delivery status, opt-outs, and review click-through.
app.reviewnudger.com
ReviewNudger drip campaign editor with the text review request step open for editing, followed by email follow-ups with wait steps

Why a native connection beats middleware

The same four guarantees on every native integration — because they come from the platform, not the connector.

No middleware account or per-task fees

The connection runs directly between your account and ReviewNudger. There is no third-party automation account to maintain and no per-task metering on your review requests.

No manual field mapping

ReviewNudger already knows the provider's payload. Customer name, phone, and email resolve automatically — there are no field mappings to build or quietly break later.

Built-in duplicate protection

Every incoming event is deduplicated before any message goes out, so provider retries and replays can never double-text a customer.

Opt-out compliance handled

STOP replies and email unsubscribes are recorded per customer and honored automatically on every future trigger.

Set up the Gingr integration

  1. 1
    Start a ReviewNudger trial and finish the short signup.
  2. 2
    In ReviewNudger, open Settings › Integrations › Gingr, enter your Gingr address (yourbusiness.gingrapp.com), and click Connect. ReviewNudger shows you a webhook URL and a signature key.
  3. 3
    In Gingr, have an Admin open Left Navigation › Admin » Custom Configurations, paste the URL into Webhook URL and the key into Webhook Signature Key, and save.
  4. 4
    Check out a real reservation in Gingr to confirm the trigger end to end.
  5. 5
    Done. Each checkout can now start one automatic review request per pet parent under your sending rules.

Frequently asked questions

Do I need a Zapier account to connect Gingr?

No. The Gingr integration is native: you connect it directly inside ReviewNudger, with no middleware account, no per-task automation fees, and no field mapping to maintain.

What exactly triggers a review request?

Each time a reservation is checked out in Gingr, ReviewNudger records the event and evaluates it against your per-location send delay, cooldown, contact, and channel rules. One matching event can create one review-request journey by SMS or email.

Can a retry or duplicate webhook double-text a customer?

No. Every incoming event is deduplicated before any message is sent, and each event can create at most one review request. Provider retries and replays collapse onto the same request instead of sending twice.

What about customers who opt out?

SMS recipients can reply STOP at any time and email recipients can unsubscribe. Opt-outs are recorded per customer and honored across every future Gingr-triggered event.

Do I need Gingr API access or a particular Gingr plan?

No. ReviewNudger uses Gingr's built-in webhooks, which every facility configures itself under Admin » Custom Configurations, and never calls the Gingr API — so the Enterprise-only API credentials are not needed. Gingr allows several webhook URLs separated by commas, so a facility already sending webhooks to another tool keeps that working.

What if two pets check out together, or a daycare regular comes every day?

Gingr sends one checkout per reservation, but ReviewNudger keeps one review request per pet parent per checkout day, so a multi-pet family is asked once. Recurring daycare clients fall under the cooldown you set, and a reservation reopened and checked out again the same day never asks twice.

Questions before you start? Email support@reviewnudger.com and a human will answer.

← All integrations

More reviews. Zero effort. Start today.

$29/month per location · 14-day free trial · cancel anytime