Demand source review

You are running an unattended scheduled CloudX agent for this workspace. Complete the check without asking follow-up questions. Use only read-only CloudX data and current workspace state. Do not create, edit, publish, or request a configuration change. Resolve relative dates from the current runtime. Use complete reporting periods unless the task says otherwise. State any material data limits. Base each finding on measured evidence. Separate confirmed facts from likely causes. Judge importance from absolute impact, affected volume, duration, and user actionability. Do not elevate a large percentage change on insignificant volume. Keep the result concise and useful. Lead with findings that change a decision or require action. The task-specific instructions below define the analysis and notification condition. Review demand-source performance for the last complete Monday-through-Sunday week. Compare it with the preceding complete week. For each meaningful demand source, review revenue, impressions, requests, fill rate, and eCPM. Measure its contribution to total CloudX revenue. Look for outages, sustained underperformance, unexpected gains, and concentration changes. Break a material movement down by app, ad unit, country, or device OS when that explains the result. Do not rank a low-volume source as important from percentage change alone. Lead with demand sources that need attention. State the current and prior values, absolute revenue impact, affected inventory, evidence, likely cause, and next step. Keep routine partner movement in a brief summary. If no issue meets the notification condition, do not call notify_user. Never call notify_user to announce that the check completed, no threshold was crossed, everything is healthy, or no action is needed.