analytics.js

jquery replacement, or just vanilla. Little content on vanilla js nowadays :), https://gomakethings.com/articles/ is something interesting. Don’t want to flame here, am not js expert, maybe someone can elaborate. 6. For compex components - svelte web components (or stencils or lithtml) - I’d prefer svelte but am not sure what’s best. 7. Google analytics a) - there is new google analytics (GA4) with measurement protocol2 and new server side google tag manager. Serve side gtm does two things a) serves gtag.js; b) accepts measurement protocol hits and sends to GA. Take a look how it’s done - https://www.simoahava.com/gtm-tips/build-custom-universal-an... , it’s very similar as cloudflare workers, cool stuff. But it’s hosted on Google App Engine, thus - slow. But you don't need google's server anymore, you control full infra, so why not setup simple cache here. 8. Google analytics b) To owerome latency to Google App engine, so you make async proxy in cloudflare workers - one worker to proxy for gtag.js download, one for serving gtag.js from your own domain. <script src=“http://yourdomain.com/workers/gtag/js?id=G-1234455> . Basicly just serve from js cache and check every once in a while if google hadn’t changed their code. Same for GA hits. It used to be google-analytics.com/collect endpoint, server side gtm allows to host collection yourself. You again make worker-proxy, define it in gtag’s transport_url:'https://turboeshop.com/measure' setting and make sure worker returns non-blockingly, and just then forward the measurement protocol hit from worker async-ly with event.waitUntil(). 9. Google analytics c) The gtag.js/analytics.js is a huge file and you have no control, so maybe just use https://github.com/segmentio/analytics.js instead or check out https://www.thyngster.com/app-web-google-analytics-measureme... (search “navigator.sendBeacon”) - craft measurement protocol yourself and send it to gtm. I plan on investigating this but have not yet done that. 10. All the stuff (fb tracking pixel, etc.) you are used to just ‘putting in html’, you instead send as measurement protocol hit dimension and do ETL in google tag manager. 11. All the 3rd party stuff that demands to be executed client-side - you just don’t use that :D (or use, but wisely) 12. HTML - bussiness as usual. 13. So after page reload - double check if all requests are done/received from your own domain. Use curl on each of them to find header CF-cache-status: HIT. They have this ‘varied’ or similar status which means something I can’t remember, but I always fix stuff till ‘Hit’ :) 14. I guess that’s it. Enjoy your own fastest website in the world :)

revenue. But the biggest and most challenging engineering problems lie ahead. We're a key piece of infrastructural data plumbing for thousands of web businesses, and we need to interoperate reliably and seamlessly with hundreds of integration partners. Email myself peteratsegment.com, calvinatsegment.com (cto/co-founder) or drop us a note here: https://segment.com/jobs/descriptions/infrastructure-enginee...

ring our the best way to design the landing page—much less scope that conceiving the entire idea. It's really hard to quantify that kind of time investment, and even harder to explain that to friends who think that everyone is launching fully-formed, successful MVPs in a single weekend without much thought. It definitely seems like something that can only be learned through experience. It's just an earlier stage version of the classic problem of founders always thinking that successful startups spring out of nowhere, when really the multiple years of living in a cramped room and almost killing each other is just shielded from view. At least it makes things more defensible :) Random other thought: I often catch myself bundling up tons of logic into a "first commit" and wishing that that wasn't a common practice, so that we could learn about how the beginnings of codebases are iterated on. [1]: https://github.com/segmentio/analytics.js [2]: http://www.myth.io/ [3]: https://github.com/ianstormtaylor/rework-pure-css

include: + Becoming a core maintainer of https://github.com/segmentio/analytics.js, which runs on tens of millions of computers every month, growing fast. + Building the Segment.io app where users manage their analytics services and data. We use component, d3.js, socket.io, and node.js. Shoot us an email if you're interested! peter@segment.io https://segment.io