-
Notifications
You must be signed in to change notification settings - Fork 2
Hubspot example #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Hubspot example #25
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
"dub_pk_tLnpzXvJAEik0UtzuzdmMJSn" | ||
); // Replace with your publishable key | ||
s.setAttribute("data-domains", '{"refer":"dub.sh"}'); | ||
s.setAttribute("data-api-host", "http://localhost:8888/api"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s.setAttribute("data-api-host", "http://localhost:8888/api"); |
The analytics script is configured to use a localhost development URL that will fail in production.
View Details
Analysis
Hard-coded localhost API URL breaks analytics in production deployment
What fails: Dub analytics script in conversions/hubspot/meeting.html
uses hard-coded data-api-host="http://localhost:8888/api"
that fails outside development environment
How to reproduce:
# Deploy meeting.html to any non-localhost environment
# Analytics calls fail with connection refused/network errors
curl -I http://localhost:8888/api # Fails on production servers
Result: Analytics tracking requests fail, no conversion data collected. Browser console shows network errors attempting to reach localhost:8888.
Expected: Should use default production API endpoint https://api.dub.co
like other examples in the repository per Dub Analytics documentation
No description provided.