> For the complete documentation index, see [llms.txt](https://www.oddle.me/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.oddle.me/docs/returning-guests/google-business-integration.md). # Google Business Integration Connect your Google Business Profile to Oddle and your Google Review Request automations stop being a black box. New reviews flow into one dashboard, and each new review that arrives after a request gets matched back to the automation that likely earned it — tagged **"Earned with Oddle"** — so you can see the real impact of your campaigns instead of guessing. You manage this in Merchant Admin at **Engage > Reviews**. *** ## What it does Google Business Integration covers four capabilities: 1. **Connect** — Link your Google Business Profile via Google sign-in, then map each Google location to one or more Oddle stores. 2. **Collect** — Reviews flow from Google into a Reviews dashboard, filterable by store, rating, and date. 3. **Attribute** — New reviews are matched back to the Google Review Request automation that likely drove them, surfaced as campaign stats and tagged **"Earned with Oddle"**. 4. **Reply** — Respond to reviews from inside Oddle, with AI-drafted replies and optional auto-posting. *(See* [*Replying to reviews*](#replying-to-reviews) *below.)* *** ## Why connect Most restaurants run review requests and never know if they worked. A guest dines, gets an automated email, leaves a review three days later — and there's no way to tell whether your campaign drove that review or it would have happened anyway. Connecting your Google Business Profile closes the loop: * **See attribution.** New reviews are matched back to the automation that prompted them. * **Measure what's working.** Each Google Review automation surfaces attribution stats — New Reviews, Attribution Rate, and Attributed Review Rating. * **All your reviews in one place.** The Reviews tab shows every synced review across all your connected locations. *** ## How attribution works When a new Google review comes in, Oddle looks back over a recent time window and checks whether you sent Google Review Request emails to that store's customers in that window. If the reviewer's name matches a customer who was emailed, the review is credited to that automation. Three things have to line up: 1. **Timing** — The review was submitted within the attribution window (default **7 days**, configurable per campaign) of a review-request email being **sent** to that store's customers. 2. **Reviewer name** — The Google reviewer's display name matches a customer who received the email. 3. **Store match** — The Google location reviewed maps to the Oddle store the email was sent for. Reviews that meet all three are tagged **"Earned with Oddle"** in your Reviews tab and counted toward the automation's stats. Reviews that don't still appear in the Reviews tab — they aren't attributed. {% hint style="info" %} **Attribution keys off when the email was sent, not when it was opened.** Google only exposes the reviewer's public display name — not their email — so there's no click or open event to tie a review to a specific recipient. Oddle matches on name within the send window instead. That makes attribution a close estimate, not a click-by-click count. {% endhint %} ### How names are matched Because Google only gives us the reviewer's public display name, attribution matches on the name. The matcher is built to handle how real names actually appear: * **Different word order** — "Tan Wei Ming" matches "Wei Ming Tan". * **Minor spelling differences and typos** — small variations still match. * **Accents and special characters** — normalised before comparison. * **Chinese names** — matched against their romanised (Pinyin) spelling. If a full-name match isn't found, Oddle falls back to weaker signals — the reviewer's name appearing in the email address, or a first-name match (tie-broken by whichever email was sent closest to the review date). ### It's an estimate, not an exact count Attribution is a careful best-guess, and it leans conservative: * **Some real wins go uncounted.** If a customer reviews under a nickname, initials, a different name than they gave you, or anonymously, there's nothing to match on. So your true impact is usually a bit *higher* than the number shown. * **Read it as a signal, not a ledger.** A climbing attributed count alongside a healthy star rating means your review requests are working. Don't treat it as a to-the-review tally. *** ## Connecting your Google Business Profile A one-time setup, four steps. You'll need access to the Google account that manages your Google Business Profile. 1. Go to **Engage > Reviews** and select **Connect Google Business**. 2. **Step 1 — Connect with Google.** Select **Connect with Google** and complete the Google sign-in. Oddle requests the Google Business Profile management permission so it can read and (later) reply to your reviews. 3. **Step 2 — Review matched locations.** Oddle matches your Google locations to your Oddle stores. Review the matches and adjust if needed. 4. **Step 3 — Confirm.** Confirm your location and store mapping selections. 5. **Step 4 — Start syncing.** Select **Start Syncing**. Reviews from the **past 90 days** start importing. Once it's connected, new Google reviews flow into the Reviews tab automatically. *** ## The Reviews tab The Reviews tab in **Engage > Reviews** is where your synced reviews live. At a glance: * **Total attributed reviews** — how many of your synced reviews came through Oddle automations * **Google locations connected** — how many of your locations are linked and updating The reviews table shows every synced review with reviewer name, review content, the store it applies to, star rating, and date. You can filter by store, rating, and time period. Attributed reviews are tagged **"Earned with Oddle"** so you can scan for them quickly. *** ## Attribution stats on Google Review automations Once connected, each Google Review Request automation surfaces attribution-specific stats in place of the generic transaction metrics: | Metric | What it measures | | ---------------------------- | --------------------------------------------------------------- | | **New Reviews** | Number of new Google reviews attributed to this automation | | **Attribution Rate** | Share of automation sends that resulted in an attributed review | | **Attributed Review Rating** | Average star rating of reviews attributed to this automation | The campaign view also breaks attributed reviews down by store, so you can see which locations are responding to your requests. *** ## Managing integration settings Once connected, you can adjust your setup at any time without disconnecting. 1. From the Reviews tab, select **Manage Integration Settings**. 2. Toggle individual Google locations on or off — useful if you want to stop updating a closed location. 3. Update store mappings using the multi-select dropdown — useful if you've added a new Oddle store and want to map it to an existing Google location. 4. Select **Update** to save. *** ## Replying to reviews Beyond collecting reviews and attribution, you can reply from inside Merchant Admin — and Oddle drafts every reply for you. There are two layers here, and the difference matters: **Oddle drafts a reply for every review.** Drafts use your brand's own words — your cuisine, signature dishes, and neighbourhood — so replies reinforce what you want diners searching for. They wait for you to read and post. **Auto-post replies posts the safe ones for you.** Turn it on and Oddle posts replies that pass your rules, shortly after a review arrives. Anything that doesn't pass is held as a draft with a reason, so nothing goes out that Oddle wasn't confident about. The toggle starts off, and you'll be asked to confirm the first time you turn it on. You can also **promote your shop or reservation link** in replies, turning a review response into a soft call to action. ### Your auto-post rules Rules stay editable whether the toggle is on or off: * **Star threshold** — the ratings you're happy to auto-post for. * **Sensitivity** — how cautious Oddle should be before holding a reply back for you. * **Topics** — subjects that should always come to you rather than post automatically. * **Instructions** — your own guidance on tone and what to mention. ### Catching up on past reviews Reviews that arrived before you turned this on won't have drafts waiting. Use **Catch up** from your Reviews list to draft replies for that backlog in a batch, then read and post them as normal. {% hint style="info" %} Leaving the toggle off at first is a sensible way in. You see how the drafts read in your own voice, then turn on auto-posting once you trust the tone. {% endhint %} *** ## Related {% content-ref url="/pages/0fCeu44t0JSVkVzuBnRh" %} [Automations](/docs/returning-guests/automations.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.oddle.me/docs/returning-guests/google-business-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.