At a Glance

Upgrade your embedded (in‑product) marketplace to unlock a user‑aware experience with clearer ROI, faster iteration, and richer controls, without rebuilding your partner directory.

Top outcomes

Higher engagement where users already work. Customers discover and act on integrations inside your product.
User‑aware experience. Show the right listings and CTAs based on each user’s role, plan, and status (e.g., Install, Configure, Open).
Measurable adoption. Track which integrations are installed and by whom to inform roadmap and partner reporting.
Point‑and‑click control. Update layout, styles, and content rules without code redeploys.
Future‑proof. Access new features (translations, category controls, public vs in‑app inventory rules, etc.).

Why Migrate (Business Value)

Drive integration adoption & revenue: Contextual, in‑product CTAs reduce friction from discovery to activation.
Show impact: Visibility into installs/configuration supports leadership and partner ROI conversations.
Reduce engineering lift: Most changes move from code to configuration (design parity, categories, translations).
Control the experience: Segment by role/tier/region; decide which listings appear in public vs in‑app.
Stay current: Legacy embeds won’t receive enhancements; the new in‑app is our ongoing investment area.

Two Implementation Paths

1. Basic In‑App (fastest path to parity)

What you get

Design parity with your public marketplace (header/footer/styles)
In‑app vs public inventory controls and translations
Point‑and‑click management (no code changes for routine updates)

What it involves

Replace legacy JS snippet with the new in‑app snippet
Copy over design settings; set content/visibility rules
(If applicable) Swap any one‑off legacy hacks for supported config

Good fit when you want immediate stability, design control, and feature access without user authentication.

2. Advanced In‑App (full, user‑aware experience)

What you get

Authenticated experience with per‑user status (installed / not installed / in‑progress)
Dynamic, contextual CTAs (e.g., install, configure, open)
Permission & segmentation controls (role, plan, region)
Stronger analytics on adoption

What it involves

Build a lightweight JWT generator to authenticate users into the iframe
Implement integration status mapping so UI reflects true install state
Embed the new JS snippet and pass the JWT/attributes

Good fit when integration activation, personalization, and reporting are priorities.

Typical Timeline & Roles

Basic: ~1–3 weeks (customer: front‑end owner to replace snippet; Partner Fleet: configuration & design parity)
Advanced: ~3–6 weeks (customer: small backend work for JWT + status mapping; Partner Fleet: configuration, QA, rollout)

We’ll align a plan to your release cadence. Many teams ship Basic first, then layer in Advanced.

What We’ll Need From You

Decision on path: Basic now, Advanced later, or Advanced from day one
Owner(s): Product/Engineering contact for snippet swap; Backend contact for JWT/status mapping (Advanced)
Environment access: Dev/stage to validate embedding & SSO

FAQs

Will this change my public marketplace?
No—public and in‑app can be managed independently (including what appears where).

Do we need SSO?
Advanced In‑App uses a lightweight JWT (often alongside your SSO) to pass user identity/attributes.

What analytics are available?
Counts of unique users engaging with integrations in‑app and per‑integration install/configuration status (Advanced).

Can we start simple?
Yes. Ship Basic for design parity and controls, then add authentication and status mapping for full value.

Next Steps

Pick your path: Basic, Advanced, or phased
Reach out to your CSM to schdule a 30‑min planning session: confirm settings, roles/segments, and milestones
Implement & validate: snippet swap (Basic) → JWT + status mapping (Advanced) → QA → launch

Ready to move forward? We’ll schedule a quick planning session and get you a clear, dated checklist to launch.