Data Mapping
The Settings → Data Mapping tab shows how fields from your connected platform map to ProofPod's internal data model. This is where you control which fields are synced and how they're transformed.
Prerequisites
Data mapping requires an active integration (Mindbody, Square, or ClubReady). If no integration is connected, you'll see a warning with a link to the Integrations tab.
Product & service catalog
At the top of the page, cards show the count of synced items:
- Products — number of products imported
- Services — number of services imported
- Categories — number of categories imported
Click Sync Catalog to pull the latest product/service taxonomy from your connected platform.
Field mapping table
The main table shows each mapped field with sortable columns:
| Column | Description |
|---|---|
| Source Field | The field name in your platform (e.g., SaleAmount) |
| Maps To | The ProofPod field it feeds into (e.g., revenue) |
| Type | The mapping type (direct, computed, etc.) |
| Sync | Toggle to enable/disable syncing for this field |
Use the sync toggle to control which fields flow into ProofPod. Disabling a field stops future syncs but doesn't remove already-imported data.
When to update mappings
You typically only need to touch data mappings when:
- You add new products or services to your platform and want them reflected in ProofPod
- You want to stop syncing a field you no longer need
- Your platform's field structure changes after an update
For most users, the default mappings work out of the box after connecting an integration.