Custom tables, bi-directional relations, and a visual query builder — the structured-data backbone for dynamic sites.
Model, relate, and query your content with database-grade performance.
Store large datasets in dedicated tables instead of bloated post meta.
Connect any content types with indexed, high-performance relationships.
Query across sources with filters, meta, taxonomies, and relations — no SQL.
Create custom tables and fields for exactly the content you have.
Link content types together with two-way relationships.
Pull it into any Tiger widget with the visual query builder.
Yes. For guests the list is written to a first-party, Tiger-prefixed cookie with secure attributes, lasting 30 days, so it survives page loads without an account. Logged-in users get theirs saved to user meta instead, which persists across devices and browsers.
It is merged into their account on login and the guest cookie is cleared, so the two never diverge afterwards. Nothing is dropped at the moment of signing in — which is exactly when a shopper is most likely to abandon.
Almost certainly not. Guest lists live in a 30-day cookie, so clearing cookies, switching browser or using private browsing starts a fresh, empty list. Signing in moves the list to the account, where it’s durable.
No. Each store holds a JSON array of item IDs capped at a sensible maximum, so neither a cookie nor a user-meta row grows without bound.
No. Add and remove happen over AJAX, so a shopper can save products without a page reload and the counts stay live across the page.
It’s the engine behind the Wishlist and Compare experiences in the WooCommerce Conversion Suite. The store keys are allow-listed — wishlist, compare and favorites — rather than accepting arbitrary names.
The performance-first data engine at the core of Tiger Elements.
Join thousands of web creators who are building better, faster, and more beautiful WordPress websites with Tiger Elements.