mx-asin-target-negation

Automate ASIN target negation by evaluating PDP form-factor overlap and lifetime performance across campaigns. This process separates clean negate candidates from review buckets, reducing manual workload for auto campaigns and category targeting paths.

ASIN negation analysis requires MySQL database access to keywordtargetingmetric and targetexpressionsmetric tables. A brand context file is also necessary to properly evaluate buyer intent and form-factor matching for targeted products.

PDP inspection for relevance assessment evaluates form-factor overlap and buyer intent matching against your brand context. It checks lifetime performance by location, campaign, and ad group to identify clear negation candidates.

Yes, you can render HTML reports for campaign negation reviews. The process uses pypdf and pdfplumber for document processing to output structured HTML reports detailing ASIN performance and negation recommendations.

Yes, MySQL is required to run ASIN target negation reviews. The system queries the keywordtargetingmetric and targetexpressionsmetric tables within your MySQL database to extract the performance data needed for evaluation.

You should review ASIN targets matched through auto campaigns and category targeting when assessing phase 2 negation. Evaluate targets showing poor form-factor overlap or low lifetime performance to separate immediate negation candidates from watch buckets.