Properties·New
The control plane your client’s site never had.
Properties is the runtime layer for every site and app we ship. Update store URLs, flip feature flags, see real analytics, and trigger nurture sequences — all without a single redeploy. One dashboard for every client surface.
The problem
Every client change is a dev ticket.
The App Store URL changes. The hero CTA needs to swap. A campaign banner has to go live by Friday. Every one of those is a dev ticket, a redeploy, and a chunk of your margin.
Analytics is scattered across GA, a spreadsheet someone updates manually, and a Slack channel where wins get screenshotted. Nobody can answer “is this site actually working?” in under an hour.
Traffic converts on the marketing site — and then nothing happens. There is no bridge from a form fill on the live site to the nurture sequence that closes the deal. Leads cool off in a CSV.
What you can do
Six jobs, one dashboard.
The before / after of every Properties capability — written in the JTBD shape because that is how agencies actually think about this work.
Remote config
Update App Store URLs, primary CTAs, custom JSON without a redeploy.
Kill switch
Toggle a property offline instantly when something goes wrong.
Feature flags
Roll a feature to a cohort, measure, then expand. No redeploy needed.
Per-property analytics
Sessions, users, events, conversions, and a live event stream.
Conversion sequences
Auto-enrol converters into a linked email nurture sequence.
Creator / affiliate links
Property-scoped short URLs with click counts and attribution.
How it works
Three steps, then it is live.
Drop the ingest key
A single env var in your client's site or app. The lightweight @partnersinbiz/analytics-js SDK does the rest.
Configure in PiB
Set store URLs, primary CTAs, kill switches, feature flags, and the linked email sequence — from one dashboard.
Measure & iterate
Watch real sessions stream in. Flip a flag, ship a config change, see the lift — without a single deploy.
Capability deep-dive
What each capability actually does.
The detail behind the six headlines. Skip what you do not need.
Each property exposes a JSON config block read by the client at runtime. Change the App Store URL, the primary CTA href, the announcement banner copy, or any custom field — your client's site picks it up on the next request, no redeploy needed.
Every property has a global kill switch. Flip it and the property's SDK serves a maintenance shell instead of the live site. Useful during incidents, takedowns, or planned outages — no DNS surgery, no panicked hosting calls.
Boolean and JSON flags scoped per property and per cohort. Roll a feature to 5% of traffic, watch the conversion delta, and either expand or roll back from the same dashboard. The SDK caches and revalidates so flags are fast in production.
A first-party analytics pipeline with sessions, users, events, funnels, and a live event stream. Each property gets its own dashboard so your client sees their numbers — not yours, not aggregated, not second-hand from GA.
Wire any conversion event to a linked email sequence. The contact is auto-enrolled into the sequence on the event, with the property's context attached. No CSV exports, no Zapier glue.
Property-scoped short URLs with click counts, referrer attribution, and per-creator dashboards. Pay creators on real, attributable clicks — not the honour system.
Built for agencies
Built for the agency model.
Multi-org from day one. Every client gets their own workspace, their own property dashboards, and their own white-labelled reports — without you spinning up another tool per client.
- check_circleMulti-org workspaces — one PiB account, every client cleanly separated.
- check_circlePer-property dashboards your clients can actually log in to.
- check_circleWhite-label monthly reports baked in — branded for you, sent to them.
- check_circleRead-only client roles, full-access internal roles, audit log on every change.
- check_circleDrop-in SDK that works with Next.js, Vite, plain HTML, React Native, and Expo.
FAQ
Questions buyers ask before they wire it in.
For the first property, yes — a developer drops the ingest key into the env and the SDK into the client's site. After that everything is dashboard-driven. Most agencies wire it once and reuse the pattern across every client site they ship.
No. The SDK fails open: if PiB is unreachable the site falls back to its build-time defaults. Nothing in Properties is on your client's critical render path.
Yes. Each client org gets read-only access to their own property dashboards. You control what they see — analytics, conversions, or the full config plane.
Keep GA if you want it — Properties analytics runs alongside, not instead. Most agencies keep GA for the marketing team and use Properties for the operational and product view.
Yes. The SDK is cookieless by default, IPs are hashed at ingest, and per-property data export and deletion are one click. You stay in control of the data.
When the kill switch is on, the SDK serves a configurable maintenance shell instead of the live site. The shell is fully customisable per property — your branding, your copy, your retry behaviour.
Ready?
Ready to take control of your client surfaces?
Properties ships with every Web Application and Bespoke Build. Or wire it into a site we did not build — we’ll quote the integration in a day.