Tagembed social-media aggregator

Webflow pages show what you last published. Social posts and campaign UGC pile up on Instagram and LinkedIn. Google reviews pile up too. Reaching your site requires a manual edit and a republish. Tagembed closes that gap.

Connecting Tagembed with Webflow puts an auto-updating widget inside any page. You build and moderate the feed in the Tagembed dashboard, then generate an iFrame or JavaScript snippet. Paste it into a Code Embed element. The widget then refreshes on its own, so the page stays current without another publish.

This integration fits marketers who need fresh site content without developer time. It also fits event teams running hashtag campaigns and e-commerce brands turning customer posts into shoppable galleries. B2B teams use it to put company LinkedIn feeds on their homepages. Agencies benefit too, since Tagembed's dashboard manages widgets across unlimited client sites.

How to integrate Tagembed social-media aggregator with Webflow

What is Tagembed social-media aggregator? Tagembed is a social media aggregator and website widget platform. Its 20+ source platforms include Instagram, LinkedIn, X, TikTok, and YouTube. It also pulls review sources such as Google and Yelp. Moderation and styling controls are built in, and content updates automatically.

Teams reach for this pairing when a page needs content that changes faster than an edit-and-publish cycle. An event page fills with attendee posts during the event itself. A testimonial page picks up new Google reviews as customers leave them. In both cases the widget refreshes on Tagembed's schedule while the Webflow page stays untouched.

The Tagembed-Webflow integration supports three approaches:

• The Code Embed element places the widget in a specific spot on a page. Setup is pasting one generated snippet.
• Custom code in head and body tags loads the widget script across the whole site or on a single page. You manage it in site or page settings.
• An unsupported custom architecture using the Webflow Data API and Tagembed API can provide programmatic control over script registration and feed content, but Tagembed's public endpoint documentation is deprecated and the approach requires server-side development.

Most setups use the Code Embed element alone. Add site-wide custom code when the widget script must load on every page. Treat API work as unsupported custom infrastructure. Neither company documents it as a Tagembed-Webflow integration.

Add a Tagembed widget with a Code Embed element

Pasting Tagembed's generated code into a Code Embed element is the only documented integration path. It covers the documented widget types: Social Widget, Shoppable Gallery, Review Widget, Story Widget, and Album Widget. Code embeds need a paid Site plan or a Core, Growth, Agency, or Freelancer Workspace. The free Starter plan does not include them. Tagembed documents this flow across its Webflow guides, including the Webflow setup guide. You don't write code on either side.

To set up the integration:

1. Log in to Tagembed and click Content Gallery in the left sidebar. Select a social network, authenticate the account, and click Create Feed.
2. Set the layout in the Theme tab, then adjust colors, cards, and fonts in the Customization tab.
3. Click Publish in the left sidebar and choose Website.
4. Click Generate Code, set the platform, width, and height, then copy the code.
5. In Webflow, open the Add panel, go to Advanced, and drag a Code Embed element to the spot where the widget should sit.
6. Paste the code into the element, save, and publish the site.

You configure everything in the Tagembed dashboard before copying the code:

• Themes, layouts, background, banner, card style, fonts, and CTA buttons
• Manual moderation, auto-moderation rules, a profanity filter, and a ratings filter
• Automatic content updates and responsive sizing for any screen
• Custom CSS through More > Custom CSS in the widget dashboard

Tagembed's guides use inconsistent labels for the platform selector. Tagembed's guides variously label it Webflow, HTML, Other, or Webflow (Other). Every option generates functionally equivalent embed code. The Code Embed element accepts up to 50,000 characters. It supports HTML plus CSS in <style> tags; JavaScript must appear in <script> tags.

Load the widget through site-wide or page-level custom code

Tagembed's JavaScript embed code can also be placed in the built-in Custom code in head and body tags fields. Use this path when the widget script should load on every page. It suits teams who prefer managing code in settings rather than on the canvas. The same paid-plan requirement applies here as with the Code Embed element.

Add the script to a single page

Page-level custom code applies only to that page and appears after any site-wide custom code.

To add the code to one page:

1. Open the Pages panel and click Page settings for the target page.
2. Under Custom code, paste the Tagembed snippet into the Inside <head> tag or Before </body> tag section.
3. Click Save changes and publish.

Each of these sections carries the same 50,000-character cap as the Code Embed element.

Add the script site-wide

Site-wide custom code loads on every page of the site. Footer code appears right before the closing </body> tag.

To add the code site-wide:

1. Open Site settings and go to the Custom code tab.
2. Paste the snippet into the Head code or Footer code section.
3. Click Save changes and publish.

These fields support HTML and CSS; they also support JavaScript. Server-side languages such as Perl, PHP, Python, or Ruby will not run in any code section.

Understand the Webflow and Tagembed APIs

The API path is narrow and amounts to unsupported custom infrastructure. Tagembed's v1 API documentation states "These API have been deprecated on 31st October 2022." Tagembed advertises API access on its Enterprise plan, but its available public endpoint documentation is legacy and deprecated, and Tagembed publishes no webhooks. Webflow's Data API v2 is Webflow's current API version, and it supports both custom code registration and Webflow CMS writes. That leaves only a hypothetical server-side pattern: a Data Client app, which is an OAuth app that calls the Webflow Data API on a user's behalf. The app can manage the embed script or, if Enterprise Tagembed API access is available, poll Tagembed posts on a schedule.

API responsibilities and constraints differ between Tagembed and Webflow.

• The Tagembed API is Enterprise-plan only. Its publicly documented filters for network, post count, and post ID range come from deprecated legacy v1 endpoints and should be treated only as reference material; their current status is unverified.
• Webflow's Data API v2 handles custom code registration, Webflow CMS collection items, and site publishing at https://api.webflow.com/v2.
• Webflow webhooks fire events such as collection_item_created and collection_item_changed for anything that writes into the CMS.

Tagembed sends no webhooks, so any hypothetical Tagembed-to-CMS sync would have to poll Tagembed on a schedule and depend on Enterprise access to endpoints whose available public documentation is deprecated. Writes would go through POST /v2/collections/{collection_id}/items. That pattern is unsupported custom infrastructure you own; neither company documents or endorses it.

Register the embed script with the Data API

A Data Client app can place Tagembed's embed script on a site programmatically, without opening the canvas. Only Data Client apps get the custom_code:read and custom_code:write scopes. Site tokens will not work here. Scripts register once, then get applied at the site or page level.

To register and apply the script:

1. Register inline JavaScript with POST https://api.webflow.com/v2/sites/{site_id}/registered_scripts/inline (2,000 characters max, no <script> tags). For an externally hosted script URL, use POST https://api.webflow.com/v2/sites/{site_id}/registered_scripts/hosted.
2. Apply it with PUT https://api.webflow.com/v2/sites/{site_id}/custom_code for the whole site, or PUT https://api.webflow.com/v2/pages/{page_id}/custom_code for one page.
3. Push it live with POST https://api.webflow.com/v2/sites/{site_id}/publish.

Registered script versions are immutable, so ship changes by registering a new version. If your build also calls the Tagembed API, keep your Tagembed API key on the server. Tagembed's documentation says to store it in environment variables and never in client-side code or public repositories.

What can you build with the Tagembed Webflow integration?

Integrating Tagembed with Webflow lets you run live social feeds and review sections alongside UGC galleries on any page without manual content edits or repeated publishing.

• Event hashtag wall: Collect attendee posts under a campaign hashtag and display them on the event landing page on Tagembed's plan- and platform-dependent refresh schedule. Tagembed's own example is an organizer aggregating every post tagged #ChristmasEvent2025 into a single wall.
• Review section for a services business: Pull Google, Facebook, or Yelp reviews into one widget on a testimonial page. Tagembed's blog shows WealthCare Financial running a Google Review List on a dedicated "Client Testimonial" page. The same widget type embeds on a Webflow page.
• Shoppable UGC gallery: Turn customer Instagram or TikTok posts into a gallery with product tagging and hotspot tagging. Place it on a landing or product page. Tagembed documents native catalog sync for Shopify and BigCommerce, but not for Webflow Ecommerce. On Webflow, the gallery is an embedded widget.
• B2B LinkedIn feed: Put company LinkedIn posts on a homepage to show activity without weekly page edits. In Tagembed's PowerPlan case study, a homepage LinkedIn feed added 102 followers and lifted impressions 26% in 45 days.

If you need more control over how widget content reaches your pages, the hypothetical API path requires Tagembed Enterprise access and custom infrastructure. Tagembed's available public endpoint documentation is legacy and deprecated, and the lack of webhooks means a CMS sync would require polling, secure authentication, rate-limit handling, and ongoing maintenance.