Introduction
Altegio’s open ecosystem lets you extend core booking, CRM, and ERP modules with partner apps and custom integrations. This guide maps the Marketplace categories, multi‑branch installation model, webhook disable behaviors, and analytics event schemas—plus practical patterns for payments, messaging/WhatsApp, IP telephony, CRM, and Power BI reporting. References point to official Altegio documentation for implementation.
Marketplace categories and representative docs
| Category | Typical integrations and what they enable | Key documentation |
| Payments | Online/prepayment, membership sales, card‑fee handling via gateways (e.g., Stripe, VivaWallet, MonoBank, LiqPay, PIX) | See payment options in platform settings and partner setup guides: Platform settings (payments overview), Partner sites & payments hub |
| Chatbots, WhatsApp, SMS | WhatsApp/SMS reminders, re‑engagement, mass mailings, review collection | Chat bots catalog, Fromni WhatsApp/SMS, SMS.to, SMS providers directory |
| IP telephony | Caller identification, call recordings, callback flows, chain‑wide call analytics | IP telephony integrations, Reports – Calls |
| CRM | Lead/booking sync with external CRMs (e.g., Kommo via integrators) | Documentation hub (integrations), Social booking + CRM context |
| Analytics & BI | GA4/Meta Pixel booking events, client ID transfer, Power BI dashboards | GA4 connection, Event schema, Widget analytics + notes, Client ID (UA), Power BI – Smart‑Metrika, Power BI index |
| Loyalty & memberships | Digital cards, gift cards, bonuses, membership gating for online booking | Loyalty cards (chain), Loyalty transactions, LoyalCards integration, Boomerangme, Membership‑only booking |
Installation model for chains and franchises
Multi‑branch app installation
Altegio supports installing a Marketplace app across many branches in one flow. During connection, the user selects branches; your service receives an array of branch IDs (salon_ids[]). You must activate your integration for each ID to unlock per‑branch API access and webhook registration. Developers enable this in the app settings (“Allow to add the application to several branches”). See multi‑branch installation guide.
Chain data unification (for app designers)
- Client graph: a single chain client database and a consolidated “customer chain card” expose spend, visits, locations visited, and loyalty assets for a person across the network. See Chain client database and Customer chain card.
- Analytics surfaces metrics on unique customers, occupancy, bookings and revenue for chains; de‑dupe prevents duplicate outreach. See What chain analytics solves.
Webhook lifecycle and the “disable” flow
When a user disables your Marketplace app:
- All integration settings are deleted at the location level.
- API access is revoked for that location and Altegio stops sending events to your webhooks.
- Altegio sends a “disable” webhook to the callback URL configured in your app settings (format referenced from the API docs in that page). See Disabling an integration.
Analytics event schemas and attribution
GA4 connection and verification
Connect GA4 by adding a web data stream (G‑XXXXXXXXX) and pasting the Measurement ID into Integrations → Analytics → Google Analytics. Verify using Realtime reports. See GA4 setup.
Booking widget event taxonomy
The online booking widget emits standardized events to GA/Meta, including (not exhaustive): widget_loaded, service_selected, master_selected, date_selected, time_selected, booked, appointment_changed, appointment_deleted, company_page_open, master_page_open, review_created. See Full event list and Widget analytics notes.
Implementation notes:
- Each booking link can map to only one data stream (create additional forms for multiple streams). See GA4 setup.
- Minor discrepancies can occur between analytics and platform data when customers use multiple sources. See Widget analytics notes.
- (Legacy/UA) You can pass a custom Client ID to unify GA and CRM identities. See Client ID transfer.
Typical integration patterns
1) Payments and prepayment flows
- Enable online prepayments for services and group events; configure provider fees and where funds land (cash register mapping). See Partner sites & payments hub and Card fee configuration guide.
- Gate online booking to active memberships when needed (fitness/education). See Membership‑only booking.
2) Messaging: WhatsApp/SMS automation
- Connect a WhatsApp/SMS provider to drive reminders, re‑engagement of no‑shows, birthday promos, and reviews; some partners add triggers for “lost” clients. See Chat bots catalog, Fromni WhatsApp/SMS, and SMS.to.
- Core notification system (SMS/Email/Push/WhatsApp) is configurable in Altegio. See Notifications feature.
3) IP telephony with operational analytics
- Integrate virtual PBX/SIP to surface caller name, client card, quick booking, transfers, and callbacks; store recordings for 1 year and analyze calls via Reports → Calls. See IP telephony integrations and Reports – Calls.
4) CRM and lead sources
- Route bookings/lead data to your CRM (e.g., Kommo via integrators) and use social and map entry points to convert. See Online booking with social media and Book via Google.
5) Power BI dashboards for chains
- Push enterprise KPIs (cohorts, retention, time‑slot occupancy, service/staff sales, plan vs. fact) to Power BI via Smart‑Metrika. See Power BI – Smart‑Metrika and Power BI index.
6) Loyalty and digital cards
- Issue and sync digital cards to Apple Wallet/Google Pay, send location‑based/push notifications, and reconcile transactions across locations. See LoyalCards, Boomerangme, and Loyalty cards (chain).
Chain analytics and reports your apps can rely on
- Services profitability and revenue share (Arrived only); filter by period, service category, employee, location; export to Excel. See Services chain report.
- Staff earnings, services/products sold, hours, cost/hour, % of revenue, per location and period; export and audited downloads. See Staff chain report.
Security, privacy, and access controls
- Data roles: Businesses are data controllers for their client data; Altegio is the processor. GDPR is observed. See Privacy Policy (EU).
- Infrastructure and residency: EU hosting (Hetzner, Germany) is documented. See About Altegio.
- Fine‑grained access rights and data leakage controls, including masking client contacts, per‑section rights, and activity logs. See Securing your data and Appointment Calendar access rights.
Developer checklist
- Design for multi‑branch: handle arrays of branch IDs and activate your app per branch. See Multi‑branch installation.
- Implement a robust disable handler: purge per‑branch state on your side when you receive the disable webhook; expect Altegio to stop event delivery and revoke API access. See Disable flow.
- Emit/consume analytics using the official widget event names; connect GA4 correctly and document any attribution caveats. See Event schema and GA4 setup.
- For messaging/payment flows, reference partner‑specific setup pages from Altegio Support to avoid misconfiguration (e.g., WhatsApp templates, card fee mapping, membership rules). See sections above.
Additional resources
- Documentation hub (multi‑module, multi‑industry): Support index
- Online booking documentation sitemap: Online booking docs
- Analytics reports catalog: Analytics & reports
