CCT Builder

Performance-First Data Architecture.

Break free from WordPress limitations. Our Dynamic Content module delivers schema-defined records stored in dedicated database tables, ensuring blazing-fast performance for even the largest datasets.

The Dynamic Content Architecture

Dedicated Database Tables

Traditional WordPress data handling relies on wp_posts and wp_postmeta, which can create performance bottlenecks as your site scales.

Our Dynamic Content module solves this by utilizing schema-defined records stored in their own custom database tables. This approach removes the standard overhead, providing a clean, efficient, and fast environment for your site’s data.

How It Works

Connect Data in 3 Steps

The Dynamic Content interface is built for speed and precision, allowing you to establish custom data structures in seconds.

Select a Widget Control

Click the dynamic tag icon on any Elementor widget control — titles, images, text, URLs, and more.

Choose Your Data Source

Pick from ACF fields, post meta, user data, custom tags, or your registered custom sources.

Apply & Preview

The widget instantly reflects live data. No page refresh, no switching tools.

CORE CAPABILITIES

A Universal Dynamic Tag System

Connect any widget to any data source in a few clicks.

Deep Plugin Integration

Native support for ACF, Pods, and Metabox fields. Point and click to bind any field value to any widget control.

User & Author Data

Display current user info, author bios, user meta, and role-specific content automatically.

Post Meta & Custom Tables

Pull from post meta or your own custom SQL tables via a registered dynamic tag — no PHP required in Elementor.

Custom Tag Registration

Register your own dynamic tags via a clean PHP API. Once registered, they appear in every Elementor widget's dynamic tag picker.

Output Filters

Apply date formatting, text truncation, number formatting, and fallback values directly within the tag configuration.

Questions

A CCT stores structured records in their own database table rather than in wp_posts. Reach for it when data is structured and mostly displayed — properties, team members, menu items — because it keeps wp_posts lean and queries quick. Choose a CPT when you need WordPress-native editing of long-form content.

No. You define the type and its fields and save; Tiger creates the dedicated table for you. Three reserved fields — the record id and its created and updated timestamps — are managed automatically.

Text, text area and rich text; number, email, URL and phone; date, time and date & time; select, radio and switch; colour; and image or gallery from the Media Library. There is also a Computed field, a virtual value generated from other fields in the record with no column of its own.

Records live in their own table rather than sharing wp_posts with your pages and posts, so large datasets stay fast and don’t compete with ordinary WordPress content for the same indexes.

Every field is published as a Tiger dynamic tag, so you can bind it to any Elementor widget. Pair it with the Query Builder and a Dynamic Loop to build a directory, a property archive or a filterable grid.

Each type gets its own item list where you can add, edit, duplicate and bulk-delete records, with required-field validation applied on save.

Usually the loop source. Point the Query Builder query, or the loop’s source, at the CCT, and make sure the loop template binds the CCT’s dynamic tags — a fixed heading won’t change per record.

Make Every Widget Dynamic.

Stop hard-coding content. Let your data do the work.