Install your embedded research feed

Two tags on one page. A web team can do it in under fifteen minutes, and nothing needs maintaining afterwards: the feed updates itself as new research is published.

This guide covers the embed code, which is what most sites use. If your web team would rather have the JavaScript plugin or the JSON feed, or you want investors to read each note on a viewer page on your own site, we send the instructions for that instead. Compare the options.

Before you start

You need your feed id, which we email you when the feed is set up, and the page you want the feed to appear on. That is usually an investor relations page, something like /investors or /analyst-research. Tell us the domain and we whitelist it; the feed will not render anywhere else.

The code

Replace your-feed-id with the id we sent you. Everything else goes in as it is.

<!-- Research Tree research feed -->
<iframe
    id="portal-frame"
    data-frameMinSize="800"
    data-sourceurl="https://www.research-tree.com/erf/embed/research/your-feed-id?"
    src="https://www.research-tree.com/working.html"
    title="Research Tree Portal Frame"
    width="100%"
    sandbox="allow-scripts allow-same-origin allow-popups allow-popups-to-escape-sandbox"
    style="border: none; overflow: hidden;">
</iframe>

<!-- Must be placed below the iframe above -->
<script src="https://www.research-tree.com/scripts/CorporateWhiteLabelled/embed_v2.js"></script>

Where each piece goes

1. 1. The iframe, where you want the feed

   Put it exactly where the research should appear on the page. It is responsive and takes the width of whatever contains it, so it will fit a full-width section or a narrower column.

2. 2. The script, below it

   Ideally just before the closing </body> tag. It lets the feed expand vertically to show every note, instead of scrolling inside a fixed box.

Three things people get wrong

• The script above the iframe

  The resize script has to sit below the iframe on the page. Above it, the feed cannot grow to fit its content and you get a scrollbar inside a scrollbar. This is the most common one by a distance.

• The page is not on a whitelisted domain

  The feed only renders on domains we have whitelisted, which is what stops anyone else embedding it. If you are testing on a staging domain, tell us and we will add it.

• A CMS stripping the iframe

  Some content management systems remove iframes and script tags from rich-text fields. Paste the code into an HTML or embed block rather than the body editor.

Once it is live

Send us the URL and we will check it renders properly and looks right on a phone. We will also match the colours to your branding at that point if you have not already sent them over.