How to Request Addition of Customer Domains to Metabase Embed Allowlist

Overview

When a customer hub is hosted on a custom domain, the Metabase dashboards embedded in the Insights Hub tab may fail to load due to restrictive frame-ancestors or X-Frame-Options headers. These headers prevent the content from being embedded in iframes on unrecognized domains. This is not within the scope of SaaS support and must be routed to the appropriate Business Unit (BU) contact for allowlist changes.

Solution

To request that a customer's custom domain be added to the Metabase embed allowlist, follow these steps:

1. Do not create a SaaS incident. SaaS has confirmed this task is out of scope.

2. Open a side conversation from Kayako to the appropriate BU contact:

   • To: Omar.Ortiz@trilogy.com (Owner for General BU Inquiries)

   • Subject suggestion:

     Insights Hub – Metabase embed domain allowlist for <Customer Name> (<custom-domain>)

3. Include the following information in the side conversation message:

   • Customer organization name

   • Primary contact name and email (from the original ticket)

   • Kayako ticket ID (e.g., 60276791)

   • Hub URLs:

     • Default hub URL (e.g., <hub>.influitive.com)

     • Custom domain URL (e.g., https://portal.advocacymaven.com)

   • Symptom:

     Error: ragged-aboard.metabaseapp.com refused to connect. Path: /corporate/metabase_dashboards when clicking Insights Hub.

   • Your triage findings:

     • Confirm that the hub runs on a custom domain.

     • Confirm the Metabase request returns HTTP 200 but with restrictive frame-ancestor or X-Frame-Options headers.

     • (Optional) Confirm that direct access to https://insight.influitive.com loads dashboards correctly.

4. Explicitly request the domain to be allowlisted:

   Example message to include:

   We have confirmed that for <Customer Name> on <custom-domain>, the Insights Hub /corporate/metabase_dashboards route shows “ragged-aboard.metabaseapp.com refused to connect.” The Metabase host responds with HTTP 200 but its frame-ancestors/X-Frame-Options headers do not include this hub’s custom domain, so the browser blocks the iframe. Direct access to https://insight.influitive.com with the customer’s Metabase account appears to work. Please add the customer’s hub domain(s) below to the Metabase embed allowlist so their Insights Hub tab can load dashboards correctly:

Reference Documentation

• Influitive Routing Table - Influitive Support