Skip to main content
Drupal is a registered trademark of Dries Buytaert
Release: Views Bootstrap 5.5.4 — Minor update available for module views_bootstrap (5.5.4). Release: Rightup theme 1.0.3 — Minor update available for theme vartheme_bs5_rightup (1.0.3). Release: CommentOn 1.0.6 — Minor update available for module commenton (1.0.6). Release: ChatGPT Ads 1.0.3 — Minor update available for module chatgpt_ads (1.0.3). Release: Opensolr Search 5.1.3 — Minor update available for module opensolr_search (5.1.3). Release: ServiceM8 Webform Integration 1.2.1 — Minor update available for module servicem8_webform (1.2.1). Release: PostfixAdmin 1.0.0 — Initial release available for module postfix_admin (1.0.0)! Release: ip_analyser 1.0.3 — Minor update available for module ip_analyser (1.0.3). Module Revived: Swagger-PHP OpenAPI 3 documentation generator 1.0.0 — Module swagger_php updated after 10 months of inactivity (1.0.0). Security Coverage: Microsoft Azure AI — Module ai_provider_azure now has official Drupal security advisory coverage.

Acquia-VWO Connect

Security covered Drupal 9–11
View on drupal.org

Acquia-VWO Connect provides additional Drupal specific settings to allow you to capture content metadata with page views in VWO. Currently supports Content Section, Keywords and Persona field mappings from common content type taxonomies on the site.

Post-Installation

1. Configure the User roles and permissions for Acquia-VWO Connect via menu People > Permissions or visit /admin/people/permissions.
2. Configure the module:
2.1 Navigate to the configuration page via menu Configuration > Acquia-VWO Connect Settings or visit /admin/config/system/acquia_vwo.
2.2 Insert the VWO account ID and submit.
2.3 You can extract the account ID from smart code by clicking the "Extract Account Id" tab.
2.4 Click the Visibility tab. Here you can configure the visibility to show only on specific pages, roles or content types.
2.5. Click the Field Mapping tab. Select which field to use for each segment. You may reuse existing fields or create new vocabularies and new term reference fields for each segment.

Acquia VWO Content Governance

Acquia VWO Content Governance allows you to export content from your Drupal website into VWO as Custom Widgets, which can be used in your VWO campaigns.

  1. Configuring the module
    1. After installing the main Acquia VWO module, install the Acquia VWO Content Governance submodule
    2. Navigate to Configuration > Acquia VWO Connect Settings and select the Content Governance tab. Alternatively, go directly to: /admin/config/system/acquia_vwo/content-settings.
    3. To authenticate the module with VWO, you will need to obtain your VWO API Key from your VWO account. Follow the link provided in the module form. Enter the API Key in the designated field within the module settings. Click Save Configuration to apply the changes.
  2. Configuring Entities
    1. To enable Content Type for VWO Export navigate to Structure > Content Types. Select the content type you want to export (e.g., Article). Click Edit to modify the content type settings.
    2. Within the content type settings, go to Acquia VWO Content Governance Settings. Check the "Make this content type available as Acquia VWO custom widgets" checkbox.
    3. Select the appropriate Render Role and Render View Mode based on your requirements. The default values should work for most cases.
    4. Click Save to apply the changes and ensure the content type is correctly configured for export to VWO.
    5. From this point onwards, when creating or editing an entity of the configured entity type, you will have the option to choose whether it is exported to VWO.

Depends on

Dependencies of the latest stable release

  • node Drupal core
  • taxonomy Drupal core

Required by

Tracked projects that depend on this one

No tracked projects depend on this one yet.

Activity

Tracked releases
4
Tracked since
Jul 2024
Latest release
2 years ago
Releases (12 mo)
0
Maintenance
Dormant

Release Timeline

Releases

Version Type Core Release date
1.0.2 Stable 9–11 Sep 10, 2024
1.0.1 Stable Aug 29, 2024
1.0.0 Stable Aug 29, 2024
1.0.x-dev Dev Jul 10, 2024