noon-ads

Noon — Ad Manager

PREREQUISITE: Read ../noon-shared/SKILL.md for login, page structure, and common patterns.

Mechanics for noon Ad Manager. The actual thinking — when to create / tune / kill a campaign, how to research keywords — lives in the three reference files (see § 11).

URL: https://admanager.noon.partners/en-{cc}/home?mpCode=noon&project=PRJ{project_id}

Left nav (ul role=menu): Campaigns, Budget, Billing, Vantage (Beta), Settings. Country switcher at bottom.

1. Campaigns Overview Metrics

Top-level KPI cards:

A time-series performance chart below lets you toggle any metric.

2. Campaign List Filters

• Status (Active/Paused/etc.)
• Ad Type
• Date range

Columns: Performance (chart), ROAS, Revenue, Spends, eCPC, CTR, Orders, Campaign Details, Status, Budget.

3. Campaign Detail Page

URL: admanager.noon.partners/en-{cc}/campaign/details/{campaign_id}?mpCode=noon&project=PRJ{project_id}

Campaign ID format: C_{alphanumeric} (10 alphanumerics after the underscore, e.g. C_XXXXXXXXXX).

Campaign ID extraction from the campaigns list (IDs are in <a href> attributes, not visible text):

browser-use eval "var links = document.querySelectorAll('a[href*=\"/campaign/details/\"]'); var data = []; links.forEach(function(l) { var m = l.href.match(/\/campaign\/details\/([^?]+)/); if (m) data.push({name: l.textContent.trim(), id: m[1]}); }); JSON.stringify(data);"

⚠️ The campaign list is PAGINATED (~15 per page) — that eval only returns the CURRENT page. The footer reads Showing 15 items per page and a pager (1 2 3 4 5 →) sits bottom-right. A single eval captures ~15 campaigns; an account with 70 campaigns across 5 pages will be silently under-reported by ~80% if you stop at page 1. This has produced a real audit that reported "12 active campaigns (all manual targeting)" for a noon account that actually had ~70 campaigns across 5 pages, including Auto-targeting and Product-Ad campaigns the page-1-only read never saw.

Phase 1 (Discover) MUST enumerate every page before concluding the campaign set:

1. Read the pager to learn the last page number, then page through all of them, unioning campaign IDs into one set. The pager is an Ant Design component — click the explicit page-number anchor li.ant-pagination-item-N a (verified reliable 2026-06-08); the generic next-chevron snippet below is an unreliable fallback (the /next|›|→/ match returns no-next on this paginator):

   # RELIABLE: jump to each page by its number, 1..last
   browser-use eval "var a=document.querySelector('li.ant-pagination-item-2 a'); if(a){a.click(); 'page-2';} else 'no-page-2';"
   # how many pages exist:
   browser-use eval "JSON.stringify([...document.querySelectorAll('li.ant-pagination-item')].map(function(li){return li.getAttribute('title')||li.textContent.trim();}));"
   # fallback chevron (often fails on Ant Design — prefer the anchor):
   # browser-use eval "var b=[...document.querySelectorAll('button,a,[role=button]')].find(function(e){return /next|›|→|>/.test(e.getAttribute('aria-label')||e.textContent||'') && !e.disabled;}); if(b){b.click(); 'clicked-next';} else 'no-next';"
   

   Re-extract a[href*="/campaign/details/"] after each page and merge into a de-duped set (IDs repeat if you re-read the same page).
2. Establish the true total before trusting any count: the last pager number × page-size (minus the short last page) is your completeness target. If the distinct campaign-id count you collected is less than (last_page − 1) × 15, you have NOT read every page — keep going. Many noon list footers also expose a page-size selector; bumping it (e.g. 15 → 100) collapses the account to a single page and is the most reliable read when available.
3. Only after the union is complete (count stable, all pages visited) do you have the manifest. Treat a single-page read as a spot-check, never as the full campaign set. The same caveat applies per country — re-paginate after every country switch.