Settings & Administration
The AFI > Settings page has a General tab and one tab per active receiver platform. This page walks through every option, what it does, and when to change it.
General tab
Path: WP admin > AFI > Settings > General. Eight options, grouped here by purpose.
Activate platforms
A checklist of every receiver platform AFI supports. The platforms you tick appear in the receiver dropdown when you build an integration; unchecked platforms are hidden. The default is to show every platform — narrowing the list is purely a UI declutter step. The activation list is shared by all admins on the site.
Tip: if you only use 3–5 receivers, untick the rest. The receiver dropdown becomes a lot faster to scan.
Disable Log
Stops AFI from writing to the activity log table. Off by default. Tick this only if you’re running an extremely high-volume site and the log table is growing faster, losing the log makes troubleshooting hard, so prefer the Auto-delete logs option below.
Auto-delete logs after N days
Days to retain log rows. 0 means keep forever. Setting this to a positive value schedules a daily Action Scheduler task that deletes rows older than the cutoff. Recommended for production: 30 or 60 days.
Disable Special Tags
Hides the system tag family ({{_date}}, {{_user_ip}}, etc.) from the field-mapping dropdown. Existing mappings that reference these tags continue to resolve at submission time — this toggle only changes the UI. Off by default. See Smart Tags & Field Mapping for the full tag list.
Send UTM Variables
Enables capture of UTM parameters and ad-platform click IDs (gclid, fbclid, etc.) from the URL. When enabled, AFI sets cookies the first time a visitor lands with these query parameters and exposes them as tags in every form submission, even if the visitor browses to other pages before submitting. Off by default.
Turn this on whenever you run paid ads, email campaigns with tracking links, or any UTM-tagged source. The full list of captured parameters is on Smart Tags & Field Mapping.
Enable Job Queue
Switches AFI from sending receiver API calls inline (during form submission) to enqueueing them as background jobs run by Action Scheduler. The form submission itself returns instantly; the receiver call happens within seconds (or minutes if the queue is backlogged).
When to enable:
- Slow receiver APIs (a third-party platform takes 3+ seconds and is making your form feel slow).
- High-volume forms where parallel submissions would otherwise saturate PHP workers.
- Unreliable upstream APIs — queued jobs retry on failure, inline calls do not.
When NOT to enable: when the user needs immediate confirmation that the data reached the receiver (e.g. a payment platform), since the receiver call happens after the response goes back to the browser.
When enabled, the toggle row shows live stats: pending jobs, failed jobs, and when the queue last ran.
Send Error Email
Emails the WordPress admin when a receiver API returns an error response (4xx/5xx). The email contains the integration name, the request body, and the receiver’s response. Off by default — useful in production to catch silent breakages (e.g. an OAuth token expired), but noisy if you have many high-volume forms.
Developer note: the recipient, subject, and message body are all filterable: see adfoin_error_email_to, adfoin_error_email_subject, and adfoin_error_email_message.
Reset general settings to defaults
A small link at the bottom of the General tab that puts every option above back to its default. Does not touch platform activations, saved credentials, or existing integrations — only the eight general-tab options.
Per-platform tabs
Every receiver platform that needs credentials registers its own settings tab. When you visit AFI > Settings, the tab strip lists every receiver you’ve activated (in the Activate Platforms section above) — Google Sheets, Mailchimp, HubSpot, Salesforce, ActiveCampaign, etc.
What each tab contains depends on the platform’s authentication model:
- API key — paste a single token. Saved against the platform, used for every integration with that receiver.
- API key + subdomain / region — for platforms that host accounts on per-customer URLs (ActiveCampaign, ClickUp, Zoho’s regional clouds).
- Username + password — older platforms that don’t issue tokens.
- OAuth — Google Sheets, Google Calendar, HubSpot, Pipedrive, etc. Paste a Client ID + Client Secret you generate in the platform’s developer console, then click Connect to approve a permissions prompt. AFI stores the resulting access token / refresh token and renews automatically.
If a credential set stops working (e.g. someone revokes the OAuth grant from the receiver’s side), the integration starts failing with HTTP 401 — visit the platform’s Settings tab, click Reconnect, and existing integrations recover immediately. The individual receiver doc has the exact steps for each platform — see the Receiver Platforms index.
Multiple credentials per platform
AFI lets you save multiple credential sets per platform, so you can route different forms to different accounts. The Settings tab gains an Add credential button, and each integration’s receiver picker shows a Credential dropdown. Useful for agencies managing many clients in one WordPress install, or for sites that maintain separate marketing and support Mailchimp accounts.
Account & license (Pro)
AFI > Account is a separate top-level menu item managed by Freemius. You’ll find:
- License key — paste, activate, deactivate.
- Subscription & renewal info.
- Plan changes — upgrade, downgrade, or cancel. See Upgrade, Downgrade, Cancel.
- Site URL changes — see Change Domain.
- Multisite licensing — see Multisite.
Capability requirements
Every Settings page and every admin action (save, reset, clear logs) is gated by the manage_options capability — i.e. the WordPress Administrator role. Editors and lower roles cannot reach AFI’s admin UI. If you want to delegate AFI admin to non-administrators, use a role-management plugin to grant manage_options to a custom role.
Where settings are stored
General settings live in wp_options under keys prefixed adfoin_general_settings_*. Platform credentials live in encrypted form under adfoin_credentials. On multisite, every option is per-subsite — see Multisite.