sales-blueconic
BlueConic platform help — Customer Data Platform (CDP), real-time profile unification, segmentation, personalization, audience activation, Jebbit Experiences, AI Workbench. Use when profiles aren't merging across channels, segments aren't syncing to ad platforms, BlueConic connections aren't importing or exporting data, you need help setting up BlueConic on a single-page app, consent and privacy objectives aren't working correctly, or you're choosing between BlueConic and another CDP. Do NOT use for general email marketing strategy (use /sales-email-marketing) or CRM data deduplication without BlueConic (use /sales-data-hygiene).
What this skill does
# BlueConic Platform Help
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated platform knowledge.
1. **What do you need help with?**
- A) Setting up BlueConic on my site (script tag, SPA, mobile SDK)
- B) Profile unification / identity resolution
- C) Segmentation and audience building
- D) Connections — importing or exporting data to/from other tools
- E) Personalization — dialogues, experiences, A/B testing
- F) Jebbit Experiences (interactive content, quizzes, AI Shopping Assistant)
- G) API integration (REST API v2, JavaScript front-end API, Event API)
- H) MCP server setup for AI tools (Claude, Cursor, VS Code)
- I) Privacy, consent management, GDPR/CCPA objectives
- J) AI Workbench (Python, custom models)
- K) Choosing BlueConic vs another CDP
- L) Other — describe it
2. **What's your role?**
- A) Marketer — I use the BlueConic UI
- B) Developer — I'm integrating via API or SDK
- C) Data/analytics — I work with segments, exports, or AI Workbench
- D) Admin — I manage users, permissions, connections
3. **Which BlueConic plan are you on?**
- A) Pyxis (free tier)
- B) Standard
- C) Professional
- D) Enterprise
- E) Not sure / evaluating
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
## Step 2 — Route or answer directly
| Problem domain | Route to |
|---|---|
| Email campaign strategy | `/sales-email-marketing` — then come back for BlueConic segment activation |
| CRM data dedup without BlueConic | `/sales-data-hygiene` — BlueConic is a CDP, not a CRM dedup tool |
| Retargeting ad strategy | `/sales-retargeting` — then come back for BlueConic audience sync |
| Connecting BlueConic to other tools | Answer here using connections reference |
| Tool integration architecture | `/sales-integration` — for webhook/Zapier patterns beyond BlueConic connections |
| SMS/push strategy | `/sales-sms-marketing` or `/sales-push-notification` — BlueConic activates audiences, doesn't send messages |
When routing to another skill, provide the exact command: "This is a {problem domain} question — run: `/sales-{skill} {user's original question}`"
## Step 3 — BlueConic platform reference
**Read `references/platform-guide.md`** for the full platform reference — modules, pricing, integrations, data model, connections, workflows, JavaScript API, Event API, MCP server.
Answer the user's question using only the relevant section. Don't dump the full reference.
## Step 4 — Actionable guidance
You no longer need the platform guide — focus on the user's specific situation.
- **For setup questions**: Walk through script tag placement, SPA handling (`handlePageView()`), or mobile SDK initialization
- **For identity resolution**: Explain profile merge rules, email-based vs cookie-based matching, cross-device stitching
- **For connections**: Identify the right connection type (named vs universal), configure import/export, set sync frequency
- **For segmentation**: Help build segments using behavioral + profile data, explain dynamic vs static segments
- **For API questions**: Point to the right API (REST v2 for server-side, JS front-end for client-side, Event API for custom events)
- **For MCP**: Walk through OAuth2 app creation, client credentials, tool configuration
If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
## Gotchas
> *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*
1. **Identity resolution depends heavily on email** — if your visitors don't log in or provide email, profiles stay anonymous and fragmented. Progressive profiling (Jebbit Experiences) helps bridge this gap.
2. **SPA pages don't auto-trigger** — BlueConic doesn't detect client-side route changes. Call `blueConicClient.handlePageView()` after each navigation event in React/Angular/Vue apps.
3. **Pyxis free tier expires after 6 months** — then pricing starts at $750/month for 100K profiles. Plan capacity before the trial ends.
4. **No mobile access** — BlueConic's admin UI is desktop-only. You cannot manage segments or connections from a phone.
5. **Ease of Setup rated 6.7/10 on G2** — the platform is powerful but has a steep learning curve. Start with one use case (e.g., segment activation to one ad platform) before expanding.
6. **Profile limits are billed automatically** — if you exceed your subscription's profile threshold, you get charged overages. Monitor profile counts proactively.
7. **REST API v2 is OpenAPI-based, JSON-only** — XML is not supported. Default encoding is gzip, output is minified. Add `?prettyPrint=true` for readable responses.
8. **Connection sync is not real-time for all integrations** — some connections run on schedules (hourly, daily). Check the connection's sync frequency settings if data seems delayed.
## Related skills
- `/sales-cdp` — CDP comparison and selection strategy across Tealium, Segment, BlueConic, mParticle, Treasure Data
- `/sales-tealium` — Tealium CDP — Real-Time CDP, identity resolution, 1300+ connectors
- `/sales-treasuredata` — Treasure Data enterprise CDP — profile unification, 400+ connectors, AI Marketing Cloud
- `/sales-data-hygiene` — CRM data quality, deduplication, enrichment automation
- `/sales-retargeting` — Retargeting strategy, audience activation to ad platforms
- `/sales-integration` — Connect sales tools with webhooks, Zapier/Make, APIs
- `/sales-email-marketing` — Opt-in email marketing strategy across platforms
- `/sales-customerio` — Customer.io platform help (Journeys, Data Pipelines — often compared to BlueConic)
- `/sales-braze` — Braze platform help (Canvas Flow, Braze Data Platform — CDP-adjacent)
- `/sales-klaviyo` — Klaviyo platform help (Klaviyo Data Platform — CDP-adjacent for ecommerce)
- `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do`
## Examples
### Example 1: Activating segments to ad platforms
**User says**: "I have customer segments in BlueConic but I can't get them into Facebook Ads for retargeting."
**Skill does**: Walks through the Facebook Advertising connection setup — configuring the connection, mapping BlueConic segments to Facebook Custom Audiences, setting sync frequency, and verifying audience match rates.
**Result**: User has BlueConic segments automatically syncing to Facebook Custom Audiences for retargeting.
### Example 2: Setting up BlueConic on a React SPA
**User says**: "BlueConic dialogues only fire on the first page load, not when I navigate between routes in my React app."
**Skill does**: Explains that SPAs need `blueConicClient.handlePageView()` called after each route change. Provides a React useEffect hook pattern that listens to route changes and triggers BlueConic re-evaluation.
**Result**: Dialogues and listeners fire correctly on every SPA route change.
### Example 3: Choosing BlueConic vs Segment
**User says**: "Should I use BlueConic or Twilio Segment as our CDP?"
**Skill does**: Compares positioning — BlueConic is marketer-first (no-code segmentation, personalization, audience activation), Segment is developer-first (event tracking, data routing, warehouse integration). Asks about team composition, technical resources, and primary use case to recommend.
**Result**: User has a clear recommendation based on their team and goals.
## Troubleshooting
### Profiles not merging across channels
**Symptom**: Same customer has multiple BlueConic profiles (one from web, one from email, one from mobile)
**Cause**: No shared identifier connecting the profiles. BlueConic merges on matched identifiers (typically email).
**Solution**: Implement progressive profiling to capture email from anonymous visitors. Use the JavaScript API `profile.setValue()` to set email when a user logs in or submitsRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".