Simpleview (Granicus) CRM Integration Guide
Enterprise CRM integration for Destination Marketing Organizations (DMOs) and Convention & Visitors Bureaus (CVBs).
Executive Overview & Value Proposition
Simpleview (a Granicus company) is the dominant CRM and CMS provider for the travel and tourism industry. Tourism marketing teams spend dozens of hours each week manually entering weekend festivals, live music schedules, and community events into their CRM.
Vibemap automates this entire pipeline:
- Automated Event Discovery & Enrichment: Vibemap continuously discovers and enriches local leisure events with photos, geo-coordinates, and vibe tags.
- Direct CRM Ingestion: High-quality, verified events flow automatically into Simpleview via Granicus-approved import tasks.
- Member Attribution & Reporting: Events are linked to Simpleview partner accounts, enabling DMOs to deliver clear value reports to local hospitality stakeholders.
- Configurable Approval Workflows: Choose whether approvals happen inside the Vibemap Hub or within Simpleview CRM before publication.
Per the Aug 27, 2026 sales meeting, each integration gets a standard playbook (procedural steps plus sales talking points), and less flexible proprietary integrations may carry an extra setup fee.
Architectural Patterns
Vibemap supports Simpleview in two distinct patterns based on client technical maturity:
flowchart LR
subgraph PatternB["Modern Pattern B (Visit Corpus Christi)"]
direction LR
V1["Vibemap Hub Engine"] -->|"REST API Feed\n(nightly)"| G1["Granicus Import Task"]
G1 --> S1["Simpleview CRM\n(Member/Partner Group)"]
S1 --> W1["DMO Public Website"]
end
subgraph PatternA["Legacy Pattern A (Discover Peoria - Being Decommissioned)"]
direction LR
S2["Simpleview CRM"] -->|"Scheduled Pull\n(4-8 hr lag)"| V2["Vibemap"]
V2 --> W2["WordPress Site"]
end
Pattern B: Vibemap as Source, Simpleview CRM as Destination (Modern Standard)
Live Implementation: Visit Corpus Christi
In this architecture, Vibemap is the system of record for discovering, verifying, and enriching public leisure events. Simpleview serves as the downstream CRM repository for marketing, reporting, and web syndication.
- Feed Exposure: Vibemap exposes a dedicated, client-scoped Event REST API endpoint (e.g.
https://api.vibemap.com/v0.3/events?boundary=<slug>&is_approved=true). - Granicus Ingestion Task: Granicus’s CRM team configures an automated Leisure Event import task scheduled to run nightly.
- Approval Gating: The import task pulls only events flagged with
is_approved = true. - CRM Partitioning: Imported events populate under a designated saved search in the Member/Partner user group.
- Review & Publishing: DMO staff (e.g., Dalilah at Visit Corpus Christi) review or auto-publish listings for downstream DMO website feeds.
Field Mapping Agreed with Granicus (Case 08416866)
| Vibemap Feed Field | Simpleview CRM Field | Data Type | Transformation & Mapping Rule |
|---|---|---|---|
is_approved | (Import Task Filter) | Boolean | Import only true. (The legacy field is_approved_crm is unused). |
title | Leisure Event → Name / Title | String | Canonical event headline. |
description | Leisure Event → Description | HTML String | Formatted event narrative. Crucial: Use description (HTML). Do not use text_full, which contains AI metadata and quality-analysis text. |
start_date / end_date | Start Date / End Date | ISO 8601 | Localized event schedule timestamps. |
place.name | Venue / Facility Name | String | Primary host location. |
place.address | Venue Address | String | Street address, city, state, postal code. |
place.point | Latitude / Longitude | Float GeoJSON | Standard EPSG:4326 map coordinate pair. |
categories | Category (CatID) | Integer Enum | Mapped to Simpleview category codes per the taxonomy table below. |
images | Media Assets | URLs | High-resolution photography links. |
ticket_url | External Ticket URL | URL | Primary booking or RSVP link. |
Category Mapping Taxonomy
Vibemap terms automatically normalize to Simpleview CatID parameters. Any unmapped or novel vibe category safely defaults to CatID_3 (Community).
| Vibemap Category | Simpleview CRM Category | CatID |
|---|---|---|
arts | Art | CatID_4 |
music | Live Music | CatID_15 |
theater, film | Film | CatID_21 |
family | Family | CatID_6 |
sports | Sports | CatID_10 |
outdoors | Outdoors | CatID_8 |
food, shop, drink | Shopping & Dining | CatID_11 |
entertainment | Ticketed Events | CatID_22 |
health, games, community | Community | CatID_3 |
visit | Holiday & Seasonal | CatID_12 |
(Note: Vibemap can also rename or remap categories to match bespoke Simpleview taxonomies upon DMO onboarding).
Pattern A: Simpleview CRM as Source (Discover Peoria, Legacy)
Status: Decommission in progress (4-Week Cutover)
In this legacy flow, Peoria staff edited listings and events directly in Simpleview CRM. Vibemap pulled those records on a recurring schedule and mirrored Simpleview values verbatim onto the website.
Historical Pain Points & Failure Modes
- End-to-End Latency: Changes took 4–8 hours to propagate from Simpleview into Vibemap and the frontend.
- Stale or Incorrect Data: Map coordinates and dates originated in Simpleview, requiring staff to fix data in multiple dashboards.
- Renamed Business Desync: Renaming an account required updating both the Simpleview account record and listing record before the sync accepted the change (e.g. CrossFit 309, June 2026).
- Archaic Duplicates: Legacy archived records frequently resurfaced in live site search.
- Mapping Glitches: In June 2026, an upstream location-mapping error placed dozens of disparate events at the Peoria Art Guild (fixed by John).
4-Week Decommission & Direct-Publishing Cutover
To eliminate the 4–8 hour lag and remove unnecessary middleware, Peoria is cutting over to direct Vibemap → WordPress publishing:
sequenceDiagram
autonumber
participant DMO as Peoria Staff
participant Hub as Vibemap Hub
participant WP as WordPress VIP Site
participant CRM as Simpleview CRM (Sales Only)
Note over CRM: Decommissioned from public web publishing
DMO->>Hub: Edit place, verify hours, approve event
Hub->>WP: Instant REST Webhook / Sync
WP-->>DMO: Page reflects change in real time
Note over CRM: Retained strictly for B2B sales & convention leads
- Week 1 — Decouple Publishing: Remove Simpleview from the public web publishing pipeline.
- Week 2 — Direct WordPress Connector: Establish native Vibemap WordPress plugin syndication.
- Week 3 — Parity Audit: Validate event schedules and venue amenity parity against historical records.
- Week 4 — Decommission & Archive: Remove legacy sync crons. Simpleview remains solely as Peoria's internal sales and convention lead CRM (Peoria confirmed no Simpleview Accounts sync or hotel extranet needed).
Operational Best Practices & Troubleshooting
- Kickoff Alignment: Granicus project notes occasionally default to assuming CRM → Vibemap ingestion. Always confirm Pattern B (Vibemap → CRM) in writing at project kickoff.
- Ticket Escalation: Establish clear ticketing protocols with Granicus (Case 08416866). Never rely on automated ticket closures without joint verification.
- Origin Tagging: Tag imported events inside Simpleview with a distinct lead source tag (
Vibemap Feed) so staff can differentiate API events from manual website member submissions. - Staging Verification: Always validate imports in staging (
<destination>.simpleviewcrm-stage.com) with a dedicated Vibemap QA login before pointing to production. - Approval Gate SOP: Agree whether initial approval happens in the Vibemap Hub or Simpleview CRM. For Corpus Christi, Vibemap filters to
is_approved = true, and Dalilah conducts final review in Simpleview.
Key Contacts & Resources
- Granicus / Simpleview Leads: Madison Graves, Meredith Sasser, Steven Giampapa
- Reference Case: Granicus Support Case 08416866 ("Vibemap Rest API / Feed")
- Live Clients: Visit Corpus Christi (staging QA), Discover Peoria (cutover in progress)