Data Model

Data model

The plugin creates its own tables using the active WordPress table prefix.

Core tables

ace_sessions

Stores the session spine:

• session UUID and visitor UUID
• first and last seen timestamps
• landing path and referrer
• UTM values
• IP and browser hashes
• raw IP with expiry where retained
• location/provider enrichment fields
• linked company ID
• bot and ignored flags

ace_events

Stores tracked events linked back to sessions:

• event UUID
• event type and name
• URL, path, and page title
• post and taxonomy context
• commerce-related context fields
• linked number ID
• metadata
• occurrence timestamps

ace_companies

Stores company-level enrichment and roll-up data:

• company name and domain
• provider/source information
• confidence state
• first and last seen
• total sessions, events, and calls
• notes and ignore state

ace_numbers

Stores number-routing rules:

• label
• display number
• E.164 number
• source and page matching rules
• campaign matching
• Amazon Connect identifiers
• default and active flags
• priority

ace_calls

Stores call-level data:

• call UUID
• Amazon contact ID
• number relationship
• called number
• caller hash and raw value with expiry
• start, end, and duration
• direction and status
• queue and agent names
• matched session and company IDs
• match confidence
• attributes and notes

ace_enrichment_cache

Stores cached enrichment responses:

• hashed IP
• provider
• provider response payload
• company details
• ASN and ISP
• confidence
• expiry

WordPress options

Alongside the custom tables, the plugin stores settings and saved reporting data in options, including:

• ace_settings
• ace_hash_salt
• ace_reporting_segments
• ace_schema_version

Design intent

I want the tables to be direct and operational.

The schema is meant to support:

• first-party tracking
• reporting drilldowns
• future call matching
• enrichment reuse
• saved reporting workflows

It is not meant to become a generic event lake with no clear reporting purpose.