Connect Meta and Google ads sources
Ads sources tell Spiderlook which Meta and Google advertiser libraries to include in daily scans for a rival.
How do I add ads sources?
During Add a Rival, confirm suggested Meta Ads and Google Ads sources, or open the rival Sources tab later and add them manually. Enter the advertiser or library URL the platform exposes publicly when discovery does not suggest one.
After connect, leave Daily scans on for ads sources you care about. The next daily run (or a Refresh) fills the rival Ads tab and Activity ads rows.
How do I verify it worked?
Open the rival Ads tab after scanning completes. You should see creatives or an honest empty state when the library has nothing public. Cross-check Activity filtered to Ads for chronological evidence.
- Source row shows connected on Sources.
- Daily scans is on for the ads source.
- Scan status moves scanning → ready.
- Ads tab or Activity shows new creatives when the library has public ads.
What errors should I expect?
Discovery failed: enter the ads library URL manually and continue. Empty Ads after ready: the platform may hide the advertiser, or the URL may point at the wrong entity — fix the source and wait for the next daily scan. Do not expect second-by-second library refresh; Spiderlook uses the daily schedule plus optional Refresh.
How do ads sources fit the weekly loop?
After ads sources are connected, daily scans fill the rival Ads tab and Activity ads rows. Use that evidence in the weekly competitive review and in sales battlecard prep before client or prospect calls.
Agencies should keep ads sources inside the correct client project so MCP connectors never mix advertiser libraries across accounts. Brands usually keep ads sources on the primary landscape for the category.
If a source row shows connected but Ads stays empty after ready, re-check the advertiser URL, confirm Daily scans is on, and wait for one more daily run before assuming the library is hidden.