Engineering Readiness Brief
Estimate the engineering effort required to embed Partner Fleet’s In-App Marketplace, including JWT SSO, frontend embed, and status sync requirements.
Use this brief to estimate what your engineering team needs to build to embed Partner Fleet’s In-App Marketplace in your product.
Embedding Partner Fleet’s In-App Marketplace into your product requires 8–16 hours of engineering effort for most teams. If you don’t yet issue JWTs, budget 24–40 hours. You configure the rest — marketplace UI, branding, content, personalization, and analytics — in Partner Fleet’s admin without code.
What this document covers
The integration has three areas, each with a clear scope and implementation pattern.
| Integration area | Typical effort |
|---|---|
| 2–4 hours |
| 2–8 hours |
| 4–16 hours |
1. Authentication (JWT SSO)
Partner Fleet uses JWT SSO (single sign-on using JSON Web Tokens) to identify users from your app. When a user navigates to the marketplace, your backend generates a signed token containing user and account context.
If your product already issues JWTs for any purpose, this is likely a known pattern for your team.
What Partner Fleet provides
- JWT shared secret management in the admin UI
- Built-in Test Tools, including Generate Test Token and Decode & Verify Token, for validation without touching your backend
- Ruby, Node.js, and Python reference implementations in the help docs
What your team provides
- A backend endpoint that returns a signed JWT with the required claims using HS256 signing
- Standard user fields your auth system likely already stores: email, first name, last name, account identifier, and account name
Effort estimate: 2–4 hours for most teams. Near-zero if you already issue JWTs.
2. Frontend Embed
The marketplace embeds into your product through a lightweight JavaScript loader. Partner Fleet provides the copy-paste snippet in the admin UI under Developer Settings > Embed Script.
What Partner Fleet provides
- Auto-generated embed code snippet with your specific CNAME and URLs
- CNAME configuration with SSL certificate provisioning
- Allowed Domains whitelist so the marketplace only renders on domains you’ve authorized
- Setup checklist with real-time status tracking for each configuration step
What your team provides
- A page or route in your product where the marketplace should appear, such as
/integrationsor/marketplace - A CNAME DNS record pointing your chosen subdomain, such as
marketplace.yourcompany.com, toproxy.partnerfleet.app
Effort estimate: 2–8 hours for most teams. This includes placing a div, including a script tag, adding a DNS record, and wiring up the token callback. Because Partner Fleet serves the marketplace from your own CNAME, it appears first-party and does not require CSP changes.
3. Status Sync & Visibility
The marketplace personalizes what users see based on JWT claims, including which listings they can see, which CTAs render, and which integrations appear installed.
| Mechanism | What it does | Your team provides |
|---|---|---|
| Listing Visibility | Server-side rules gate which listings a user can see by account tier, region, or custom fields. Hidden listings never reach the browser. You configure these rules in the admin UI without code. | Tier, region, and role fields in the JWT |
| Integration Status | Per-user status, such as null, active, pending, error, or disabled, controls which CTAs render on each listing. | Status per user through the JWT, constructor, or postMessage |
| CTA Routing | Conditional CTAs route users to install flows, lead forms, or in-app actions based on role, tier, and status. You configure CTA routing in the admin UI without code. | Event handlers for postMessage CTAs, if needed |
Effort estimate: 4–16 hours depending on whether you already track integration statuses. If your system already knows which integrations each customer has installed, this is minimal. If you need to build status tracking, budget the higher end.
Total effort summary
| Integration area | Typical effort | If starting from scratch |
|---|---|---|
| Authentication (JWT) | 2–4 hours | 4–8 hours |
| Frontend Embed | 2–8 hours | 4–12 hours |
| Status Sync & Visibility | 4–16 hours | 16–20 hours |
| Total | 8–16 hours | 24–40 hours |
What you do not need to build
Partner Fleet provides the marketplace infrastructure. Your team only provides the connection points.
You do not need to build:
- Marketplace UI, search, or filtering logic
- Integration listing management or CMS
- Visibility or access-rule engine
- Conditional CTA matching logic
- Analytics or usage tracking infrastructure
- Partner onboarding or listing submission workflows
Quick readiness checklist
Share this checklist with your engineering lead. If you can answer “yes” to most of these questions, implementation is straightforward:
- Does your app authenticate users?
- Can your backend generate a signed JWT?
- Can your frontend include an external JavaScript file and render a
<div>? - Do you track which integrations each customer has installed?
- Can you add a CNAME DNS record?
If you answered “yes” to questions 1–3 and 5, you’re ready. Question 4 is the variable. Even without it, the marketplace works; install-state badges appear after status sync is wired up.
Next steps
Schedule a 30-minute technical walkthrough with the Partner Fleet team. We’ll screen-share the admin UI, walk through the setup checklist live, and answer architecture questions. Most teams leave that call with a clear plan and a confident sprint estimate.
Partner Fleet powers ecosystems for Gong, Mindbody, Salesloft, Greenhouse, ZoomInfo, Motive, and 50+ others.
Updated 2 months ago