Content Hub

Managing Cloud Platform Filters


Content Hub 2.x will reach end-of-life on December 31, 2024. Acquia recommends that you update your Content Hub version to Content Hub 3.x by using the composer require instructions available on the acquia_contenthub project page.

Cloud Platform Filters in Content Hub are stored Elasticsearch queries which act as filters for content. Cloud Platform Filters associate with a given webhook, which is a local endpoint in your website which sends and receives information flowing to and from Content Hub.

Administrators can use Cloud Platform Filters to control and restrict the information sent from Content Hub to those webhooks according to their search results. You may associate one or more Cloud Platform Filters to any particular webhook. The publishing website controls the management of Cloud Platform Filters and their association with the webhooks. Administrators can use this association to control the information flow to all subscribing websites.

Enabling Cloud Platform Filters

To view your website’s Cloud Platform Filters in your Content Hub publishing website:

  1. Sign in to your Drupal publishing website as a user with administrative permissions.
  2. In the Admin menu, go to Extend.
  3. Select the Acquia Content Hub Curation checkbox.
  4. Click Install.

Managing Cloud Platform Filters

Use the Content Hub discovery interface to create Cloud Platform Filters for content existing in Content Hub.

You must assign a Cloud Platform Filter to a website before the content restriction will take place.

The discovery interface will display all available Cloud Platform Filters.

Creating a Cloud Platform Filter

To create a new Cloud Platform Filter in Content Hub:

  1. In your Content Hub publishing website, go to Content > Acquia Content Hub.
  2. Select one or more Cloud Platform Filters. In the discovery interface, you can filter content by selecting from the following criteria:
    • Keywords
    • Created Date
    • Source
    • Tag
    • Type
    • Bundle
  3. Click Save filter. Content Hub will display the Save New Filter dialog box.
  4. Enter a name in the Saved filter name field, and then click Save filter.
  5. Click Assign Sites. A list of websites with registered webhooks displays.


    Webhooks which aren’t enabled are grayed out in the interface and can’t be assigned to a filter.

  6. Select the checkbox for each webhook the Cloud Platform Filter applies to. You may select more than one subscribing website at a time.
  7. Click Save filter.

Editing a filter

Selecting an existing Cloud Platform Filter loads the current saved criteria the filter uses. To edit a filter’s criteria:

  1. In your Content Hub publishing website, go to Content > Acquia Content Hub.
  2. Click Saved Filters.
  3. Click the Cloud Platform Filter whose criteria you want to edit.
  4. Add or remove filtering criteria as required.
  5. Click Save filter.

Deleting a filter

To delete a Cloud Platform Filter:

  1. In your Content Hub subscribing website, go to Content > Content Hub.
  2. In the left menu, click Saved Filters.
  3. Click the filter you want to delete, and then click Delete filter.
  4. In the Delete saved filter confirmation dialog box, click Delete filter.

Assigning more than one Cloud Platform Filter to a website

Any website (or webhook) can have more than one Cloud Platform Filter assigned to it, but content matching any Cloud Platform Filters will be sent to the subscribing website.

Understanding the default Cloud Platform Filter

Registering a new client and webhook with Content Hub creates a default Cloud Platform Filter and assigns it to the webhook. This Cloud Platform Filter’s name is default_filter_[client name] and, by default, will prevent content from being sent to the website.


Websites without a valid SSL certificate must configure their webhooks to use http, not https.

Content administrators must explicitly define specific Cloud Platform Filters on every website to enable them to receive content updates. The default Cloud Platform Filters globally exclude content, which prevents the website from receiving updates to all content created by the publishing website.