Edition 2.0

The guides, rebuilt for how these platforms work now.

Each guide was rewritten from current platform documentation, with worked examples, numbered figures, and a clear line between what is fine while you test and what production needs.

Free. Sign up once with your name, email and phone number to open all three guides on this device.

  1. AI Media Buying

    How to use Claude for research, diagnosis, reporting and creative operations on Meta, and how to let it propose changes without ever handing it the budget.

    14 chapters, about 180 minutes of reading. For media buyers, performance marketers and agency teams.

    What changed since V1

    • Meta now runs most delivery decisions itself. The AI’s job moved from tweaking bids to diagnosing, briefing creative and proposing changes.
    • Credentials are split by environment: short-lived tokens for testing, system users for production, and no token ever inside the model’s context.
    • Official connectors and Agent Skills replace copy-pasted scripts and prompt-only guardrails.
    • Every write goes through a proposal, a human approval and a deterministic executor that creates objects paused.
  2. Claude Ads

    The supported ways to connect Claude to Meta advertising in 2026, from Meta’s hosted MCP server to your own Marketing API integration, with the exact credential to use in development and in production.

    12 chapters, about 170 minutes of reading. For technical media buyers, agencies and automation developers.

    What changed since V1

    • Meta now hosts an official ads MCP server (open beta since 29 April 2026) that can create, edit and activate ads. The confirmation step lives in your AI client.
    • Development and production use different Meta credentials on purpose: short-lived tokens on the Limited tier for testing, 60-day expiring system users on the Full tier for production.
    • Claude’s connector directory now serves Claude apps, Claude Code and Cowork, and Anthropic is explicit that verification is not a security audit.
    • The MCP authorization spec requires tokens bound to the server they are for and forbids passing them through to other services.
  3. Shopify Integrations

    Choosing between the Claude connector, Shopify’s AI toolkit and your own app; current authentication and token lifetimes; webhooks; and the write protocol that keeps a store safe.

    14 chapters, about 185 minutes of reading. For Shopify merchants, agencies and developers.

    What changed since V1

    • Custom apps can no longer be created in the Shopify admin (since 1 January 2026). New apps start in the Dev Dashboard or Shopify CLI.
    • Offline tokens now expire after an hour and refresh with a 90-day refresh token. Public apps must migrate before 1 January 2027.
    • Shopify’s own Claude connector can change products, inventory, new discount codes and unpublished theme copies. Orders and customers stay read-only, and refunds, cancellations and gift cards are blocked even with write access.
    • Admin API 2026-10 is current. Inventory writes need compare-and-swap and some mutations require idempotency keys since 2026-04.

These guides are education, not legal, security or financial advice. Platform rules change; each chapter shows the date its facts were checked and links the primary sources. Verify against those sources before you build, and never paste a live credential into an AI chat.