Database tables
AcquisitionSuite stores its data in custom tables (prefixed with your WordPress table prefix, usually wp_) plus gated files as a custom post type. System Status checks that these exist.
Lite tables
| Table | Holds |
|---|---|
acquis_leads |
One row per person: name, email, IP, device, browser, country and visit count |
acquis_submissions |
One row per form fill, with source URL, referrer and UTM values |
acquis_submission_values |
Each field value for each submission |
acquis_forms / acquis_form_fields |
Your forms and their fields |
acquis_tokens |
Signed download tokens with expiry and used flag |
acquis_email_logs |
Sent and failed emails |
acquis_analytics |
Download and event counts for reports |
acquis_integration_logs |
Results of Mailchimp, Brevo and MailWizz calls |
Pro tables
| Table | Holds |
|---|---|
acquis_automation_rules, acquis_automation_log |
Rules and a record of what they did |
acquis_scoring_rules, acquis_lead_scores |
Scoring rules and each lead’s score |
acquis_lead_tags |
Tags and segments applied to leads |
acquis_pipeline_stages, acquis_lead_pipeline, acquis_pipeline_history |
Stages, each lead’s stage and the move history |
acquis_sequences, acquis_sequence_steps, acquis_sequence_enrollments |
Sequences, their steps and who is enrolled |
acquis_pay_orders, acquis_pay_transactions, acquis_pay_download_tokens |
Orders, payment records and buyer download tokens |
acquis_product_events |
Custom product interaction events |
Gated files
Each gated file is a post of a custom post type; its file (if uploaded) lives in wp-content/uploads/acquis-protected/. See Protected directory security.
Options
Settings are stored as WordPress options whose names begin with acquis_. Pro keeps its license state in its own options.
Working with the data safely
- Prefer the admin screens, exports and hooks over editing tables directly.
- Always back up before any manual SQL.
- Table structure can change between versions; avoid depending on column order.