Tracking & Integrations

How Third-Party Apps Are Integrated in Duda

By Hibu • February 9, 2026
This definition explains how third-party apps integrate into Hibu One Smart Sites using Duda’s client-side capabilities. It outlines supported embed methods, code types, and platform constraints to clarify what is technically possible without backend or plugin-based integrations.

Preferred Third-Party Widgets

By Hibu • February 9, 2026
This definition outlines commonly recommended third-party widgets that embed cleanly with Hibu One Smart Sites. It provides Sales and teams with a centralized reference for scheduling, chat, forms, maps, calculators, reviews, and limited real estate tools, with clear ownership expectations.

Google Tools & Tracking

By Hibu • February 1, 2026
Google Tools connect a Hibu One Smart Site to services like Analytics, Ads, Tag Manager, and Search Console for tracking and performance insights. Clients provide their own IDs, which are added through the Google Tools tab in Duda. Hibu does not create or manage Google accounts but supports multiple tracking codes runn

Third-Party HTML Widgets

By Hibu • February 1, 2026
Widgets are small code-based tools that add interactive features like chats, reviews, or forms to a Hibu One Smart Site. Hibu supports client-supplied code through approved HTML areas but does not create, debug, or manage third-party widgets. Only secure, HTTPS-based scripts are allowed, and full IDX/MLS integrations a

UTM-Tagged URLs

By Hibu • February 1, 2026
Hibu One supports full UTM-tagged URLs exactly as provided. We add the tracking URL—and GTM if supplied—but all testing, validation, and troubleshooting of analytics, triggers, and reporting is the client’s responsibility once installed.

Reviews Widgets: Display Rules, Sources, and Placement Standards

By Hibu • February 1, 2026
Reviews display in the header, homepage, category pages, and right gutter only when a client has 3+ reviews and a 4.0+ rating. The Reviews page shows all sources in chronological order. Yellow stars are standard, and removing reviews may reduce conversion.

Google Tools & Tracking

Definition

Google Tools allow clients to connect their Hibu One Smart Site with Google services such as Analytics, Ads, Tag Manager, and Search Console to track site activity and measure performance. All tracking is added through the Google Tools tab in Duda, under SEO & Settings.

Supported Tracking Codes

Hibu supports client-supplied IDs for the following Google services:

  • Google Analytics – Global Measurement ID (G-) or UA Property ID (UA-)
  • Google Ads – Conversion ID (AW-*)
  • Floodlight / DoubleClick – Tracking ID (DC-*)
  • Google Tag Manager (GTM-*) – ID for managing tags
  • Google Search Console – Verification meta tag (client supplies code)


Placement in Duda

  • All IDs and codes must be added in the Google Tools tab under SEO & Settings.
  • If a client submits a meta tag (e.g., Search Console verification), build teams should extract the verification code and place it in Google Tools — not in the Head HTML.
  • Never paste full      <meta>       tags into the site code. Always use the Google Tools fields.


Rules and Limitations

  • Hibu will not create or manage Google accounts (Analytics, Ads, Tag Manager, or Search Console). Clients must provide their own IDs.
  • Google Analytics anonymizes IP addresses by default, in line with privacy best practices.
  • Google supports multiple tracking codes per site, so client IDs and Hibu’s internal tag can run together without conflict.
  • Tracking codes only function on published/live sites — they will not work on proofs.
  • If tracking appears broken, common causes include:
  • Site not yet published
  • Ad blockers preventing data collection
  • Setup within the past 24 hours (may not be active yet)

Internal Note (Transparency)

For internal testing and performance monitoring, Hibu includes its own Google Analytics tracking ID on every site.

  • This ID is aggregated across all Hibu websites.
  • Data from Hibu’s internal tag is not shared with clients.
  • This setup does not interfere with client-supplied IDs.

Third-Party HTML Widgets

Definition

A widget is a small application or code snippet (HTML, CSS, or JavaScript) that can be embedded into a webpage to display features such as chat, reviews, calculators, or forms. Widgets are supported on Hibu One Smart Sites. Plugins, which require backend access (such as WordPress plugins or IDX/MLS feeds), are not supported.


Hibu One Smart Site Rules

  • Hibu can add client-supplied third-party code into:
  • Head HTML — for critical styles or scripts that must load before content.
  • Body End HTML — for most non-essential scripts, such as analytics, tracking, or chat.
  • This is the preferred placement because it improves performance and avoids conflicts.
  • Content body or Footer — using the HTML widget for visible, interactive elements (e.g., maps, video embeds, social feeds).
  • When adding code to Head HTML or Body End HTML, it is mandatory that Build team adds comment tags for clarity
  • Hibu will not:
  • Set up accounts, retrieve, or generate third-party code.
  • Debug, maintain, or guarantee functionality of client-supplied code.
  • Add code to the site header on behalf of the client.
  • All third-party code is client-owned, and clients must contact the provider directly for support.


IDX / MLS Feeds

  • Full MLS/IDX integrations are not supported due to platform limitations, real-time update requirements, and compliance restrictions.
  • Embeddable IDX widgets (e.g., iHomefinder, IDX Broker Lite, RealBird) may be added, but functionality is limited and SEO benefit is minimal.


Important Limitations

  • Only add code from trusted sources.
  • All code must load securely over HTTPS.
  • Server-side scripts (PHP, ASP) are not supported.
  • Do not attempt to overwrite system libraries (e.g., jQuery).
  • Adding third-party code can slow down page load times and may affect overall site performance.
  • Faulty or incompatible code may cause widgets to stop working or become inaccessible; in that case, the widget may need to be removed.