Skip to main content

Circle installation

Circle Community Testimonials with Custom Code

Circle gives admins two places for your own HTML: the Custom HTML element in its website builder, for the public page that sells membership, and the Custom HTML field in a post’s settings, for proof inside the community. Each has its own rules about plans, who can edit and what the mobile apps show.

  • Code for a Circle website page
  • Code for a post’s Custom HTML field
  • What members in the Circle app see instead

Code for Circle

Paste into Circle’s Custom HTML spots

Add your widget id. Part 1 goes on a page of your Circle website, usually the page that sells membership. Part 2 goes in the settings of a single post, often one you pin. Both use the full two line embed.

Shown in StoryProof when you copy a widget’s embed code.

Part 1 · A page on your Circle website

Website › Pages › open the page › Elements › drag Custom HTML into place

<div data-storyproof-widget="YOUR_WIDGET_ID"></div>
<script src="https://app.storyproof.io/embed.js" async></script>

Part 2 · Inside one community post

Post editor › Settings (gear) › Custom HTML › Done › Save

<div data-storyproof-widget="YOUR_WIDGET_ID"></div>
<script src="https://app.storyproof.io/embed.js" async></script>

Neither editor previews custom HTML. Publish the page or save the post, then open it in a browser where you are logged in as a member, not an admin, to see what they see.

The widget id stays in this page. Nothing is sent to StoryProof or to Circle.

The problem, solved

Proof on Circle: where it gets lost and how StoryProof helps

  • Problem 1

    Our join page has no proof on it

    Visitors deciding whether to pay for membership cannot see the feed, so the success stories members post never reach them.

  • Problem 2

    Great wins vanish down the feed

    A member’s breakthrough post gets a burst of likes and then sinks under newer posts, so new members never read it.

  • Problem 3

    Members on the app see a button

    In Circle’s mobile apps, custom HTML in a post is not drawn inline. Members get a See attachment button that opens it separately.

  • Problem 4

    A full wall overwhelms a post

    The post area is narrow and the HTML output sits at the bottom of the post, below everything you wrote.

In StoryProof

Set it up in Circle

Step 1 of 5

Choose stories and a layout

In StoryProof, approve the member stories you want and build one widget for the website page and, if you want one, a compact widget for a post.

Website page, post or link?

Behaviour as described in Circle’s help center, read 2026-11-13.
WhereWho sees itWatch out for
Circle website page, Custom HTML elementProspective members on the public pageWebsite builder plan; test after publishing
Post settings, Custom HTML fieldMembers reading that post in a browserShows at the bottom of the post; app users get a See attachment button
Wall of Love link in a post or the menuAnyone, on web or in the appOpens outside Circle

Before you start

Circle limits worth knowing

  • Not in notification emails

    Circle says custom code in a post does not appear in the email notification for that post. Members reading by email will not see the widget.

  • Script behaviour is not documented

    Circle’s articles describe the Custom HTML element and field but do not say how scripts inside them run. Check the published result, and keep the Wall of Love link ready if the box is empty.

  • In app navigation

    Circle fires its own route change event as members move around the community, a sign that pages change without a full reload. If a post widget is empty until you refresh, link to the Wall of Love instead.

  • No Circle integration

    StoryProof is pasted in as HTML; there is no Circle app or connector. Widgets show a "Powered by StoryProof" badge until Pro.

  • Circle help as of 2026-11-13

    Menu names, plan levels and app behaviour come from Circle’s help center and pricing page as read on 2026-11-13. Nobody has yet tried these steps in a live Circle community.

FAQ

Questions people ask

Short answers to what usually comes up next.

Can a moderator who is not an admin add the widget to a post?

Circle limits post custom HTML to admins, on desktop or mobile browsers. Ask an admin to paste it.

Should I use Circle’s Code snippets setting instead?

Code snippets under Website add head code and tracking style JavaScript across the site. The widget also needs its div in a page or post, so the Custom HTML element or field is the place for this embed.

Can members submit a testimonial without leaving Circle?

They open your StoryProof collection link from a post or a menu item and record a video, an audio note or a written review in the browser. That opens outside Circle.

Will the widget slow the community feed?

Only the page or post that holds the custom HTML loads it. The rest of the feed is untouched.

Still have a question? Ask the StoryProof team or book a demo.

Turn member wins into proof

Collect stories, approve them and paste one widget into your Circle website page.

Sources

  1. Embed custom HTML code within posts, Circle Help Center. Checked 2026-11-13.
  2. Customize elements and blocks, Circle Help Center. Checked 2026-11-13.
  3. Create a page, Circle Help Center. Checked 2026-11-13.
  4. Custom code snippets, Circle Help Center. Checked 2026-11-13.
  5. Track page transitions within your community, Circle Help Center. Checked 2026-11-13.
  6. Pricing (Website included from Professional), Circle. Checked 2026-11-13.

Last updated 2026-11-13.