Multisite

Overview

AFI fully supports WordPress Multisite (network-activated and per-site activations). Every subsite in a network gets its own integrations, its own logs, and — for Pro users — its own license activation.

How AFI behaves on a multisite network

• Per-site data. Integrations, logs, queued jobs, and saved credentials are stored in each subsite’s own database tables (wp_2_adfoin_*, wp_3_adfoin_*, etc.). Nothing leaks between subsites.
• Per-site settings. Settings such as API tokens, OAuth connections, UTM tracking, log retention, and the background queue are configured independently on each subsite.
• Database tables. The plugin creates its required tables automatically on every existing subsite at activation and on any new subsite created later via the standard wpmu_new_blog / wp_initialize_site hook.
• Network-activated installations are supported. You can also keep AFI in the plugin list and let site admins activate it themselves.

Licensing on Multisite

• Each subsite counts as one site. AFI Pro licenses are issued per site URL, so a network of 5 subsites needs the equivalent of 5 site activations.
• Pro plans of different tiers allow different activation counts. Pick the plan that covers your total subsite count, or move to the Unlimited plan if you’re running a large network.
• Each subsite is activated independently in AFI > Account on that subsite.
• If you change a subsite’s domain (e.g. moving from staging to production), see the Change Domain guide.

Setting up AFI on a new subsite

1. From the Network Admin, install AFI once at the network level.
2. Either network-activate the plugin, or let each subsite admin activate it.
3. On each subsite, go to AFI > Settings to enter API keys / connect receiver accounts.
4. For Pro: activate the license on each subsite under AFI > Account.

Notes & caveats

• No cross-site dashboard. There is no Network Admin screen that lists integrations across all subsites; you manage each subsite individually.
• Domain Mapping plugins. AFI binds the license to the canonical URL returned by home_url() on each subsite. If you use a domain-mapping plugin, make sure the canonical URL is correctly set before activating the license.
• Subdomains vs subdirectories. Both topologies are supported — AFI doesn’t care which one your network uses.
• Background queue. The WP Cron schedule that drives the queue is per-subsite. Make sure WP Cron is firing on each subsite or configure a server cron that triggers each site’s wp-cron.php.