菜单
Tracking pixel + identity resolution for MyAPI funnels and email. Capture visits and events, resolve known users to anonymous sessions, stream interaction events for analytics. Pairs with mycrmapi for auto-ingest of pixel_visit events on known contacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deploy JavaScript functions to the MyAPI edge runtime (Cloudflare Workers). Register a function, upload a single-file JS bundle, get a live HTTP invocation URL or run it on a cron schedule. Each function gets a scoped capability key for cross-slot calls.
Take payments via Stripe — one-off or recurring. Connect your own Stripe account, then create hosted Stripe Checkout URLs. No raw card data ever touches your code.
Auth, organizations, and billing hub. Start here to get an api_key and org_id — every other service depends on both.
Saved audiences = named Goldfox-filter snapshots over the people or company database. Build a target list once, name it, reuse it across campaigns, refresh to re-evaluate against current data. The persistence layer on top of my-people-api + my-company-api.
Register new domains and manage edge settings. Required before a funnel can go live on a custom URL.
Synchronous single-address email verification — syntax + DNS + Microsoft GetCredentialType probe. Returns a verdict in <1s for ~50% of inputs; the rest get verdict='unknown' with smtp_recommended=true. The pre-send quality gate for any outbound campaign.
| name | my-pixel-api |
| version | 1.0.0 |
| description | Tracking pixel + identity resolution for MyAPI funnels and email. Capture visits and events, resolve known users to anonymous sessions, stream interaction events for analytics. Pairs with mycrmapi for auto-ingest of pixel_visit events on known contacts. |
| triggers | ["pixel","analytics","tracking","visit","event","identity","session","attribution","geo","open pixel"] |
| checksum | sha256-pending |
A lightweight pixel data layer for funnels published via myfunnelapi and emails sent via myemailapi. Reads visits, events, identity resolutions, and interaction streams. The analytics half of the loop between outbound (email/funnel) and the CRM.
from_url, to_url, pixel_id, timestamp). --website <domain> is required.sent, open, click, page_visit. Requires at least one filter: --campaign-id or --domain.--website, --campaign-id, or --domain.pixel_id plus the --website <domain> it was seen on, resolve its identity graph ({uuid, is_resolved, nodes, …}).myapi pixel audience, no subcommand).The cookie-bridge pixel (/t/p) is a cross-domain pixel used to stitch an anonymous session on one MyAPI funnel to the same browser on another. The open-pixel (/t/o) is the 1x1 transparent gif embedded in outbound email and resolves the email recipient's session when they open the mail.
When pixel identify events fire with a known email, the CRM service auto-creates / upserts a contact and writes a pixel_visit event on its timeline. Today this hook lives in the hypersearch service and needs to move to the integrated stack — until then, pixel data and CRM data live in separate stores.
Pixel data lives ~90 days hot; aggregated geo/audience samples persist longer. Don't depend on individual-event-level data being available indefinitely — promote anything you need long-term into the CRM as a custom event.
pixel_visit is more than N days old| Command | What it does |
|---|---|
myapi pixel visits --website <domain> [--from <iso>] [--to <iso>] [--limit N] [--offset N] | Page-visit timeline scoped to a website host |
myapi pixel events (--campaign-id <id> | --domain <domain>) [--from <iso>] [--to <iso>] [--limit N] [--offset N] | Engagement events (sent / open / click / page_visit). Requires at least one filter: --campaign-id or --domain |
myapi pixel interactions [--website <domain>] [--campaign-id <id>] [--domain <domain>] [--from <iso>] [--to <iso>] [--limit N] [--offset N] | Unified timeline of visits + events |
myapi pixel identity <pixel_id> --website <domain> | Resolve a pixel ID's identity graph (returns {uuid, is_resolved, nodes, …}) |
myapi pixel audience | Geographic distribution sample of your pixel audience |
# Page visits on a funnel host (--website is required for visits)
myapi pixel visits --website acme.com --limit 50
# Engagement events for a campaign (event_type: sent | open | click | page_visit)
myapi pixel events --campaign-id q2-launch --from 2026-06-01 --to 2026-06-30
# Events by domain instead of campaign
myapi pixel events --domain acme.com --limit 100
# Unified timeline (visits + events) — needs at least one filter
myapi pixel interactions --website acme.com
# Resolve a pixel ID's identity graph (--website is required)
myapi pixel identity px_abc123 --website acme.com
# → { "uuid": "...", "is_resolved": true, "nodes": [ ... ] }
# Geographic distribution sample of the org's pixel audience
myapi pixel audience
myapi crm contacts/{id}/events instead (when reserved-kind allows; today event writes are platform-only).my-crm-api is the durable record. Pixel data ages out at ~90 days; CRM events are permanent. If a behavioral signal matters for long-term targeting, promote it into the CRM.Run myapi pixel --help for inline reference.
Backend reads are GA; agent-facing skill content is draft. This skill publishes (status flips from planned to ga in services.ts) once pixel → CRM auto-ingest is wired so the cross-primitive examples above resolve end-to-end.