analytics
Google business profile and PEKO: workflow and limits
Updated October 2026: Understand Google Business Profile reporting, local discovery and customer retention, with clear limits on what is verified about PEKO connectivity. No app for customers: snap the receipt, or use the optional Zalo Mini App add-on (Vietnam), and it works with the POS you already use.
Quick facts
- Integration
- Parallel workflow: confirm a supported direct connection before transferring data.
- Category
- analytics
- Ecosystem
- PEKO (AI customer retention) + LOOP (AI POS for operations). Same company, use either on its own or both together.
Google Business Profile helps eligible businesses manage how they appear on Google Search and Maps. PEKO focuses on customer retention. A venue can use both as parts of its customer journey, but that does not establish a direct technical connection between the products. This page explains a practical way to review discovery and retention separately, and what to confirm before expecting data to move between them.
Keep your Google presence accurate
Start with the information customers need before visiting: your business name, opening hours, location or service area, phone number and website. Google lets owners manage profile information through the account associated with the business. Verification and access requirements apply, and the available features can differ by business type and interface. Follow Google's instructions for your own profile rather than assuming a loyalty subscription changes your listing or verification status. Reviews are another part of that presence. Google documents how verified businesses can respond to reviews, subject to availability and its policies. Handle this work in Google unless a specific supported tool has been demonstrated. A retention workflow should not be described as automatically reading, replying to or publishing Google reviews without evidence of that functionality.
Read discovery signals without overstating attribution
Google's performance reporting helps eligible profile owners understand discovery and interactions. Only applicable metrics appear, and availability varies. A request for directions is an interaction with a profile; it is not, by itself, proof that a customer visited, purchased or joined a loyalty programme. Likewise, a change in discovery activity does not identify which individual customers returned. For a useful operational review, choose a consistent reporting period and record profile activity alongside separately available business and retention records. Note changes in opening hours, holidays and promotions. Look for questions worth investigating rather than treating similar trends as proof of causation. Do not combine aggregate profile statistics with named customer records on the assumption that Google supplied a person-level match.
Confirm connectivity before planning a rollout
This page does not confirm a live PEKO connection to Google Business Profile. Before depending on one, ask the PEKO team to demonstrate the supported account connection, exact permissions, available fields, reporting delay, disconnection process and any plan restrictions. Google's APIs have their own access prerequisites; their existence alone does not show that a particular vendor has an approved integration. Until those details are confirmed, maintain the profile in Google and assess retention through the tools actually available to your venue. There is no verified basis here for promising a ten-minute OAuth setup, automatic cohort correlation, a fixed three-day delay or a ranking improvement. Bring your requirements to a product discussion before committing to an automated workflow.
Discuss your discovery and retention requirements with PEKO.
Book a demoRelated integrations
analytics
Google Analytics 4
analytics
Meta Ads
pos
KiotViet
pos
LOOP POS

