Skip to content

fix(platform): add Instagram Ads to PLATFORM_REGISTRY (BUI-299)#92

Merged
maciejwitowski merged 1 commit intomainfrom
fix/bui-299-instagram-ads-registry-entry
Mar 30, 2026
Merged

fix(platform): add Instagram Ads to PLATFORM_REGISTRY (BUI-299)#92
maciejwitowski merged 1 commit intomainfrom
fix/bui-299-instagram-ads-registry-entry

Conversation

@maciejwitowski
Copy link
Copy Markdown
Contributor

@maciejwitowski maciejwitowski commented Mar 30, 2026

Summary

  • Adds a dedicated instagram-ads entry to the PLATFORM_REGISTRY so that clicking "Instagram Ads" on the home page loads the correct ads data (instagram.ads scope) instead of falling back to regular Instagram data
  • Sets showInConnectList: false since the main Instagram connector already exports ads — this entry exists purely for data resolution

Root cause

The instagram-ads-playwright connector (added in vana-com/data-connectors#38) had no matching registry entry. Without one, the source page has no ingestScope, so it falls back to loading whatever data it finds for company "Meta" — which is the regular Instagram posts data.

Test plan

  • Open DataConnect, go to home page
  • Verify "Instagram Ads" card appears (loaded from connector files)
  • Click "Instagram Ads" → source page should show ads data (advertisers, ad topics), not Instagram posts
  • Verify regular "Instagram" still works and shows profile + posts data
  • Verify Instagram Ads does NOT appear as a separate option in the connect flow (only in "Your data" if already connected)

🤖 Generated with Claude Code

The instagram-ads-playwright connector had no registry entry, so
clicking it on the home page resolved to the regular Instagram
data instead of the ads data. Add a dedicated entry with
ingestScope "instagram.ads" so the source page loads correctly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@maciejwitowski maciejwitowski merged commit 72087f6 into main Mar 30, 2026
@maciejwitowski maciejwitowski deleted the fix/bui-299-instagram-ads-registry-entry branch March 30, 2026 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant