Skip to main content

Chrome Extension Troubleshooting

Common issues, fixes, and best practices for the kenbun Intent Tagger Chrome extension.

Common Errors​

"Reload page to use tagger"​

Cause: Content script not loaded on the page.

Solution: Refresh the page after opening the side panel. The extension needs to inject scripts into the page.

"Error: Beacon not found on page"​

Cause: kenbun Web Beacon is not installed on the target website.

Solution: Install the beacon script on the site. See Web Beacon installation.

"Error: Server returned 404"​

Cause: Backend API endpoint missing or incorrect Backend URL configured.

Solution:

  • Verify the backend is running
  • Check the Backend URL in settings matches your kenbun environment
  • For kenbun SaaS: use https://app.kenbun.io

"Error: Server returned 403"​

Cause: Invalid or missing Organization Unit ID.

Solution:

  • Check OU ID in settings matches your organization
  • Log into kenbun in the same browser to enable auto-detection
  • Verify you have permission to create tags for this OU

"Error: Failed to fetch"​

Cause: Backend not reachable or network issue.

Solution:

  • Check the Backend URL is correct
  • Verify the backend is running
  • Check firewall or network settings
  • Try enabling Testing Mode to work offline

"Wrong OU ID"​

Cause: OU ID in settings doesn't match your logged-in session.

Solution:

  • Clear the OU ID field in settings to use auto-detection
  • Log out and back into kenbun
  • Manually enter the correct OU ID if needed

CORS Errors in Console​

Cause: Backend not allowing requests from the extension.

Solution: This is expected behavior. The extension sends API requests with the X-Active-OU-ID header, which requires backend CORS configuration. For the kenbun SaaS backend, this is already configured. For self-hosted setups, ensure CORS allows the extension origin.

Best Practices​

When to Use Global vs. Page-Specific Tags​

Page-Specific Tags for:

  • Unique elements on single pages
  • A/B testing different CTAs
  • Page-specific forms

Global Tags for:

  • Persistent navigation elements
  • Footers and headers
  • Consistent CTAs across pages

Security and Privacy​

  • No sensitive data: Avoid capturing passwords, credit card numbers, or PII in form submissions
  • DOM scraper limits: Data capped at 10 KB per capture to prevent abuse
  • OU scoping: All tags are scoped to your Organization Unit — other organizations cannot see your tags
  • Origin allowlist: Beacon tokens enforce origin allowlists for security

Testing Before Production​

  1. Enable Testing Mode in settings
  2. Tag elements on a staging or test environment
  3. Verify events appear correctly in kenbun (check the Events page)
  4. Confirm event metadata is as expected
  5. Disable Testing Mode to sync to backend for production use

Use Cases​

Track CTA Clicks Across Product Pages​

You have a "Start Free Trial" button on multiple product pages. Create a global tag:

  • Pattern: https://example.com/products/*
  • Selector: button.free-trial-cta
  • Event Name: Product Free Trial Click

Now every click on that button across all product pages is tracked with the same event name.

Identify High-Intent Pricing Page Visitors​

Someone who clicks "See Pricing" from your homepage and then clicks "Contact Sales" on the pricing page is a hot lead.

  1. Tag the homepage "See Pricing" link → Homepage See Pricing
  2. Tag the pricing page "Contact Sales" button → Pricing Contact Sales
  3. Create a scoring rule: Homepage See Pricing = +10 points
  4. Create a scoring rule: Pricing Contact Sales = +25 points
  5. Create a sequence trigger: Both events within 10 minutes = Slack notification

Capture Form Submissions with Auto-Identification​

Track contact form submissions and automatically associate them with the lead's email.

  1. Tag the form element (not the submit button)
  2. Event Name: Contact Form Submit
  3. When submitted, form fields are captured, including email
  4. kenbun automatically runs identify if an email is found
  5. Subsequent events are linked to that lead

Extract Google Tag Manager Data​

Your marketing team uses GTM and you want to capture page category and user type from the dataLayer.

Create a DOM scraper:

  • Event Name: DataLayer Capture
  • Pattern: *.example.com/*
  • Window Path: dataLayer
  • Capture Mode: On Page Load

Events include the entire dataLayer contents, which you can then use in triggers or scoring rules.

Annotate Leads with Contextual Sales Info​

A sales rep is reviewing a prospect's account page on your SaaS product and notices they are on the "Enterprise" pricing tier and have started a quote. The rep wants to capture this context for the team.

  1. Set up a DOM scraper for user.email on your product domain so leads are auto-detected
  2. Open the side panel and select Lead Profile
  3. The lead is identified automatically from the page
  4. Add attributes: quote_step: Step 1, plan_interest: Enterprise
  5. Click Save Attributes

Now anyone viewing this lead in the kenbun dashboard sees the annotated context. If you have profile scoring rules tied to plan_interest, the lead's profile score updates automatically.