Frequently Asked Questions

Humblytics is a web analytics, A/B testing and revenue attribution platform for growth teams and agencies. One script connects website behavior, experiments, Meta and Google Ads spend and supported payment-processor revenue so teams can find conversion leaks, test changes and evaluate results against revenue.

Getting started is simple: visit humblytics.com, click "Start Free Trial", create your account, choose a plan (your card won't be charged until the 14-day trial ends), and add the tracking script to your website's <head> section. For Webflow users, you can connect directly through the Webflow App Store with one-click authorization.

Webflow: Connect directly through the Webflow App Store with one-click authorization. Analytics tracking begins automatically.

Framer: Add the tracking code snippet to your site header through site settings.

Custom websites: Copy your unique tracking code from the Humblytics dashboard and add it to your site's <head> section. No additional configuration needed.

For SPAs (React, Vue, Angular), you'll need to manually trigger page view events on route changes. The initial script installation remains the same in your index.html.

1. Install Humblytics alongside GA for 1-2 weeks

2. Map custom events using attributes or small JS helpers

3. Verify accurate tracking and set up events to match your GA configuration

4. Export historical GA data for records

5. Remove GA when comfortable with Humblytics metrics

Historical data won't transfer directly, but you can run both tools in parallel during transition.

Humblytics provides comprehensive tracking capabilities without requiring any coding knowledge. You can monitor page views and see real-time visitor data, along with detailed information about traffic sources and geographic distribution. The platform automatically tracks important engagement metrics such as scroll depth and session duration. For more detailed insights, you can track form submissions, conversion rates, and specific interactions with buttons and links. Our CMS performance tracking helps you understand which content performs best with your audience. All of this happens automatically once you install Humblytics - no additional configuration required.

Personal data: Name, email, billing details during account creation

Automatic tracking: IP (hashed), location, OS, device metadata

Analytics data: Page views, clicks, form submissions, scroll depth

All data is encrypted and anonymized for privacy compliance

Humblytics provides near real-time data:

• Page views: Appear within seconds

• Click events: Show up immediately

• Form submissions: Tracked instantly

• Heatmaps: Update in real-time

• A/B test results: Refresh every few minutes

Add a simple attribute to any HTML element: humblytics="event-name". Events appear in your dashboard under "Clicks" within seconds. No additional code or configuration needed - it's no-code and low-code friendly for platforms such as Webflow and Framer.

Yes. Humblytics supports form tracking from:

• Typeform (embedded submissions)

• HubSpot Forms (auto-detected when embedded)

• HubSpot Booking Links

• Cal.com (calendar bookings)

• Tally.so form submissions

• GoHighLevel (automatic tracking)

• Custom forms with simple attributes

Yes - embedded HubSpot forms are auto-detected. For native HubSpot pages, you need to add the Humblytics script in HubSpot settings. The platform automatically captures form submissions without additional configuration.

Track purchases using the custom event tracking feature. You can also set up purchase events as goals in your A/B tests to measure conversion impact.

Yes, you can track cart abandonment by setting up custom events when users add items to cart vs. when they complete checkout. Create a funnel to visualize the drop-off between cart addition and purchase completion.

No cross-site or deterministic cross-device identity is promised. Humblytics uses a one-way hash of IP and device characteristics for visitor measurement, so the same person on two devices may be counted separately.

Monitor engagement through:

• Session duration: How long users stay on your site

• Scroll depth: How far users scroll on pages

• Click events: Interactions with specific elements

• Return visitor patterns: Frequency of visits

• Funnel progression: Movement through conversion steps

The dashboard Submissions number counts every form submission event fired, not unique people. One visitor submitting twice counts as two submissions, while your CRM usually deduplicates by email into one contact. Test submissions and validation failures can also fire events that never become CRM records.

If you need deduplicated counts, the External Analytics API exposes a unique_submissions metric (distinct sessions that submitted a form). Use the dashboard number for trends and A/B comparisons, and the API metric to reconcile against your CRM. Full explanation at docs.humblytics.com under Understanding Forms Data.

Because clicks count every click event, and one visitor can click many times. That also means CTR can go above 100%: 200 sessions producing 500 clicks is a 250% CTR. It's expected behavior, not a data error.

If you're comparing against GA4: GA4 counts users and events with different definitions, so the numbers won't match one-to-one. Neither tool is wrong; they answer different questions.

• Unique visitors: Anonymous visitors estimated from a one-way hash of IP and device characteristics

• Page views: Total number of pages loaded, including repeat visits

• Sessions: Groups of interactions within a time period

• Bounce rate: Percentage of single-page sessions

Geographic data is inferred from network location and should be treated as approximate, especially at city level or when visitors use VPNs, mobile networks or corporate proxies. Humblytics does not publish a guaranteed geography-accuracy percentage.

Heatmaps activate automatically once the base script is installed - no extra code needed. They provide:

• Dynamic click density overlays for desktop, tablet, and mobile views

• Scroll-depth insights showing where users lose interest

• Page-level filtering to compare different layouts or devices

• Real-time data without sampling

Heatmap best practices:

• Hot spots (red areas): High engagement, popular elements

• Cold spots (blue/no color): Low engagement, consider repositioning

• Compare heatmaps across device types (desktop vs. mobile)

• Use scroll depth data to identify where users lose interest

• A/B test changes based on heatmap insights

Create and run A/B tests without coding knowledge. The platform automatically splits traffic between variations and provides real-time results showing performance for each version, including statistical significance calculations. All split-testing logic is built into the main script.

Choose Split Testing → Start New Experiment

1. Set your testing goal (conversion events or page destinations)

2. Name your experiment clearly

3. Add variant page URLs (control vs. test versions)

4. Set visitor assignment preferences

5. Apply optional restrictions (geo-targeting, audience filters)

6. Launch the experiment

No. Split-testing logic is built into the main Humblytics script. No extra files or libraries needed - one script handles analytics, heatmaps, and A/B testing.

Yes, you can run multiple A/B tests at the same time on different pages or elements. However, avoid testing overlapping elements on the same page as this can affect statistical validity. Humblytics tracks each experiment independently with separate conversion metrics.

Conversion Goals: Form submissions, click events, page view events, purchase events

Page Goals: Reach destination page (internal or external)

All goals support both same-domain and cross-domain tracking.

• Allow Visitor Overlap: Assignment happens per session - repeat visitors could see different versions on different visits. Good for high-traffic sites and short tests.

• No Visitor Overlap: Assignment happens once per user (sticky) - they always see the same version. Better for brand-sensitive flows and long funnels.

For statistically significant results, you typically need:

• Minimum: 100-200 conversions per variant

• Recommended: 1,000+ visitors per variant

• Duration: At least 1-2 weeks to account for weekly patterns

Use Humblytics' A/B testing calculator to determine ideal sample sizes.

Best practices for monitoring tests:

• Daily monitoring: Track progress but avoid making decisions

• Weekly reviews: Assess trends and statistical significance

• Decision point: Wait for statistical significance before concluding

• Avoid: Stopping tests early based on initial results

High-impact elements to test:

• Headlines: Main value propositions

• Call-to-action buttons: Text, color, placement

• Hero images: Product shots vs. lifestyle images

• Form fields: Number and types of fields required

• Pricing presentation: Layout and emphasis

Set up value attribution in your funnels by:

• Assigning monetary values to conversion events

• Tracking revenue-generating actions (purchases, sign-ups)

• Using the per-step value attribution in funnel analysis

• Comparing revenue between test variants

If your website experiences downtime during an A/B test, Humblytics will pause data collection until the site is accessible again. The test will resume automatically once your site is back online, and all previously collected data remains intact. You can also manually pause tests from your dashboard if needed.

The agent proposes a test and you approve the exact change before it reaches the site. A losing test is not promoted, and promoting any winner into production remains a human decision.

Create multi-step funnels by mapping page views, clicks, form submissions, or any custom event in a visual flow. You can see conversion metrics at a glance including starting volume, drop-off percentages, overall conversion rate, and per-step value attribution. Funnels support cross-domain tracking.

Conversion optimization workflow:

1. Analyze heatmaps to identify low-engagement areas

2. Review funnel data to find drop-off points

3. Test hypotheses with A/B experiments

4. Monitor form analytics to optimize lead capture

5. Use click data to optimize navigation and CTAs

Humblytics is built for privacy-first analytics, and your consent requirements depend on your complete setup. Our privacy policy and data processing agreement explain how data is handled. Review your complete stack and applicable law, since other tools on your site may need consent too.

Humblytics is built for privacy-first analytics: visitors are anonymized with a one-way hash and raw IPs are discarded immediately. Review the privacy policy and data processing agreement for the legal terms that apply to your use case.

Humblytics' privacy-first approach supports CCPA work:

• No personal identifiers are stored

• Data is anonymized through hashing

• Users aren't tracked across sites

• You can implement data deletion requests if needed

Different analytics tools can report different unique-visitor totals because they identify sessions differently and browsers block some scripts. Humblytics uses a one-way hash of IP and device characteristics and does not publish a guaranteed accuracy percentage. Compare trends and conversions consistently within one measurement system rather than expecting two tools to match exactly.

Humblytics anonymizes visitors with a one-way hash. If you want to offer an opt-out, you can:

• Respect Do Not Track browser settings

• Implement custom opt-out functionality using JavaScript

• Provide transparency about data collection in your privacy policy

The current privacy policy and data processing agreement are the canonical sources for data use, subprocessors and disclosure commitments. Review those documents for the complete terms rather than relying on a short FAQ summary.

The public privacy policy and data processing agreement are the canonical sources for security, subprocessors and data-handling commitments. Do not rely on an infrastructure detail copied into a FAQ, because hosting and controls can change independently of this page.

Data-residency and subprocessor details belong in the current data processing agreement. If a specific region is a hard requirement, review that agreement and confirm the requirement with support before subscribing.

Humblytics is publicly offered as a cloud-hosted product. A self-hosted edition is not listed in the current public plans, so do not assume it is available. Contact Enterprise before making it a procurement requirement.

Yes, plan switching is flexible:

• Upgrades: Take effect immediately with pro-rated charges

• Downgrades: Start next billing cycle with no data loss

All historical data is retained regardless of plan changes.

You can change plans from the product. Billing timing, proration and the effect of a downgrade are shown in the checkout before confirmation. If a billing transition is important to your decision, confirm the current behavior with support rather than relying on an old threshold or grace-period rule.

The dashboard shows current usage against your plan's event allowance. Enforcement and upgrade options can change, so use the in-product notice or contact support for the current overage behavior rather than assuming a fixed grace period.

Use the billing and usage dates shown in your dashboard as the source of truth. If the reset date is unclear, contact support before planning around a specific calendar day.

Upgrading to a different plan during your 14-day trial ends the trial immediately and triggers an immediate pro-rated charge for the new plan. If you want to evaluate a higher plan's features without being charged, email [email protected] before upgrading and we'll set your trial up on the right plan.

Cancellation, account deletion and data retention are separate actions. Review the current privacy policy and the cancellation screen for the applicable retention period, and export anything you need before deleting the account.

Current plan limits and the data processing agreement are the canonical sources for retention. Enterprise lists unlimited data retention publicly; do not infer fixed Business or Scale retention periods when they are absent from the current pricing page.

API access is included on every plan, and dashboards can be shared with public view-only links. Export formats vary by product surface. Humblytics does not currently ship scheduled emailed reports, digests or alerts.

Team members are a Scale and Enterprise feature:

• Business: 1 seat (account owner only)

• Scale: 5 team members

• Enterprise: Unlimited team members

Business is the single-seat plan and Scale includes 5 team members. Contact sales if the published seat counts do not fit.

Yes. Humblytics supports public view-only share links. Scale also includes team seats for people who need product access.

Use the account controls or contact support from the account email. Review the privacy policy for the current deletion process and export anything you need before confirming an irreversible deletion.

Humblytics does not currently ship scheduled emailed reports, digests or alerts. Use the live dashboard, public view-only share links, or the API instead.

Scheduled emailed alerts and reports are not a shipped feature. Share the live dashboard with a public view-only link or give team members access on a plan that includes seats.

Current integrations include:

• Website installation: Webflow, Framer, Shopify, WordPress, Squarespace, Wix and custom sites

• Ad attribution: Meta and Google Ads

• Revenue attribution: Stripe and Foxy

• Agent access: hosted MCP plus the REST API

Check humblytics.com/integrations for the current public list.

The REST API and hosted MCP are included on every plan for programmatic analytics and experiment access. Use MCP discovery or the current documentation for the supported operations. A public real-time goal webhook is not documented, so do not design around one without confirming it first.

WordPress sites can install the tracking script directly. For a multisite network, add and verify each site according to the current installation guide; do not assume a dedicated network-wide plugin is available.

AMP restricts custom JavaScript, and Humblytics does not publish a dedicated AMP integration. Verify the current AMP installation path before relying on it.

Humblytics is engineered for minimal performance impact:

• Lightweight script (about 16 KB compressed)

• Asynchronous loading, so it does not block the initial page render

Like any third-party script it has a load cost, so verify the result on your own page.

There is no universal Lighthouse delta. The script is about 16 KB compressed, loads asynchronously and does not block the initial render, but every third-party script has some cost. Measure your own production page before and after installation.

Some visitors or network policies can block any analytics script, so no vendor can promise zero blocking. Humblytics does not publicly offer self-hosting or a first-party proxy as a standard workaround.

Humblytics works across all modern browsers including Chrome, Firefox, Safari, Edge, and mobile browsers. The script is compatible with:

• Desktop computers (Windows, Mac, Linux)

• Mobile devices (iOS, Android)

• Tablets (iPad, Android tablets)

• All major browser versions from the past 5 years

Automated anomaly alerts are not a documented shipped feature. Use traffic trends, funnels and the agent's read access to investigate changes, but do not expect an email alert or autonomous anomaly-monitoring system.

The base tracking script is non-visual, but A/B-test variants can change page content and the DOM. Treat every variant as a production UI change: preserve semantics, keyboard access, focus behavior, labels and contrast, then test it with assistive technology before launch.

Support options include:

• Email support: [email protected] with product specialists

• Documentation: Comprehensive guides at docs.humblytics.com

• Video tutorials: YouTube channel with step-by-step guides

• Blog: CRO tips, platform guides, and product updates at humblytics.com/blog

• Tools: Free calculators and UTM builders

The support team provides personalized assistance for setup, troubleshooting, and optimization questions.

Humblytics supports IP exclusion so you can filter out internal traffic. Go to your site settings and add the IP addresses you want to exclude. Visits from those IPs won't be tracked. You can also:

• Use UTM parameters to identify internal visits

• Set up custom events to separate internal team interactions

• Apply audience filters in your funnel analysis to exclude specific traffic sources

Currently, Humblytics offers basic filtering options. More advanced segmentation features are in development. You can segment data by:

• Device type (desktop, mobile, tablet)

• Traffic source (direct, referral, search)

• Geographic location

• Time periods