How do I embed an interactive chart in Confluence?
Quick answer
On Confluence Cloud, use the built-in Iframe macro: type /iframe on the page, paste your chart's public HTTPS URL, and set an explicit height. The catches are that the iframe will not resize itself, your Confluence admin may need to allowlist the chart's domain, and script-based embeds usually need the separate HTML macro, which on most instances is a Marketplace app your admin controls. On Confluence Data Center or Server the steps differ, so confirm which one you are on first.
The fastest way to put a live, interactive chart on a Confluence page is the Iframe macro: on Confluence Cloud, type /iframe in the editor, paste the chart's public HTTPS URL, give it an explicit height, and publish. That covers most cases. The reasons it sometimes fails are specific to Confluence, and to the fact that Confluence is usually an internal, governed tool rather than a public website - which is what this guide is really about.
Cloud, Data Center, or Server - check first
Confluence comes in more than one flavor and the embed path differs. Confluence Cloud ships a native Iframe macro and a set of smart-link behaviors. Confluence Data Center and the older Server product do not have the same native iframe support out of the box and often rely on an administrator-installed HTML macro app. Before you follow any set of steps, confirm which you are on - the version usually sits in your site's footer or under the help menu - because a tutorial written for Cloud will send a Data Center user hunting for a macro that is not there.
The Iframe macro, step by step
On Cloud, open the page for editing and type /iframe, or use the Insert menu and search for iframe. A panel opens asking for the URL and the dimensions. Paste the chart's HTTPS address, set a width - full width is usually right for a research page - and set a height in pixels. Publish the page and the chart renders inline, fully interactive, so a reader can hover and read values without leaving Confluence. That is the entire happy path; the rest is the things that quietly break it.
The iframe will not size itself
An iframe holds whatever height you give it and does not grow to fit its contents. Set it too short and your chart is clipped behind an inner scrollbar; set it too tall and there is dead space below it. There is no auto-fit, so choose a height that matches the chart's natural aspect ratio and test it at the widths your readers actually use. A chart designed to be responsive still needs the iframe around it to be given a sensible height - the responsiveness inside the frame cannot rescue a frame that is the wrong size.
Domain allowlisting and the HTML macro
Two governance details trip up Confluence embeds in a way they never trip up a personal blog. First, some Confluence configurations restrict which external domains an iframe may load, and an administrator may need to add the chart's domain to an allowlist before the macro will render anything. Second, if your chart is a script-based embed rather than a plain URL - a snippet you would normally drop into a page's HTML - the Iframe macro will not run it, and you need the HTML macro instead. On most Cloud and Data Center instances the HTML macro is a Marketplace app that an admin installs and configures, not a default feature, precisely because running arbitrary HTML on an internal wiki is a security decision. If the macro is missing, that is a request to your Confluence admin, not a bug. A self-hosted chart exposed as a simple HTTPS page sidesteps all of this - the plain Iframe macro handles it.
HTTPS and the preview trap
Two smaller catches. Confluence pages are served over HTTPS, so an embed loaded over plain HTTP is blocked as mixed content and shows nothing; make sure the chart URL starts with https. And the editor preview is not the published page - a macro can look different, or fail to render, in the draft view and then work once you publish, or the reverse. Always publish and view the live page, ideally as a colleague with normal space permissions, before you trust the result.
Who can actually see it
Because Confluence is permissioned, an embed is only as visible as the page and space around it. A chart on a restricted space is invisible to anyone without access, which is usually what you want for internal research and board material but a genuine surprise if you meant to share it more widely. And the embed points at a live external URL, so viewers see whatever the chart shows at the moment they load the page - fine for a dashboard you want current, worth a static snapshot instead if the page is meant to be a record of a specific date.
Confluence is the internal-research end of the same embed pattern behind the HubSpot, WordPress and Notion guides - the mechanics rhyme, the governance is stricter. Quadesto charts are self-hosted at a public HTTPS URL, which is the form the plain Iframe macro handles without a Marketplace app: build the view, copy the link, drop it into /iframe. [QUADESTO-EMBED: interactive research chart, self-hosted HTTPS URL for the Confluence Iframe macro, fixed height set for a full-width wiki page]. The free tier embeds it live with a Made with Quadesto credit; Pro (149 pounds a month) removes the attribution and adds branded themes.