Aivie Marketing Automation

The saved Aivie site URL enables tracking and Aivie blocks. The optional editor connection adds searchable pickers, so editors can choose published Aivie elements instead of copying IDs or names. Disconnecting the editor removes the connection and its saved element lists, but tracking, the Aivie site URL, and existing blocks remain in place. The read-only connection can retrieve these Aivie elements:

• Published forms.
• Published Focus items.
• Published Dynamic Content.
• Existing Aivie tags.
• Supported brand colors for the consent banner.

Yes, mostly. The core integration is compatible with upstream Mautic 7.2 or later, including consent-managed tracking, Forms, Focus items, Tags, and personalized Dynamic Content. Save the Mautic HTTPS URL and configure its CORS settings to allow the WordPress site. Without Aivie, editors lose some convenience features:

• Copy a Form or Focus ID from Mautic and paste it into the block instead of finding it in a searchable picker.
• Enter Tags and Dynamic Content slot names manually. The editor shows the saved fallback rather than a fetched Dynamic Content preview.
• Choose consent-banner colors manually instead of importing the brand palette.
• Work with Aivie-branded WordPress settings, blocks, and consent-service labels.

The block editor provides an Aivie category containing:

• Aivie Form: choose a published form, preview it in the editor, and style it with familiar WordPress controls for layout, typography, colors, spacing, borders, backgrounds, and positioning.
• Aivie Focus: choose a published Focus item, then review its selection summary and change it from the Block settings sidebar. It starts only after the visitor accepts the Aivie/Mautic tracking service.
• Aivie Tags: choose tags to add or remove, then review their summary and make changes from the Block settings sidebar. If a page contains several Tags blocks, the plugin combines them and avoids duplicates.
• Aivie Dynamic Content: choose personalized content and preview it in the editor. Separate Preview and Fallback tabs let you review the selected content and edit what visitors see when they have not consented or Aivie has no personalized replacement.

For least privilege, connect with a dedicated Aivie user whose role grants only API Access and these read permissions:

• Form Permissions > Forms: View Own and View Others.
• Focus Permissions > Focus Items: View Own and View Others.
• Tag Manager permissions > Tag Manager: View.
• Dynamic Content Permissions > Dynamic Content: View Own and View Others.
• Core Permissions > Themes: View.

Tracking and the consent banner have separate switches under Settings > Aivie. Both require a saved Aivie or upstream Mautic 7.2-or-later site URL but do not require the optional editor connection. The interface labels the required service as Aivie, including when it connects to upstream Mautic. Administrators can additionally configure Google Tag Manager, Google Analytics 4, Google Ads, Meta Pixel, LinkedIn Insight, Microsoft Clarity, Contentsquare, Hotjar, and consent-gated YouTube embeds. Logged-in WordPress administrators are excluded from tracking by default. They do not receive the consent banner, and no tracking service configured through this plugin is loaded for them. Administrators can explicitly enable their own tracking under Settings > Aivie > Tracking when they need to test the complete visitor experience. This setting cannot suppress trackers added independently by a theme, another plugin, or custom code. When tracking and the consent banner are enabled, Aivie/Mautic tracking starts only after the visitor accepts the required service. If the visitor declines or has not yet made a choice, this plugin does not track the page visit or start Focus and Dynamic Content features. The non-tracking Mautic essential runtime loads before consent so forms and anonymous page features can initialize. It does not access tracking identifiers or send a page visit. The separate tracking add-on, the first page visit, and Focus items load only after consent. After consent, tracking starts and records one page visit. Any Aivie Tags blocks on the page contribute their combined tags, and each registered Focus item starts once. The consent banner lists the required service as Aivie, lists each enabled additional service separately, and remembers the visitor's choices in a first-party cookie. Before enabling an additional service, remove or disable the matching tag in the theme, tag manager, header/footer snippet, or another WordPress plugin. The consent manager does not rewrite trackers loaded elsewhere. It warns about common tracking plugins that may produce duplicates. Google Tag Manager is an advanced option. Configure every tag and trigger in the container to respect its required consent state. GTM and direct services can be enabled together for different tags, but the same tag must not exist in both places. The settings page warns when both approaches are active. When YouTube embed consent is enabled, standard WordPress YouTube video and playlist embeds are replaced on the server with a consent placeholder. No YouTube iframe is created until the visitor accepts the YouTube service; the accepted iframe uses youtube-nocookie.com. This release does not rewrite arbitrary Custom HTML blocks or JavaScript video players. Google Consent Mode v2 offers three operating modes. The default Load Google only after consent mode blocks Google requests until acceptance, then sends all four granted Consent Mode v2 states before Google Tag Manager starts. Load before consent and send cookieless signals is an advanced mode that lets GTM contact Google with storage denied before acceptance. Do not use Google Consent Mode disables the Google consent-state integration. Tags inside GTM still require correct consent configuration. When Google Consent Mode is active and GTM is configured, the plugin adds tarteaucitron's gcmanalyticsstorage, gcmadstorage, and gcmadsuserdata services before the googletagmanager service. This ensures the consent update reaches the data layer before the container starts. An advanced setting can disable these services only for containers that implement all four equivalent updates themselves. After a visitor changes consent, the plugin pushes one debounced data-layer event named aiv_consent_update. Its aiv_consent object maps every registered tarteaucitron service key to true, false, or wait. In Google Tag Manager, use aiv_consent_update as the Custom Event trigger name and read values such as aiv_consent.googletagmanager with data-layer variables. The plugin implements this event itself because tarteaucitron's optional dataLayer event does not report a complete state after every decision. When the plugin detects a known active cookie-banner plugin, it suppresses the Aivie banner and shows an administrator warning. Deactivate the other consent plugin before using the Aivie banner so visitors do not see two consent interfaces. Detection is a migration aid and cannot identify every banner or script added by custom theme code. Administrators can choose from six translated consent-copy presets: three informal and three formal variants in concise, balanced, and detailed lengths. Each preset includes clear accept, necessary-only, settings, and privacy labels and is bundled in English, German, French, and Italian. The preset strings use the WordPress translation system, so a string-translation plugin can override them per language. A custom mode keeps the compact WordPress editor and separate action-label fields; supported translation plugins can translate these saved option values through the bundled wpml-config.xml. Every preset links its cookies-and-similar-technologies phrase to the published WordPress Privacy Policy. An optional setting adds a separate Privacy Policy button. If no published privacy page is configured, WordPress cannot provide a link destination. A link added directly to custom banner text remains visible. The consent manager is bundled with the plugin and served from WordPress. It does not contact a third-party CDN to download its code. A consent tool cannot by itself guarantee legal compliance. Site owners remain responsible for configuring tracking, consent, their privacy notice, and their legal basis for the relevant jurisdiction and use case.

The Form Tracking tab helps marketing teams understand which forms and calls to action turn visits into engagement. It recognizes every embedded Aivie form automatically and can report when a visitor starts a form, moves to another step, submits it, and receives a success or error response. It records the form and step names, but never the values entered into form fields. Click tracking is opt-in for each call to action. In the block editor, select a block that contains a button or link, open the Aivie Tracking panel, and enable Track clicks. An optional reporting name makes similar calls to action easy to tell apart in reports. Both reporting destinations are enabled by default and can be switched off independently:

• Google Tag Manager: places form and marked-click events in the data layer for use in tools such as Google Analytics 4. The site's GTM tags and consent rules determine which events are sent to an external provider.
• Aivie: adds form starts, form progress, and marked clicks to the known contact's timeline after the visitor has accepted Aivie tracking. Each timeline entry is recorded as a page visit.

The consent banner settings are stored in WordPress. An administrator can fetch supported brand colors from the connected Aivie account, adjust them, and save them for the website. These colors personalize the banner without changing how it works. Brand colors are fetched only when an administrator selects Fetch defaults from Aivie. Simply opening the settings page or visiting the website does not fetch them. If Aivie is unavailable or returns an unsupported value, the existing WordPress settings stay unchanged. Without a saved primary color, the banner uses its standard colors.

• Gives connected assistants access only to the WordPress content tools documented by this plugin.
• Requires secure browser sign-in and a WordPress approval screen before granting access.
• Limits every action to the permissions of the WordPress user who approved the connection.
• Creates new content as a draft by default.
• Requires explicit confirmation before changing live content or publishing a draft.
• Checks for editing conflicts and protects saved Gutenberg block structure.
• Lets administrators disable AI access or revoke all existing connections at any time.

AI assistants can work with standard WordPress posts and pages. They can also work with eligible custom content types that are public and visible in WordPress administration. The plugin shares only supported content fields, eligible categories and tags, active Advanced Custom Fields (ACF), and fields that were intentionally made available through WordPress. Private or internal classifications are excluded. It also excludes password fields and fields that appear to contain credentials, session data, authorization details, payment-card data, or bank data. The tools preserve Gutenberg block content when making updates. Connected assistants can read reusable blocks but cannot create, edit, publish, or delete them. When WPML is active, newly created or edited posts and pages are assigned WPML's Required translation priority. Developers can restrict generic content with the aivie_mcp_allowed_content_types and aivie_mcp_custom_field_allowed filters. WordPress capabilities remain authoritative.

Connected AI assistants can search the WordPress media library before uploading an image, helping to avoid duplicates. Uploads accept JPEG, PNG, GIF, and WebP images and are limited to the lower of the WordPress upload limit and 8 MiB. The plugin validates the actual image data and derives alt text from the filename when none is provided. Uploading creates a media-library attachment; it does not attach the image to content or publish content automatically.

Developers can customize the consent-manager configuration with the aivie_marketing_automation_tarteaucitron_configuration filter. The aivie_marketing_automation_mautic_tracking_url filter can change the tracking address or return an empty string to disable tracking. The narrowly scoped aivie_marketing_automation_tarteaucitron_aivie_privacy_url filter can replace the Aivie service's default https://aivie.ch/en/privacy-policy/ link with a site- or tenant-specific HTTPS privacy-policy URL; non-HTTPS or invalid values fall back to the default. The aivie_marketing_automation_pageview_attributes filter can add simple values to the consented page visit. The plugin reserves the tags value for combining Aivie Tags blocks and does not let the filter replace it.

This plugin communicates with external services only after an administrator or WordPress user configures the relevant feature. Brand colors are requested only when an administrator explicitly selects Fetch defaults from Aivie.

The main integration connects to the Aivie site entered by an administrator. During the optional editor connection, WordPress identifies the plugin and supplies the address needed to return from Aivie sign-in. The read-only connection can retrieve published forms, Focus items, Dynamic Content, tags, and requested brand colors. It does not send the content of WordPress posts or pages to Aivie. When a visitor accepts Aivie tracking, tracking starts. Aivie can then receive the page visit, configured tags, browser information, form starts and progress, and clicks on calls to action that an editor marked for tracking. It may set tracking cookies according to that Aivie account's configuration. Focus items also start only after the same consent. Form field values are not included in form-interaction tracking. An Aivie Form block retrieves the selected public form for the editor preview and published page. Forms do not require the optional editor connection after they have been selected. After consent, Aivie may replace a Dynamic Content block's fallback with personalized content. Aivie is operated by Idea 2 Collective GmbH. Before enabling the integration, review:

• Aivie service website
• Aivie Privacy Policy
• Aivie terms and conditions

An administrator can explicitly configure additional tracking services. They are disabled by default and are loaded in the visitor's browser only according to the saved consent settings. The browser sends normal request data, such as its IP address and headers, plus the events and identifiers configured for that provider.

• Google Tag Manager, Google Analytics 4, and Google Ads: load configured Google tags from googletagmanager.com and may send measurement or advertising events to Google and to providers configured inside the GTM container. When Google Consent Mode v2 is enabled, Google may receive denied consent-state signals and cookieless measurements before full consent. The site owner is responsible for every provider and tag installed inside GTM. Review how Google uses information from sites that use its services, the Google Privacy Policy, and Google Terms.
• YouTube: after a visitor accepts the YouTube service, standard WordPress video and playlist embeds load an iframe from youtube-nocookie.com and send normal browser request information plus video interaction data to Google. Review the YouTube Terms of Service, Google Privacy Policy, and how Google uses information from sites that use its services.
• Meta Pixel: loads the Meta pixel from connect.facebook.net and sends the configured page-view and advertising measurement data to Meta. Review the Meta Privacy Policy and Meta Business Tools Terms.
• LinkedIn Insight: loads the Insight tag from snap.licdn.com and sends website-visit and advertising measurement data to LinkedIn. Review the LinkedIn Privacy Policy and LinkedIn Cookie Policy.
• Microsoft Clarity: loads the Clarity tag from clarity.ms and sends configured website-usage and session information to Microsoft. Review Clarity data privacy, the Microsoft Privacy Statement, and Clarity Terms.
• Contentsquare: loads the configured UX Analytics script from t.contentsquare.net only after consent. Review the Contentsquare privacy information and service terms.
• Hotjar: loads the Hotjar tag from static.hotjar.com only after consent and sends configured website-experience and usage information to Hotjar/Contentsquare. Review the Hotjar/Contentsquare privacy information and service terms.

When a user connects WordPress to a ChatGPT custom app and requests a task, WordPress returns the information needed for that task to ChatGPT. This can include site details, post or page content, custom fields, categories and tags, reusable blocks, media details, and images. Requested changes are sent back to WordPress. The user chooses this connection and approves its WordPress access; the plugin does not enable it automatically. Review the provider information that applies to the account or workspace:

• ChatGPT service
• OpenAI Terms of Use
• OpenAI Business Terms
• OpenAI Privacy Policy

When a user connects WordPress to a Claude custom connector and requests a task, WordPress returns the information needed for that task to Claude. The possible data categories are the same as those listed for ChatGPT above. Requested changes are sent back to WordPress. The user chooses this connection and approves its WordPress access; the plugin does not enable it automatically. Review the provider information that applies to the account or workspace:

• Claude service
• Anthropic Consumer Terms of Service
• Anthropic Commercial Terms of Service
• Anthropic Privacy Policy

Other compatible AI assistants can receive the same task-dependent WordPress data. Review the selected provider's service description, terms, and privacy policy before connecting it. Disable MCP or revoke all connections when assistants should no longer have access. During an MCP connection, the plugin may contact the secure identification and signing-key addresses supplied by the client. WordPress uses these requests to verify the client and where the connection may return. Those addresses receive normal network information from the request, such as the website server's IP address and HTTP headers.

The Aivie site URL is stored in WordPress. The optional editor connection stores its encrypted sign-in details on the WordPress site. Disconnecting removes those details and saved element lists but preserves the Aivie site URL and existing blocks. The consent manager stores the visitor's service choices in a first-party cookie. After acceptance, Aivie tracking is governed by the connected Aivie site's configuration, and each enabled optional provider processes data according to that site's provider configuration. When enabled, form tracking can add form starts and progress to the Aivie contact timeline, and marked-click tracking can add the reporting name and destination URL. It does not collect values entered into form fields. Consent-gated YouTube embeds remain placeholders until the YouTube service is accepted. The optional MCP server stores the connection and session records needed to authenticate clients, keep sessions secure, and prevent duplicate create requests. Approval is requested during each new connection. This release does not store a permanent approval history or security audit log. To limit automated registration abuse, the plugin keeps request counters for one hour. Each counter uses a site-specific, pseudonymous value derived from the network address observed by the server; it does not store the original address. Expired counters are removed automatically. When WordPress debugging is enabled, the plugin can write limited connection diagnostics to the debug log. Sensitive sign-in secrets and complete request URLs are excluded. Site owners should describe their Aivie site, tracking configuration, connected AI providers, retention practices, and legal basis in their own privacy notice where required.

Aivie is a Swiss marketing automation platform for managing contacts, campaigns, forms, and personalized customer journeys. Learn more at aivie.ch.

An administrator first saves the Aivie site URL used for tracking and blocks. An optional, read-only editor connection adds searchable element pickers. Its sign-in details are stored encrypted on the WordPress site.

Forms, Focus items, and Dynamic Content are loaded only when published. Existing Tags are loaded from Aivie without a publication filter. Authenticated editor integrations can access these elements through this site's REST proxy. The connection uses five read-only Aivie API scopes for Forms, Focus items, Tags, Dynamic Content, and Themes. An administrator can explicitly fetch customer CI defaults into the consent-banner form, adjust them, and save the resulting values in WordPress.

An Aivie account and its site URL are required for tracking and Aivie marketing elements. The editor connection is optional, and manual IDs or names can be entered where available. The optional AI content tools work directly with WordPress and do not require an Aivie account.

Yes. Tracking and the consent banner have separate switches under Settings > Aivie. Form and click reporting to Google Tag Manager and Aivie can also be switched off independently under Form Tracking. The MCP server has its own independent switch.

Site Kit is optional. Aivie can load Google Analytics, Google Ads, or Google Tag Manager itself, so Site Kit is not required for consent or tracking. If you do not need Site Kit's WordPress dashboards or its other features, you can remove it. For the simplest setup, keep Site Kit only for reporting and let Aivie place the browser-side tags:

1. In Site Kit > Settings > Connected Services > Analytics > Edit, turn off Place Google Analytics code.
2. If Tag Manager is connected in Site Kit, turn off Let Site Kit place code on your site.
3. Turn off Site Kit's own Consent Mode under Site Kit > Settings > Admin Settings so only Aivie manages Google consent.
4. Under Settings > Aivie > Tracking, enable Google Analytics 4 and enter the same G-... Measurement ID shown in Site Kit. Enable Google Ads and enter its AW-... ID only when Ads is used.
5. Leave Google Tag Manager disabled in Aivie unless the site actually uses a GTM container.
6. Choose whether to enable Google Consent Mode v2 in Aivie. Leave it off to block all Google tag requests until acceptance. Turn it on only when limited requests without cookie storage are wanted before acceptance.

No. It provides consent controls and prevents configured services from starting before the applicable acceptance, except for the optional denied-mode behavior clearly described for Google Consent Mode v2. The site owner remains responsible for removing duplicate tags and for the complete legal and technical configuration.

No. Content generation happens in the AI assistant selected by the user. The plugin only provides the approved WordPress tools needed to complete the requested task.

The assistant must support remote MCP connections and secure browser sign-in. Examples include ChatGPT custom apps and Claude custom connectors when the user's plan and workspace enable those features.

No. The plugin provides only its documented content tools, and WordPress applies the permissions of the user who approved the connection. For the safest setup, connect with a WordPress account that has only the permissions needed for the intended work.

Only when the request explicitly confirms the live change. Publishing a post or page also requires explicit confirmation. WordPress permissions continue to apply.

Yes. Disable the MCP server under Settings > Aivie > MCP. To invalidate every existing connection, select Reset OAuth keys and revoke all connections on the same screen.

The MCP server exposes these controlled WordPress tools:

• aivie-mkt/post-list
• aivie-mkt/post-get
• aivie-mkt/taxonomy-search
• aivie-mkt/taxonomy-suggest
• aivie-mkt/taxonomy-create
• aivie-mkt/post-create
• aivie-mkt/post-update
• aivie-mkt/post-featured-image-set
• aivie-mkt/post-author-set
• aivie-mkt/post-publish
• aivie-mkt/page-list
• aivie-mkt/page-get
• aivie-mkt/page-create
• aivie-mkt/page-update
• aivie-mkt/page-publish
• aivie-mkt/content-type-list
• aivie-mkt/content-item-list
• aivie-mkt/content-item-get
• aivie-mkt/content-taxonomy-search
• aivie-mkt/content-item-create
• aivie-mkt/content-item-update
• aivie-mkt/content-item-featured-image-set
• aivie-mkt/content-taxonomy-create
• aivie-mkt/reusable-block-list
• aivie-mkt/reusable-block-get
• aivie-mkt/media-list
• aivie-mkt/media-upload
• aivie-mkt/media-upload-local-file

This site accepts Client ID Metadata Document (CIMD) clients and Dynamic Client Registration (DCR) public clients. Access is granted only after a WordPress user approves it.

No. Activate the plugin separately for each site in a multisite network. Network-wide activation and network administration are not supported in this release.

The consent-management feature is based on tarteaucitron.js 1.37.0. The library is bundled and self-hosted by this plugin under the MIT License. Its human-readable source files, minified runtime files, copyright notice, license, and pinned version are included with the distributed assets.

This plugin is licensed under GPLv2 or later. Aivie is a trademark of Idea 2 Collective GmbH. Mautic is an open source marketing automation project. OpenAI, ChatGPT, Anthropic, and Claude are the property of their respective owners; their names are used only to describe compatible external clients and do not imply endorsement. Human-readable block source and build instructions are included in the plugin's blocks directory. Human-readable source for the bundled tarteaucitron.js runtime is included beside its minified files and is also available from the versioned upstream link above.