• Replies 2 replies
  • Subscribers 961 subscribers
  • Views 249 views
  • Users 0 members are here
Related

iFrame widget functionality

Nathanael Pearson
$organization

I wasn't able to find any documentation on iFrame widgets. My understanding is that they can be used to pull a webpage into a dashboard.

How do they work? Are there limitations on which types of webpages can be pulled in? Some urls appear to work, and others don't, even looking at only image sources.

Is there any pre-built documentation, or best practices?

Parents
  • $organization

    Hi Nathanael,

    The widget doesn't have documentation in the help system at the moment (an oversight). I can offer a few thoughts however:

    • Analytics is served as HTTPS content and will block the display of insecure HTTP content in an iFrame, so use HTTPS URLs in the iFrame widget configuration.
    • Many sites will refuse iFrame requests using an "X-Frame-Options" setting on their site set to "sameorigin", which restricts their webcontent from being rendered on other websites.
    • Configuring an iFrame widget with a URL that requires login may open without login for you or some additional users who have already logged in and have their session key stored in a cookie, however, others may be presented with a login screen and not have the access you expect.

    Generally, issues are made fairly clear when Developer Tools are open to the Console while the iFrame widget in Analytics is rendering. E.g. here's a couple instances set to render the issues associated with the first two bullets above:

    Best,
    Chris

Reply
  • $organization

    Hi Nathanael,

    The widget doesn't have documentation in the help system at the moment (an oversight). I can offer a few thoughts however:

    • Analytics is served as HTTPS content and will block the display of insecure HTTP content in an iFrame, so use HTTPS URLs in the iFrame widget configuration.
    • Many sites will refuse iFrame requests using an "X-Frame-Options" setting on their site set to "sameorigin", which restricts their webcontent from being rendered on other websites.
    • Configuring an iFrame widget with a URL that requires login may open without login for you or some additional users who have already logged in and have their session key stored in a cookie, however, others may be presented with a login screen and not have the access you expect.

    Generally, issues are made fairly clear when Developer Tools are open to the Console while the iFrame widget in Analytics is rendering. E.g. here's a couple instances set to render the issues associated with the first two bullets above:

    Best,
    Chris

Children