How Synoveo Works
Understanding the Synoveo architecture and data flow
Synoveo acts as an intelligent bridge between your business platforms and Google Business Profile. Here's how the system works.
Architecture Overview
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ Your Source │ │ Synoveo │ │ Google │
│ Platform │────▶│ API Server │────▶│ Business Profile│
│ │ │ │ │ │
│ • WordPress │ │ • Auth/Security │ │ • Profile Data │
│ • WooCommerce │ │ • Sync Engine │ │ • Posts │
│ • Custom App │ │ • Plan Limits │ │ • Reviews │
└─────────────────┘ └─────────────────┘ └─────────────────┘Key Concepts
GBP Format Requirement
Synoveo API accepts data in Google Business Profile API format only. This means:
- Your platform transforms data to GBP format before sending
- Synoveo validates, filters, and forwards to Google
- No proprietary data models to learn
Plan-Based Field Filtering
Different plans have access to different GBP fields:
- Lite - Basic info: name, address, phone, hours (9 fields)
- Solo - Complete profile: + description, categories, attributes (14 fields)
- Pro - Full engagement: + posts, reviews, Q&A, media (150+ fields)
- Business - Everything: + analytics, insights, batch operations (200+ fields)
Location-Based Billing
You pay per location you sync, not per domain or user:
- Each plan includes a set number of locations
- Add more locations with add-ons ($5/month each)
- Unlimited WordPress sites can connect to your locations
The Sync Process
Data Collection
Your source platform (WordPress, etc.) collects business data from your site.
Transformation
Data is transformed to Google Business Profile API format.
Sync Request
Request sent to Synoveo API with authentication.
Validation & Filtering
Synoveo validates data and filters fields based on your plan.
Google Sync
Validated data is sent to Google Business Profile API.
Confirmation
Sync result returned with success/error details.
3-Way Sync Comparison
Synoveo provides a powerful 3-way comparison:
- Your Source - Current data from your platform
- Google - Current data on GBP
- Last Sync - What was synced previously
This helps identify:
- Changes made locally that need to sync
- Changes made on Google that need to sync back
- Conflicts that need manual resolution
Security Model
- OAuth 2.0 for Google authorization
- API Keys for platform authentication (WordPress)
- JWT Tokens for user sessions (Dashboard)
- AES-256 Encryption for stored tokens