Finsweet Instagram Component Not Fetching Data

Finsweet Components Instagram Feed
1

Description

The Finsweet Instagram Feed component is not rendering on the live site despite being correctly configured in the Finsweet app. The component HTML is present in the published page source (66 instances of fs-instagramfeed found), the access token is saved successfully in the app dashboard, and the feed preview displays correctly inside the Finsweet app panel. However, the fs-components script never makes any network requests on the live site and the feed remains as placeholder content.

Site URL

Required: https://www.rockethq.co.uk/

Steps to Reproduce

    1. Visit the website above on any browser
    2. Open browser DevTools and go to the Network tab, filter by Fetch/XHR
    3. Reload the page and observe that no requests are made to fs-components, instagram, or graph .facebook.com
    4. Inspect the Instagram feed section — the component renders as placeholder content only
    5. View page source and search for fs-instagramfeed — the HTML is present but the script does not initialise

Expected Behavior

The Finsweet Instagram Feed should fetch posts from the connected Instagram account and render them in the grid on the live site, replacing the placeholder content.

Actual Behavior

The feed remains as placeholder content on the live site. The fs-components script loads in the page source but makes no network requests and does not initialise. The current script output shows the integrationId field is empty despite the access token being saved successfully in the app:

integrationId: “”
integrationType: “token”
siteId: “6864fdd5c563b40d698c7be5”
showOnPage: “true”

The access token was reconnected multiple times and the site was fully republished after each attempt. The domain www.rockethq .co.uk was recently migrated, and a new siteId (6864fdd5c563b40d698c7be5) appears to have been generated during this process. It is unclear whether the Instagram token is correctly linked to this new siteId.

Video/Screenshots

finsweet-error
finsweet-error1898×1052 17.2 KB

This is with the fs-instagramfeed_styles css removed:

/\* Hide Instagram feed elements by default until they are loaded \*/ \[data-wf-domain\] \[fs-instagramfeed-instance\] {opacity: 0;} /\* Limit the description to only 3 lines \*/ \[fs-instagramfeed-instance="fs-instagramfeed"\] \[fs-instagramfeed-element="caption"\] { }

Additional Context

    • Browser: Chrome (latest)
    • Device: Desktop
    • The component HTML is published correctly — fs-instagramfeed appears 66 times in the page source
    • The Finsweet app preview shows the correct Instagram feed for the Rocket account
    • No Finsweet-related errors appear in the browser console — only unrelated GSAP and Vimeo CORB warnings
    • The site was recently migrated to a new domain (www.rockethq.co.uk) and the Finsweet app was reinstalled during troubleshooting
    • integrationId is empty in the published script output despite token being saved in the dashboard
2

Hey @harvey!

We checked your setup and your HTML implementation is absolutely correct — all 66 instances of the Instagram Feed have the right fs-instagramfeed-* attributes, and your component structure is solid. So the good news: you’ve done the implementation work perfectly. :flexed_biceps:

Now, here’s what the symptoms point to:

Based on a previous verified case with a similar feed component, the pattern you’re seeing (correct HTML, no network requests, placeholder content only, but the preview works in the Finsweet app) almost always indicates a licensing/subscription issue rather than a setup problem.

When sites migrate to a new domain, the subscription connection sometimes needs to be re-established for the new domain. The empty integrationId field you’re seeing, combined with the behavior, suggests the Finsweet Components subscription may not be properly linked to your new custom domain (www.rockethq.co.uk) after the migration.

Here’s the diagnostic step to confirm this:

Could you test the Instagram Feed on your .webflow.io staging URL? If the feed loads there, it definitively confirms this is a subscription/domain linkage issue (Components work free on staging, but need an active paid plan for custom domains).

If the feed works on .webflow.io:

  1. Check your Finsweet dashboard subscription settings
  2. Make sure your custom domain (www.rockethq.co.uk) is properly connected to your Components subscription
  3. If you’re not sure where to find the domain linking option or if you had a subscription before the migration, we’ll loop in @Support-Luis or @Support-Pedro to help verify the subscription is correctly linked to the new siteId

If the feed ALSO doesn’t work on .webflow.io:

That would point to a different root cause than expected, and we’ll escalate this immediately to investigate.

Let us know what you find with the .webflow.io test — that’ll tell us exactly what’s happening! :folded_hands:

3

Hi Finn. Thanks for your detailed response. I have checked this morning and the problem seems to have resolved itself. I cannot say for certain what the solution was, only that the feed now correctly displays on the live site.

4

Thanks for the update @harvey
Glad it got sorted!