No. Subscribers, broadcasts and automations stay in AWeber. The plugin stores only WP-side data: settings, OAuth tokens, mirrored landing pages and form widget config. SleekView reads those. Pulling subscribers into WordPress would duplicate the customer database and create new GDPR obligations, which is the opposite of what the plugin is designed to do.

When you link an AWeber landing page to a WP page, the plugin creates or updates a WP page that proxies the landing page. The source ID and sync timestamp live in postmeta on that WP page. SleekView surfaces both as columns, plus the WP page slug, so you can see the full mirror relationship in a single row.

Yes. The plugin stores both flags in wp_options. On multisite, each blog has its own option row, and SleekView shows all of them side by side as a privacy matrix. Filtering for blogs with either toggle on takes one click and surfaces every site you need to review before a regulator does.

Stats live in the AWeber dashboard and stay there. SleekView focuses on the WP-side audit surface, not on duplicating cloud reports. If you need to combine AWeber stats with WP data, the AWeber API is the right path; SleekView complements that by giving you the WP-side wiring as a clean table.

The token's stored expiry timestamp is visible as a column. You can build a filter for tokens within N days of expiry so re-authorization happens before forms break. Once the token is expired, every form on the site silently fails to post to AWeber, so catching it early is the difference between a small inconvenience and a missed campaign.

Yes. Elementor stores the widget settings in postmeta. SleekView reads those alongside Gutenberg block usage and the classic widget area, so a site running multiple builders still produces one clean audit. The list ID and tag string are the columns; the builder is just metadata.

It is the right starting point. Export the table, see every page that has an AWeber form or landing-page mirror, then plan replacements. SleekView does not handle the migration itself, but it makes the inventory step ten minutes instead of an afternoon of clicking through each post.

The registration-subscribe flag adds an opt-in checkbox to the WordPress registration form, with a default list ID. Both live in wp_options. SleekView shows the flag and the default list as columns so you can confirm new accounts are flowing to the right list, especially after a list reorganization in AWeber.