What Gingr gives you
Gingr is pet-care software for daycare, boarding, grooming and training, and it has three owner-facing pieces a website can use. Online booking lets an owner request or book daycare days, boarding stays, grooming appointments and training against your capacity and schedule. New-client registration creates the owner account and the pet profile, with vaccination uploads and your digital agreements signed in the flow. The customer portal is where owners manage bookings, update records, pay and see report cards afterwards. All three live on your Gingr customer-facing site on Gingr's domain, and Gingr provides embed options so they can appear inside your own pages.
The performance question is where the embed goes. The answer: on the pages where the owner wants to book, never on every page.
The rule
Nothing from Gingr loads until the owner taps Book. Service pages, the premises page, the first-visit page and the team page are for reading and reassuring; they link to booking. Two dedicated pages carry the embeds.
Page 1: /book, for existing clients
The booking embed on one page, with a one-line reassurance ("Pick a service and dates; you'll get a confirmation straight away"), the phone number and the drop-off windows. Nothing else. Reserve the embed's height so the page does not jump while Gingr loads, and preconnect to Gingr's domain in the head:
<link rel="preconnect" href="https://your-business.gingrapp.com">
<div class="gingr-embed" style="min-height: 720px"><!-- Gingr booking embed here --></div>Service pages link here with the service pre-selected where Gingr's booking links allow it: the daycare page opens daycare, the boarding page opens the stay calendar, the grooming page opens the groom.
Page 2: /register, for new clients
New-client registration on its own page, linked from every "New here?" prompt, from the first-visit page and from the Book page for anyone without an account. Above the embed: what it will ask for (owner details, the pet, vaccination certificate upload, your agreements), how long it takes, and what to do if a certificate is not to hand. This is where vaccination and consent get collected, so the first-visit page and this page must say the same thing.
Where an embed misbehaves in a phone's in-app browser, send new clients to the hosted Gingr registration page instead and bring them back with a link.
Configure Gingr first
- Services with durations, prices by size or attribute, and packages, matching the tables on the site.
- Capacity for daycare and boarding, and the schedule grooming may book into.
- Pet profile fields, with vaccinations marked required for a first booking and expiry reminders on.
- Agreements to be signed at registration: daycare terms, grooming consent, matted-coat policy, treatment consent, photo permission, cancellation policy.
- Deposits or card capture, with the cancellation window stated.
- Confirmation and reminder templates in your voice, linking to the first-visit page.
- Notifications to the right phone for new clients and new requests.
- Report cards enabled, because they are the ongoing reassurance for daycare and boarding owners.
Register a test pet and book a test day from your own phone before the site links to any of it.
Tap-to-call and the first-visit page stay in the header
Gingr does not change the hierarchy. The header on every page carries the phone number, Book and, for new owners, Your first visit. On phones, a slim bar fixed to the bottom of the screen with Call and Book. An owner with a question about assessments does not want a booking widget; they want the page that explains, and then the button.
Deep links from service pages
For each bookable service, the service page's Book button opens /book with that service selected via Gingr's booking link, or embeds a service-specific link. The owner sees the daycare calendar, not a menu. For the assessment day that starts a new daycare dog, the daycare page's main button goes to /register, because the assessment cannot be booked until the profile exists.
Grooming salons running grooming through Gingr alongside daycare use the same pattern: one Book page, the groom pre-selected from the grooming page, the price table beside the button.
Testing on phones
Safari and Chrome on iOS and Android, and inside Instagram's and Facebook's in-app browsers, which is where a lot of pet traffic arrives from. Register a new pet end to end: profile, certificate upload, agreement signature, deposit, confirmation received. Then book a day as that client. Check both land in Gingr with the right notifications. If the embed fails in an in-app browser, link those entry points to the hosted pages. Repeat monthly; Gingr updates its customer-facing pages, and you want to find out before an owner does.
Tracking
booking_clickon every Book tap andregister_clickon every registration tap, each with the page and service as parameters.- Gingr's own reports for new clients and bookings by source.
- Monthly: taps by page against completed bookings in Gingr, so you know which service page books and which is read and abandoned.
Common mistakes
- The booking embed on every page, slowing the site for the majority who are reading.
- Registration and booking on the same page, so new owners hit a calendar they cannot use.
- Prices on the site that differ from Gingr's, so the confirmation contradicts the table.
- The hosted Gingr page as the Instagram link with no route back to your site.
- Nobody watching the Gingr notifications between groups.
Where this sits
Gingr is one of the platforms we wire into pet business websites most often, and this setup, two dedicated pages, deep links from service pages, the phone and the first-visit page ahead of both, and tracking on everything, keeps the site fast and the bookings landing in Gingr. Gingr holds the pet's record and the schedule. The site gets the owner into it in one tap.