apify-influencer-brand-collabs

por apify

Descubre asociaciones entre marcas y creadores de Instagram encadenando Apify Actors. Úsalo cuando el usuario pregunte quién colabora con una marca, qué marcas ha hecho pagadas un creador…

npx skills add https://github.com/apify/awesome-skills --skill apify-influencer-brand-collabs

Influencer–Brand Collaborations

Surface Instagram branded-content partnerships by chaining four Apify Actors against Meta's Ad Library. Distilled from the production influencer-brand-collabs mini-tool.

When to use

  • "Who has Nike paid to promote them this quarter?"
  • "What brands does @bellahadid do sponsored posts for?"
  • Auditing an account's branded-content history
  • Building a competitor's influencer roster

Don't use for: organic mentions or tags (use a hashtag/mentions scraper), TikTok or YouTube collabs (different platforms), generic competitor ads (query Meta Ad Library directly).

Inputs to gather

  1. Instagram handle or URL@adidas or https://www.instagram.com/adidas/
  2. Lookback window — days; default 90
  3. Enrichment toggles (each adds cost + time):
    • Content insights — likes, comments, views per collab
    • Profile enrichment — followers, bio, verified status of the other side

Direction (brand vs creator) is detected empirically. Do not ask.

The pipeline

#ActorPurposeRequired
1apify/instagram-profile-scraperResolve the target's Facebook fbid
2apify/brand-collaboration-scraperPull branded-content posts from Meta's Ad Library
3apify/instagram-post-scraper + apify/instagram-reel-scraperEngagement metricsoptional
4apify/instagram-profile-scraper (again)Enrich the result-side partnersoptional

Call each via mcp__claude_ai_Apify__call-actor. Use mcp__claude_ai_Apify__fetch-actor-details first if you've never run one of these and want the exact input schema.

Step 1 — Resolve the target

// actor: apify/instagram-profile-scraper
{ "usernames": ["adidas"] }

Grab fbid from the first item. No fbid → can't query Ad Library → stop and tell the user. Most common cause: private account.

Step 2 — Build the Meta Ad Library URL

https://www.facebook.com/ads/library/branded_content/?id={fbid}&query={username}&target=instagram&start_date={YYYY-MM-DD}&end_date={YYYY-MM-DD}

Date range = the lookback window (default 90 days, ending today).

Step 3 — Fetch collaborations

// actor: apify/brand-collaboration-scraper
{ "startUrls": ["<ad library url>"], "resultsLimit": 10 }

Schema is fixed: every item has creator (always the influencer side) and brandPartners[0] (always the brand side). Do not try to infer direction from these fields.

Step 4 — Detect direction empirically

Count how often the target username appears on each side of the results:

  • target appears more on creator side → target is the influencer; results are the brands
  • target appears more on brandPartners side → target is the brand; results are the creators

⚠️ Do not use isBusinessAccount to infer this. It's unreliable — e.g. @fifaworldcup is a business account but appears as the creator of its own branded content.

Step 5 — (optional) Content metrics

Split collab URLs by type:

  • /reel/... → reel scraper
  • /p/... or /tv/... → post scraper
// actor: apify/instagram-post-scraper
{ "username": ["<post urls>"], "resultsLimit": 1, "dataDetailLevel": "basicData" }

// actor: apify/instagram-reel-scraper
{ "username": ["<reel urls>"], "resultsLimit": 1 }

Match back to collabs via shortcode in the URL: /(p|reel|tv)/([A-Za-z0-9_-]+).

Engagement formula: likesCount + commentsCount + (videoViewCount ?? videoPlayCount ?? 0).

Run the two scrapers in parallel — they're independent.

Step 6 — (optional) Enrich the result side

Collect unique usernames from the side that is not the target. Then:

// actor: apify/instagram-profile-scraper
{ "usernames": [<unique result-side usernames>] }

Only enrich the side the user actually cares about. The input handle is already known.

What to present

After aggregation, surface:

  • Headline counts: total collabs, unique partners, total engagement (if metrics enriched)
  • Top 5 collabs by engagement — only meaningful when content insights were toggled on
  • Content-type mix: Post vs Reel; Reels usually dominate engagement
  • Weekly timeline across the date range — spikes reveal campaign launches
  • Per-partner card (when profiles enriched): handle, full name, followers, verified, category, collabs in this run, avg engagement

For who-questions, the partner list alone is enough. Metrics only matter for which-was-best-questions.

URL parsing

Strip Instagram's _u/ and _n/ deep-link prefixes before extracting the handle:

/instagram\.com\/(?:_u\/|_n\/)?([A-Za-z0-9_.]+)/i

These slugs are not usernames — skip them: explore, reels, stories, direct, accounts, about, p, reel, tv, tags, locations, _u, _n.

Pitfalls

  • Target is private → profile scraper returns no fbid. Bail early with a clear message.
  • No results → try in order: widen the date range, double-check the handle (strip _u/), confirm the account actually runs branded content. Meta only indexes ads they've classified as branded content.
  • Engagement is all zeros → user skipped content enrichment. Offer to re-run with it on.
  • Direction looks wrong in the output → re-check the empirical count. Don't trust isBusinessAccount.
  • Brand collabs with no metrics are still answer-shaped for who questions — don't gate the whole flow on enrichment.

Cost & time

Full 4-actor run: ~3–5 minutes, a few cents of Apify compute. Order of magnitude:

EnrichmentActors runApprox time
None21–2 min
+ Content3–42–4 min
+ Profiles+1+30–60 s

If the user just needs a partner list, skip both toggles.

Reference implementation

Production route this skill was distilled from: mini-tools-main/src/app/api/tools/influencer-brand-collabs/route.ts — full transformation logic, error handling, and slimmed display shapes for each scraper's output.

Más skills de apify

bug-triage
apify
Triage de issues de bugs abiertos en apify/apify-mcp-server. Analizar, redactar respuestas, obtener aprobación, publicar.
official
dig
apify
Habilidad flexible para explorar, planificar y especificar trabajo en el servidor Apify MCP. NO edites archivos fuente — esta habilidad es solo para comprensión y planificación.
official
apify-financial-news
apify
Descubre y extrae noticias financieras para empresas de cartera rastreadas en 33 fuentes verificadas de primer nivel (Bloomberg, Reuters, FT, WSJ, IntelliNews, ČTK, PAP, BTA,…
official
apify-actor-development
apify
Crear, depurar e implementar programas en la nube sin servidor para web scraping, automatización y procesamiento de datos. Compatible con plantillas de JavaScript, TypeScript y Python con las bibliotecas integradas Crawlee, Playwright y Cheerio para rastreo HTTP y basado en navegador. Incluye pruebas locales mediante apify run con almacenamiento aislado, validación de esquemas para entradas/salidas e implementación en la plataforma Apify mediante apify push. Requiere autenticación de Apify CLI y metadatos obligatorios generatedBy en .actor/actor.json para IA...
official
apify-actorization
apify
Convierte proyectos existentes en Apify Actors sin servidor con integración de SDK específica para cada lenguaje. Soporta JavaScript/TypeScript (con Actor.init() / Actor.exit()), Python (gestor de contexto asíncrono) y cualquier lenguaje mediante envoltorio CLI. Proporciona un flujo de trabajo estructurado: apify init para crear la estructura, aplicar envoltorio SDK, configurar esquemas de entrada/salida, probar localmente con apify run y luego desplegar con apify push. Incluye validación de esquemas de entrada y salida, contenedorización Docker y opcional pago por evento...
official
apify-generate-output-schema
apify
Generar esquemas de salida (dataset_schema.json, output_schema.json, key_value_store_schema.json) para un Apify Actor analizando su código fuente. Úselo cuando…
official
apify-ultimate-scraper
apify
Raspador web automatizado que selecciona los Actores óptimos para más de 55 plataformas, incluyendo Instagram, TikTok, YouTube, Facebook, Google Maps y más. Cubre más de 55 Actores preconfigurados en 8 plataformas principales con orientación de selección específica para casos de uso (generación de leads, descubrimiento de influencers, monitoreo de marca, análisis de competencia, investigación de tendencias). Admite tres formatos de salida: visualización rápida en chat, exportación CSV o exportación JSON con límites de resultados personalizables. Incluye patrones de flujo de trabajo con múltiples Actores para casos complejos...
official
apify-audience-analysis
apify
Extrae datos demográficos de la audiencia, patrones de participación y comportamiento de Facebook, Instagram, YouTube y TikTok. Compatible con más de 18 actores especializados que cubren datos demográficos de seguidores, métricas de participación, comentarios y análisis de perfiles en las cuatro plataformas. Ofrece tres formatos de salida: visualización rápida en chat, exportación CSV o exportación JSON para análisis posteriores. Requiere token de Apify y la herramienta CLI mcpc; utiliza obtención dinámica de esquemas para adaptar las entradas a los requisitos de cada actor. Incluye estructura...
official