X Ads
Audits X Ads measurement, X Pixel and Conversions API, campaign objectives, keyword and conversation targeting, creative, budgets, brand safety, app measurement, and reporting. Controls keep organic signals separate from paid attribution and check that conversion events comply with X data-use policy.
/ads xInstalled as a plugin? The same command is namespaced: /claude-ads:ads x
What the audit covers
- X Pixel and Conversions API
- Campaign objectives and structure
- Keyword and conversation targeting
- Creative
- Budgets
- Reporting
- Account eligibility
- Brand safety
Measurement stack
- X Pixel
- Conversions API
- Mobile measurement partners
Each measurement surface is verified from your account evidence, never assumed. Findings carry explicit confidence: high, medium, low, or none.
Run this when
- Audit an X Ads account inherited from legacy Twitter Ads setups
- Verify X Pixel and Conversions API events and deduplication
- Review keyword and conversation targeting against your objective
- Check brand-safety controls and account eligibility before a campaign
Guardrails
- Organic signals stay separate from paid attribution and optimization claims
- Conversion events are checked against X data-use policy and sensitive categories
- Optional or ineligible features stay unscored
- Every account change stays a draft until the mutation gate passes
Questions
Does the audit mix organic and paid performance?
No. A reporting control keeps organic signals separate from paid attribution and optimization claims, and date windows, attribution, currency, and metric definitions must be consistent.
What does it check on measurement?
X Pixel and Conversions API setup, identifiers and event values, browser and server deduplication, and a supported mobile measurement path for app campaigns.