KLM-SHIP Shipping log
Always be shipping.
What we shipped and what we wrote about it, newest first. Subscribe with RSS.
- Meta events are labelled by where they happenedMeta events are labelled website or system-generated by where they happened, never by a setting. IP address and user agent are separate settings.
- New webhook catchers record until you start themA new webhook catcher keeps deliveries as samples, even after listening ends, until you choose Start processing.
- Scan reports say when they saw too littleA scan that loaded too few pages shows "Risk unknown" instead of Low, with the pages it tried and why some failed.
- GLP-1 Telehealth Ads: Tracking Conversions Without Leaking Patient DataGLP-1 telehealth ads tracking, field by field: where weight-loss funnels leak to Meta (UTMs, quiz, checkout, dose-step refills) and what to send instead.
- Telehealth Conversion Tracking: Intake, Payment, Rx Approval and RefillsTelehealth conversion tracking, stage by stage: what to send Meta for intake, payment, Rx approval and refills, when each happens, and a timing bug to fix.
- Agency PDF client reportsAgencies can generate a branded PDF of any client workspace's results for a date range. Each file is deleted 24 hours after it's ready.
- In-app help center and What's newSearch help articles, read what's new in Kalman, and find the right guide from any integration page, all without leaving the app.
- The Kalman consent bannerA built-in consent banner, shown by the Kalman tag, that asks visitors whether their visit may be shared with ad platforms. Off until you turn it on.
- Is the Meta Pixel HIPAA Compliant? What Telehealth Brands Need to Know in 2026Is the Meta Pixel HIPAA compliant? Not on its own. What HHS guidance, the 2026 class certification and the FTC mean for telehealth, and what to check now.
- CallRail: phone calls as leadsCalls from CallRail tracking numbers become Kalman leads that keep the ad click, with recordings, transcripts and caller names dropped before storage.
- Google Ads integrationConnect Google Ads with OAuth to send approvals, purchases and refills as offline conversions and import Google spend into Acquisition.
- VWO experiments measured against leads, purchases and approvalsCompare VWO test variants by the outcomes VWO never sees: leads, purchases and provider approvals, on Funnel and Traffic.
- Meta Health and Wellness Restrictions: How Telehealth Brands Check Their Pixel and Fix ItMeta health and wellness restrictions, explained for telehealth: find your restriction level in Events Manager, what each blocks, and the fixes that last.
- Purchase Is Blocked. What Should a Telehealth Account Optimize For?A signal ladder for restricted telehealth Meta accounts: how to pick an optimization event by volume, timing, closeness to revenue and what it reveals.
- In-app support requestsAsk for help from any page in Kalman, follow the thread under Your requests, and get email notices that never include your message.
- Sign your BAA in onboardingAccount owners review and e-sign Kalman's Business Associate Agreement in the app, and get a signed copy by email.
- Does Moving to the Conversions API Make Telehealth Tracking Safe?Server-side tracking changes who controls the payload, not what's in it. What telehealth media buyers should check in every CAPI event before scaling.
- Agency bulk scans and white-label scan reportsScan up to 200 client and prospect sites from one list and send each brand a report with your agency's logo, colors and call to action.
- Shadow mode and the signal-gap reportRun Kalman beside your current tracking without sending anything to Meta, then compare what Meta reports with what Kalman would send.
- Before You Scale Telehealth Spend for Black Friday: A 10-Point Tracking CheckBlack Friday budgets amplify every tracking flaw. Ten checks for telehealth Meta accounts before you raise spend, from blocked events to intake-page tags.
- The Hims & Hers Complaint, Read by a Media Buyer: What to Check in Every Telehealth AccountThe FTC's Hims & Hers complaint is about privacy promises versus data flows. What agencies running telehealth Meta ads should check in each account.
- Why Renaming Your Blocked Purchase Event Won't Save Your Telehealth CampaignsTurning Purchase into Pur_1 is popular advice for restricted health pixels. Why it's fragile, and what to design your optimization events around instead.
- Website scanner and signal audit reportsScan a telehealth site's public pages to see what its trackers send, with a score, findings and a Meta restriction risk.
- Acquisition: Meta spend import, cost per approved patient and ROASImport Meta ad spend daily and see cost per purchase, cost per approved patient and ROAS from campaign down to ad.
- First-party tag and tracking domains on your own subdomainA small Kalman tag that runs from a subdomain like kl.yourbrand.com, sets first-party cookies and never reads forms or page text.
- Meta Conversions API integrationSend intake, checkout, purchase and approval events to Meta from the server, through the PHI firewall, with value strategies and test events.
- Overview, Traffic and Funnel analytics with product LTVVisitors, intakes, purchases, approvals and lifetime value per product, computed from Kalman's own data with no third-party analytics.
- Passkeys and two-factor sign-inSign in to Kalman with a passkey, and protect your account with an authenticator app and recovery codes.
- PHI firewall and the outbound deliveries logEvery ad-platform payload is built from an allowlist, and the Events log shows exactly what Kalman sent for each event.
- Sylaris OS integrationFunnel events from Sylaris OS intake, checkout and fulfillment flow into Kalman through the browser tag and signed server webhooks.
- Webhook catchers for Stripe and any platform's webhooksPoint any platform's webhook at Kalman, map its fields without seeing values, and turn each delivery into a funnel event.