analytics
Meta ads and PEKO: campaign planning and data limits
Updated October 2026: Plan acquisition and retention without assuming PEKO audience sync, automatic ad management or verified conversion attribution. 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.
Meta Ads and a customer-retention programme address different parts of a venue's marketing. Advertising can support goals such as awareness, traffic or leads, while retention work focuses on the relationship after a customer engages with your business. Using both does not mean the systems exchange customer records or share a verified attribution model. This page explains how to plan the work without assuming an unconfirmed PEKO integration.
Start with the advertising goal
Meta recommends choosing an objective based on the outcome you want. Decide whether the campaign is intended to introduce the venue, generate enquiries or encourage another supported action. Keep that decision distinct from a retention goal such as bringing existing members back. A promotion can support both goals, but each needs its own success measure and operational owner. Meta Ads Manager organises advertising into campaigns, ad sets and ads. Account setup, payment arrangements and the applicable campaign settings belong in Meta's tools unless another supported workflow has been confirmed. Placement and format options depend on the objective and available features. Do not assume every placement or configuration is available to every account, or that PEKO creates and publishes campaigns for you.
Treat customer audiences as a separate decision
Meta offers Customer List Custom Audiences under specific terms. Those terms require necessary rights, permissions and a lawful basis for the data's disclosure and use. They also restrict certain data and audience criteria. A customer joining a loyalty programme should not be treated as automatic permission for every advertising use. Review the applicable notices, permissions and obligations before proposing any transfer. This page does not confirm that PEKO uploads contacts, maintains Custom Audiences, creates lookalikes or refreshes audience membership. It also does not confirm a PEKO-to-Meta conversion pipeline. If a team proposes a customer-list workflow, establish which tool performs each step, what data it uses, how objections are handled and who checks compliance. Hashing contact details does not remove these responsibilities.
Measure advertising and retention honestly
Review campaign reporting in Meta alongside the business records that are actually available to your venue. Use a consistent period and distinguish platform-reported outcomes from verified orders, visits and membership activity. Matching dates or campaign names can help organise a review, but it does not demonstrate that the same individual saw an ad and returned because of it. There is no verified basis here for a universal audience refresh schedule, guaranteed performance improvement or minimum spend at which better lookalikes become measurable. Agree on a test budget, a clear hypothesis and a review method before scaling. Ask PEKO to demonstrate any proposed account connection, supported data fields, permissions and limitations before making it part of your operating plan.
Discuss your acquisition and retention workflow with PEKO.
Book a demoRelated integrations
analytics
Google Business Profile
analytics
Google Analytics 4
pos
KiotViet
pos
LOOP POS

