Planned
Provider-agnostic integration framework, remote record snapshots, mapping versioning, and support tooling.
View all integrations
Integrations
Rollout gated
Simpleview compatibility built for DMO operations.
PopHops is implementing a provider-capable connector architecture with Simpleview as the first provider. The goal is operational fit, not marketing shorthand: inbound listing sync, CMS-safe embeds, mapping review, reporting export, and attribution that survives web-to-app handoff.
Availability status
Feature flag
Builder workspace, public widget delivery, reporting export, and provider-specific Simpleview adapter rollout.
Production validated
Reserved for the first real client deployment. PopHops will not use “native Simpleview integration” headline language before that validation exists.
What the connector is designed to do
- Sync remote accounts, listings, offers, and events into provider-agnostic cache tables
- Persist current canonical remote rows separately from append-only snapshot history
- Drive mapping review queues for exact, fuzzy, manual, ignored, and conflict states
- Deliver approved widgets under a generic public integrations namespace with strict allowed-origin controls
- Aggregate campaign, day, and listing reporting with attribution confidence rules
Integration model
Operational loop
Simpleview remains the source of truth for destination listing context. PopHops remains the operating system for Campaigns, Passes, Hops, Drops, redemptions, and analytics. The connector links those systems without forcing duplicate content operations.