[{"data":1,"prerenderedAt":491},["ShallowReactive",2],{"header":3,"footer":289,"blog\u002Fpre-bfcm-ad-account-audit-checklist-what-to-check-before-you-scale":419,"blog-banner":476},{"header":4},{"primaryNavigation":5,"pages":244,"buttonBlock":247,"visibilityButtonBlock":252,"lightswitch":274,"linkField":275,"plainText":277,"announcementStyle":278,"headScripts":279},[6,82,163,169,214],{"buttonLink":7,"dropdown":13},[8],{"ariaLabel":9,"target":9,"url":10,"text":11,"entryType":12},null,"https:\u002F\u002Fpixis.ai\u002Fproducts\u002F","Products","buttonLink_Entry_LinkType",[14],{"buttonLink":15,"tagline":17,"featureLinks":18,"standardLinks":62,"ctaHeading":76,"ctaLink":77},[16],{"ariaLabel":9,"target":9,"url":10,"text":11,"entryType":12},"Own the next era of advertising.",[19,35,49],{"buttonLink":20,"tagline":24,"asset":25},[21],{"ariaLabel":9,"target":9,"url":22,"text":23,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fproducts\u002Fprism\u002F","Prism","Predict outcomes, improve efficiency",[26],{"type":27,"image":28,"mobileImage":34},"image_Entry",[29],{"src":30,"alt":31,"width":32,"height":33},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002FLogos\u002FPrism.png","Prism logo",140,141,[],{"buttonLink":36,"tagline":40,"asset":41},[37],{"ariaLabel":9,"target":9,"url":38,"text":39,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fproducts\u002Fcreative-ai\u002F","Adroom","Your all-in-one creative powerhouse.",[42],{"type":27,"image":43,"mobileImage":48},[44],{"src":45,"alt":46,"width":47,"height":47},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002FLogos\u002FAdroom-logo.png","Adroom logo",80,[],{"buttonLink":50,"tagline":54,"asset":55},[51],{"ariaLabel":9,"target":9,"url":52,"text":53,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fproducts\u002Fpixis-visibility\u002F","Visibility","Be the brand AI recommends",[56],{"type":27,"image":57,"mobileImage":61},[58],{"src":59,"alt":9,"width":60,"height":60},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002Fv-logo-new.svg",39,[],[63],{"heading":64,"links":65},"Platform",[66,71],{"buttonLink":67},[68],{"ariaLabel":9,"target":9,"url":69,"text":70,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fproducts\u002Fintegrations\u002F","Integrations",{"buttonLink":72},[73],{"ariaLabel":9,"target":9,"url":74,"text":75,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fproducts\u002Fcompliance\u002F","Compliance","Seeing is believing",[78],{"ariaLabel":9,"target":9,"url":79,"text":80,"entryType":81},"https:\u002F\u002Fpixis.ai\u002Fget-a-demo\u002F","Get a demo","buttonLink2_Entry_LinkType",{"buttonLink":83,"dropdown":87},[84],{"ariaLabel":9,"target":9,"url":85,"text":86,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002F","Solutions",[88],{"buttonLink":89,"tagline":91,"featureLinks":92,"standardLinks":93,"ctaHeading":158,"ctaLink":159},[90],{"ariaLabel":9,"target":9,"url":85,"text":86,"entryType":12},"No matter your role or goal, Pixis adapts to your needs.",[],[94,117,135],{"heading":95,"links":96},"By use case",[97,102,107,112],{"buttonLink":98},[99],{"ariaLabel":9,"target":9,"url":100,"text":101,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fperformance-budget-optimization\u002F","Performance & Budget Optimization",{"buttonLink":103},[104],{"ariaLabel":9,"target":9,"url":105,"text":106,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Faudience-targeting\u002F","Audience Targeting",{"buttonLink":108},[109],{"ariaLabel":9,"target":9,"url":110,"text":111,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fad-creation\u002F","Ad Creation",{"buttonLink":113},[114],{"ariaLabel":9,"target":9,"url":115,"text":116,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Finsights-monitoring\u002F","Insights & Monitoring",{"heading":118,"links":119},"By team",[120,125,130],{"buttonLink":121},[122],{"ariaLabel":9,"target":9,"url":123,"text":124,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fperformance-teams\u002F","Performance",{"buttonLink":126},[127],{"ariaLabel":9,"target":9,"url":128,"text":129,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fcreative-teams\u002F","Creative",{"buttonLink":131},[132],{"ariaLabel":9,"target":9,"url":133,"text":134,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fagencies\u002F","Agency",{"heading":136,"links":137},"By Industry",[138,143,148,153],{"buttonLink":139},[140],{"ariaLabel":9,"target":9,"url":141,"text":142,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fretail\u002F","Retail",{"buttonLink":144},[145],{"ariaLabel":9,"target":9,"url":146,"text":147,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fconsumer-packaged-goods\u002F","Consumer Packaged Goods",{"buttonLink":149},[150],{"ariaLabel":9,"target":9,"url":151,"text":152,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Fhealthcare\u002F","Healthcare",{"buttonLink":154},[155],{"ariaLabel":9,"target":9,"url":156,"text":157,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fsolutions\u002Ftelecoms\u002F","Telecoms","Looking for a stellar marketing agency?",[160],{"ariaLabel":9,"target":9,"url":161,"text":162,"entryType":81},"https:\u002F\u002Fpixis.ai\u002Fstellar\u002F","Our partner agencies",{"buttonLink":164,"dropdown":168},[165],{"ariaLabel":9,"target":9,"url":166,"text":167,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fpeer-stories\u002F","Peer Stories",[],{"buttonLink":170,"dropdown":175},[171],{"ariaLabel":9,"target":9,"url":172,"text":173,"entryType":174},"#","Knowledge Hub","buttonLink_Custom_LinkType",[176],{"buttonLink":177,"tagline":9,"featureLinks":179,"standardLinks":180,"ctaHeading":210,"ctaLink":211},[178],{"ariaLabel":9,"target":9,"url":172,"text":173,"entryType":174},[],[181,208],{"heading":9,"links":182},[183,188,193,198,203],{"buttonLink":184},[185],{"ariaLabel":9,"target":9,"url":186,"text":187,"entryType":12},"https:\u002F\u002Fpixis.ai\u002F2025-benchmarks\u002F","2025 Benchmark Report",{"buttonLink":189},[190],{"ariaLabel":9,"target":9,"url":191,"text":192,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fblog\u002F","Blog",{"buttonLink":194},[195],{"ariaLabel":9,"target":9,"url":196,"text":197,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fresources\u002F","Resources",{"buttonLink":199},[200],{"ariaLabel":9,"target":9,"url":201,"text":202,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fevents-webinars\u002F","Events",{"buttonLink":204},[205],{"ariaLabel":9,"target":9,"url":206,"text":207,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fpodcasts\u002F","Podcasts",{"heading":9,"links":209},[],"What We Learned from Over $1.8B in Ad Spend on Google & Meta",[212],{"ariaLabel":9,"target":9,"url":186,"text":213,"entryType":81},"Get the 2025 Benchmark Report",{"buttonLink":215,"dropdown":218},[216],{"ariaLabel":9,"target":9,"url":172,"text":217,"entryType":174},"Company",[219],{"buttonLink":220,"tagline":9,"featureLinks":222,"standardLinks":223,"ctaHeading":241,"ctaLink":242},[221],{"ariaLabel":9,"target":9,"url":172,"text":217,"entryType":174},[],[224],{"heading":9,"links":225},[226,231,236],{"buttonLink":227},[228],{"ariaLabel":9,"target":9,"url":229,"text":230,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fabout\u002F","About",{"buttonLink":232},[233],{"ariaLabel":9,"target":9,"url":234,"text":235,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fcareers\u002F","Careers",{"buttonLink":237},[238],{"ariaLabel":9,"target":9,"url":239,"text":240,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fnews-press\u002F","News & Press","Join our ambitious team",[243],{"ariaLabel":9,"target":9,"url":234,"text":235,"entryType":81},[245],{"uri":246},"search-results",[248],{"type":249,"buttonLink":250},"pill-solid-pointer-icon",[251],{"ariaLabel":9,"target":9,"url":79,"text":80,"entryType":12},[253,261,268],{"buttonBlock":254},[255],{"type":256,"buttonLink":257},"pill-solid-light",[258],{"ariaLabel":9,"target":9,"url":259,"text":260,"entryType":174},"https:\u002F\u002Fvisibility.pixis.ai\u002F","Log In",{"buttonBlock":262},[263],{"type":264,"buttonLink":265},"pill-solid-teal",[266],{"ariaLabel":9,"target":9,"url":79,"text":267,"entryType":12},"Book a Demo",{"buttonBlock":269},[270],{"type":249,"buttonLink":271},[272],{"ariaLabel":9,"target":9,"url":259,"text":273,"entryType":174},"Sign up for free",false,{"url":276,"target":9},"https:\u002F\u002Fpixis.ai\u002Fmeet-prism\u002F?utm_source=homepage&utm_medium=banner&utm_content=meet_prism","Meet Prism: Your Always-On, AI-Powered Growth Partner","orange",[280,283,286],{"scriptLabel":281,"scriptContent":282},"Claydar Script","(function() {\n    var script = document.createElement('script');\n    script.async = true;\n    script.src = 'https:\u002F\u002Fstatic.claydar.com\u002Finit.v1.js?id=cng7DR4jnB';\n    var firstScript = document.getElementsByTagName('script')[0];\n    firstScript.parentNode.insertBefore(script, firstScript);\n  })();",{"scriptLabel":284,"scriptContent":285},"Default Pixel","!function(e,t){e.__defaultPixel__={key:\"b80666b3-0a8f-41d0-9241-0d1200c42bde\"};!function e(o){o=o||1;var n=t.createElement(\"script\");n.async=!0,n.src=\"https:\u002F\u002Fhandshake.default.com\u002Findex.js\",n.onload=function(){console.log(\"[Pixel] Script loaded successfully\"+(o>1?\" after \"+o+\" attempts\":\"\"))},n.onerror=function(){console.warn(\"[Pixel] Failed to load script (attempt \"+o+\"\u002F3)\"),o\u003C3?setTimeout((function(){e(o+1)}),2e3*o):console.error(\"[Pixel] Script failed to load after 3 attempts\")},t.head.appendChild(n)}()}(window,document);",{"scriptLabel":287,"scriptContent":288},"lemlist","(function() {\n    var script = document.createElement('script');\n    script.async = true;\n    script.src = 'https:\u002F\u002Fapp.lemlist.com\u002Fapi\u002Fvisitors\u002Ftracking?k=wIUMiMPlcVYKUVOt3B39xWwVNYlRvqDI7LTH9ORCn3c%3D&t=tea_JdKFTAfGe4hC5JgDE';\n    var firstScript = document.getElementsByTagName('script')[0];\n    firstScript.parentNode.insertBefore(script, firstScript);\n})();",{"footer":290},{"footerNavigation":291,"partnerAssets":381,"links":402,"copyRightNotice":418},[292,313,333,337,365],{"buttonLink":293,"dropdown":295},[294],{"ariaLabel":9,"target":9,"url":10,"text":11,"entryType":12},[296],{"links":297},[298,301,304,307,310],{"buttonLink":299},[300],{"ariaLabel":9,"target":9,"url":22,"text":23,"entryType":12},{"buttonLink":302},[303],{"ariaLabel":9,"target":9,"url":38,"text":39,"entryType":12},{"buttonLink":305},[306],{"ariaLabel":9,"target":9,"url":52,"text":53,"entryType":12},{"buttonLink":308},[309],{"ariaLabel":9,"target":9,"url":69,"text":70,"entryType":12},{"buttonLink":311},[312],{"ariaLabel":9,"target":9,"url":74,"text":75,"entryType":12},{"buttonLink":314,"dropdown":316},[315],{"ariaLabel":9,"target":9,"url":85,"text":86,"entryType":12},[317],{"links":318},[319,324,328],{"buttonLink":320},[321],{"ariaLabel":9,"target":9,"url":322,"text":118,"entryType":323},"\u002Fsolutions\u002F#teams","buttonLink_Url_LinkType",{"buttonLink":325},[326],{"ariaLabel":9,"target":9,"url":327,"text":95,"entryType":323},"\u002Fsolutions\u002F#use-cases",{"buttonLink":329},[330],{"ariaLabel":9,"target":9,"url":331,"text":332,"entryType":323},"\u002Fsolutions\u002F#industries","By industry",{"buttonLink":334,"dropdown":336},[335],{"ariaLabel":9,"target":9,"url":166,"text":167,"entryType":12},[],{"buttonLink":338,"dropdown":340},[339],{"ariaLabel":9,"target":9,"url":172,"text":173,"entryType":174},[341],{"links":342},[343,346,349,352,355,360],{"buttonLink":344},[345],{"ariaLabel":9,"target":9,"url":191,"text":192,"entryType":12},{"buttonLink":347},[348],{"ariaLabel":9,"target":9,"url":196,"text":197,"entryType":12},{"buttonLink":350},[351],{"ariaLabel":9,"target":9,"url":206,"text":207,"entryType":12},{"buttonLink":353},[354],{"ariaLabel":9,"target":9,"url":201,"text":202,"entryType":12},{"buttonLink":356},[357],{"ariaLabel":9,"target":9,"url":358,"text":359,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fblog\u002Fprism-frequently-asked-questions\u002F","Prism FAQ",{"buttonLink":361},[362],{"ariaLabel":9,"target":9,"url":363,"text":364,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fglossary\u002F","Glossary",{"buttonLink":366,"dropdown":368},[367],{"ariaLabel":9,"target":9,"url":172,"text":217,"entryType":174},[369],{"links":370},[371,374,378],{"buttonLink":372},[373],{"ariaLabel":9,"target":9,"url":229,"text":230,"entryType":12},{"buttonLink":375},[376],{"ariaLabel":9,"target":9,"url":239,"text":377,"entryType":12},"News & press",{"buttonLink":379},[380],{"ariaLabel":9,"target":9,"url":234,"text":235,"entryType":12},[382,392],{"asset":383},[384],{"type":27,"image":385,"mobileImage":391},[386],{"src":387,"alt":388,"width":389,"height":390},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002FLogos\u002Flogo-meta-business-partner.svg","Meta Business Partner logo",81,36,[],{"asset":393},[394],{"type":27,"image":395,"mobileImage":401},[396],{"src":397,"alt":398,"width":399,"height":400},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002FLogos\u002Flogo-google-partner.svg","Google Partner logo",87,61,[],[403,408,413],{"buttonLink":404},[405],{"ariaLabel":9,"target":9,"url":406,"text":407,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fprivacy-policy\u002F","Privacy Policy",{"buttonLink":409},[410],{"ariaLabel":9,"target":9,"url":411,"text":412,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Fleapus-csr-policy\u002F","Leapus CSR Policy",{"buttonLink":414},[415],{"ariaLabel":9,"target":9,"url":416,"text":417,"entryType":12},"https:\u002F\u002Fpixis.ai\u002Ffulfillment-policy\u002F","Pixis Fulfillment Policy","Pixis",{"uri":420,"id":421,"title":422,"url":423,"postDate":424,"dateUpdated":425,"slug":426,"sectionHandle":427,"type":428,"authors":429,"seo":445,"asset":455,"categories":463,"intro":9,"showBanner":274,"contentArea":469,"articleSelect":475,"schemaOrganization":9,"schemaWebsite":9,"schemaWebpage":9,"schemaBreadcrumb":9,"schemaArticle":9,"schemaFaq":9,"schemaSoftwareApp":9,"siteName":418},"blog\u002Fpre-bfcm-ad-account-audit-checklist-what-to-check-before-you-scale","42435","Pre-BFCM Ad Account Audit Checklist: What to Check Before You Scale","https:\u002F\u002Fpixis.ai\u002Fblog\u002Fpre-bfcm-ad-account-audit-checklist-what-to-check-before-you-scale\u002F","2026-10-30T00:00:00-04:00","2026-10-29T07:25:19-04:00","pre-bfcm-ad-account-audit-checklist-what-to-check-before-you-scale","blog","blog_Entry",[430],{"fullName":431,"asset":432,"position":440,"bio":441,"linkedIn":442,"authorPage":444},"Swetha Venkiteswaran",[433],{"type":27,"image":434,"mobileImage":439},[435],{"src":436,"alt":431,"width":437,"height":438},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002FIMG_6590.jpg",3024,4032,[],"Content Manager","\u003Cp>Swetha brings a storyteller’s eye to topics that can otherwise sound like they were written inside a dashboard. With experience across writing, editing, communications, scriptwriting, and theatre facilitation, she works on making AI, GEO, brand visibility, and performance marketing clearer, warmer, and more useful for marketers. Swetha is Content Manager across Pixis and Stellar\u003C\u002Fp>",{"url":443},"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fswetha-venkiteswaran-0b6a5411a\u002F",[],{"title":446,"description":447,"advanced":448,"keywords":451,"social":452},"Pre-BFCM Ad Account Audit Checklist: What to Check Before You Scale | Pixis","Audit Google and Meta ads before BFCM. Verify purchase tracking, campaign goals, budgets, product feeds, and creative with clear checks and launch criteria.",{"canonical":449,"robots":450},"",[],[],{"facebook":453,"twitter":454},{"description":447,"title":446},{"description":447,"title":446},[456],{"type":27,"image":457,"mobileImage":462},[458],{"src":459,"alt":9,"width":460,"height":461},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002FPre-BFCM-Ad-Account-Audit-Checklist_-What-to-Check-Before-You-Scale.png",1920,1360,[],[464,467],{"title":465,"slug":466},"Budget Management","budget",{"title":23,"slug":468},"prism",[470],{"blocks":471},[472],{"type":473,"textBlock":474},"textBlock_Entry","\u003Cp>\u003Cstrong>Product:\u003C\u002Fstrong> Pixis Prism\u003Cbr \u002F>\u003Cstrong>Meta title:\u003C\u002Fstrong> Pre-BFCM Ad Account Audit Checklist | Pixis\u003Cbr \u002F>\u003Cstrong>Meta description:\u003C\u002Fstrong> Audit Google and Meta ads before BFCM. Verify purchase tracking, campaign goals, budgets, product feeds, and creative with clear checks and launch criteria.\u003Cbr \u002F>\u003Cstrong>Primary keyword:\u003C\u002Fstrong> pre-BFCM ad account audit\u003Cbr \u002F>\u003Cstrong>Secondary keywords:\u003C\u002Fstrong> BFCM audit checklist, Black Friday ad account checklist, Google Ads audit, Meta ads audit, holiday campaign audit\u003Cbr \u002F>\u003Cstrong>Proposed URL:\u003C\u002Fstrong>\u003Ca href=\"https:\u002F\u002Fpixis.ai\u002Fblog\u002Fpre-bfcm-ad-account-audit-checklist\u002F\"> https:\u002F\u002Fpixis.ai\u002Fblog\u002Fpre-bfcm-ad-account-audit-checklist\u002F\u003C\u002Fa>\u003Cbr \u002F>\u003Cstrong>Editorial note:\u003C\u002Fstrong> Technical sources reviewed October 28, 2026. Focus: ecommerce advertisers using Google and Meta. All account examples are hypothetical.\u003C\u002Fp>\u003Ch1>\u003Cstrong>Pre-BFCM Ad Account Audit Checklist: What to Check Before You Scale\u003C\u002Fstrong>\u003C\u002Fh1>\u003Cp>A healthy ROAS report can conceal an unhealthy account. Purchases may be counted twice, a sale ad may point to an unavailable variant, or an old rule may raise budgets using last season's targets. These problems can remain easy to miss until Black Friday increases the cost of every mistake.\u003C\u002Fp>\u003Cp>A pre-BFCM audit should establish whether the account is ready for additional traffic and spending. Start with the purchase signal and buying journey, then inspect the campaign settings, budget controls, and creative that shape delivery. Run the first review in October, leaving time to repair problems and observe the results. For 2026, Black Friday is November 27 and Cyber Monday is November 30.\u003C\u002Fp>\u003Cp>The checklist below covers Google and Meta ecommerce accounts. Work through the explanations where a check fails or needs investigation, and retain evidence of the repair before marking it complete.\u003C\u002Fp>\u003Ch2>\u003Cstrong>Key takeaways\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cul>\u003Cli>Give purchase measurement, checkout, offer accuracy, and spending controls priority over structural improvements.\u003C\u002Fli>\u003Cli>Check the settings used by individual campaigns; an account-level configuration does not establish what every campaign optimizes toward.\u003C\u002Fli>\u003Cli>A finding needs an owner, evidence, and a retest. A setting change alone does not establish that the problem is resolved.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>\u003Cstrong>Your pre-BFCM audit checklist\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cstrong>Purchase measurement:\u003C\u002Fstrong> A test order produces the expected purchase signal, value, currency, and identifiers without unexplained duplication.\u003C\u002Fli>\u003Cli>\u003Cstrong>Checkout and product accuracy:\u003C\u002Fstrong> Priority offers work on mobile and desktop, with consistent prices, availability, variants, and shipping conditions.\u003C\u002Fli>\u003Cli>\u003Cstrong>Campaign goals:\u003C\u002Fstrong> Each campaign uses the intended optimization event and conversion goals.\u003C\u002Fli>\u003Cli>\u003Cstrong>Spending controls:\u003C\u002Fstrong> Rules, scripts, schedules, and connected tools respect approved spending authority.\u003C\u002Fli>\u003Cli>\u003Cstrong>Bidding targets:\u003C\u002Fstrong> Acquisition and return targets reflect the discounted order economics.\u003C\u002Fli>\u003Cli>\u003Cstrong>Reporting:\u003C\u002Fstrong> Revenue definitions, attribution differences, time zones, and conversion delay are understood.\u003C\u002Fli>\u003Cli>\u003Cstrong>Campaign structure:\u003C\u002Fstrong> Product coverage, geographic settings, audience controls, and destinations match the promotion.\u003C\u002Fli>\u003Cli>\u003Cstrong>Creative:\u003C\u002Fstrong> Priority ads carry accurate offers and have usable formats, destinations, and backups.\u003C\u002Fli>\u003Cli>\u003Cstrong>Launch approval:\u003C\u002Fstrong> Critical findings have been repaired and retested, or the affected activity remains inactive.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>\u003Cstrong>Set up the audit so findings turn into repairs\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>Identify the accounts, markets, products, and promotion dates in scope, then name the people responsible for measurement, media, ecommerce, and creative. Keep a record of material settings before changing them, and use representative performance periods that allow for normal conversion delay.\u003C\u002Fp>\u003Cp>For each finding, record the affected campaign or asset, observed problem, supporting evidence, owner, deadline, and required retest. Use three statuses: \u003Cstrong>pass\u003C\u002Fstrong>, \u003Cstrong>fix and retest\u003C\u002Fstrong>, or \u003Cstrong>investigate\u003C\u002Fstrong>. Keep “not applicable” separate so an unused integration does not appear to have passed a test.\u003C\u002Fp>\u003Cp>Prioritize confirmed failures that prevent purchases, distort bidding signals, misrepresent offers, or allow unauthorized spending. These should block the affected launch or expansion until repaired or contained. Suspected fatigue and structural overlap need investigation, but do not automatically justify rebuilding a working account.\u003C\u002Fp>\u003Ch2>\u003Cstrong>1. Verify the purchase signal with a controlled order\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> The store's order record, Google Ads conversion actions and Tag Assistant, and Meta Events Manager's test events and diagnostics.\u003C\u002Fp>\u003Cp>Start from a relevant landing page and complete a controlled purchase through the checkout customers will use. Record the order identifier, time, discount, item value, shipping, tax, and currency. Then compare those details with the events received by the measurement setup.\u003C\u002Fp>\u003Cp>Confirm that the purchase fires at the intended point and that revisiting the confirmation page does not produce an unexplained extra conversion. The event value should follow the agreed revenue definition, rather than merely resemble the order total.\u003C\u002Fp>\u003Ch3>\u003Cstrong>In Google Ads\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Inspect the purchase action's source, status, value settings, currency, counting method, and conversion window. Where transaction identifiers are used, check that the same order retains its identifier when delivered again.\u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F10989978?hl=en\"> Google's Tag Assistant workflow\u003C\u002Fa> helps reproduce the journey and verify website conversion tags, including actions flagged as inactive, unverified, or needing attention.\u003C\u002Fp>\u003Cp>If native Google Ads tracking and an imported analytics purchase action coexist, document the purpose of each. Both can support measurement, but the next campaign-goal check must establish whether they cause bidding to count the same business outcome more than intended.\u003C\u002Fp>\u003Ch3>\u003Cstrong>In Meta\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Inspect the connected dataset and the browser and server events received for the test order. If Pixel and Conversions API both send a purchase, verify that their event names and shared identifiers correspond to the same transaction, while different orders retain distinct identifiers. Use\u003Ca href=\"https:\u002F\u002Fdevelopers.facebook.com\u002Fdocs\u002Fmarketing-api\u002Fconversions-api\u002Fdeduplicate-pixel-and-server-events\u002F\"> Meta's deduplication documentation\u003C\u002Fa> when checking the implementation.\u003C\u002Fp>\u003Cp>Where several plugins or integrations are installed, trace what each sends before removing anything. Also check value, currency, timing, and diagnostic warnings; an active dataset or a strong matching score does not independently prove accurate revenue.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> The known order produces the expected signal and values without unexplained duplication. Verify event delivery separately from ad attribution, since a test without a qualifying advertising interaction may not appear as an attributed conversion.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Run a purchase test that can expose more than a firing tag\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Use one documented transaction to follow the entire event path, then add tests for checkout paths that use different implementations. A standard card checkout and an accelerated wallet checkout may not behave identically, while a bundle or discount can change how item values are passed.\u003C\u002Fp>\u003Col>\u003Cli>Start at a priority ad destination and record the selected variant and displayed price. Use your established debugging tools to inspect the event path without clicking your own live ads simply to create attribution.\u003C\u002Fli>\u003Cli>Add the item to the cart, apply the actual promotion, and complete payment. Retain the order record and the expected revenue calculation, with personal information removed from shared evidence.\u003C\u002Fli>\u003Cli>Inspect received purchase events for the expected identifier, timestamp, value, and currency. Where browser and server copies exist, verify the relationship between them rather than assuming that two incoming copies mean two processed conversions.\u003C\u002Fli>\u003Cli>Reload or revisit the confirmation page and inspect what happens. Some implementations may resend an event but use identifiers to prevent additional counting; the test is whether the same purchase creates an unintended additional conversion.\u003C\u002Fli>\u003Cli>Repeat for materially different payment or checkout paths, then record the result and any exceptions. If consent settings affect delivery, test the supported consent states and confirm the intended behavior with the implementation owner rather than bypassing the user's choice.\u003C\u002Fli>\u003C\u002Fol>\u003Cp>Do not close an implementation issue because the next day's ROAS looks plausible. Retest the exact path that failed. If a plugin and a tag-manager deployment both generate purchases, document which system owns the browser event, which owns the server event, and how they share identifiers before changing either.\u003C\u002Fp>\u003Ch2>\u003Cstrong>2. Check priority offers from product feed to checkout\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> Merchant Center product issues and item details, Meta catalog and product sets, relevant product pages, and checkout on mobile and desktop.\u003C\u002Fp>\u003Cp>Start with the items expected to receive the largest investment, then cover different templates, variants, bundles, and shipping conditions. Compare each product's identifier, availability, price, sale dates, and destination across its feed or catalog and the website. Include structured data where applicable, and test the specific variant promoted in the ad.\u003C\u002Fp>\u003Cp>\u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fmerchants\u002Fanswer\u002F9773429?hl=en\">Google identifies price and availability mismatches as causes of warnings and disapprovals\u003C\u002Fa>. If the website updates before the feed, repair the synchronization process as well as the individual item, then test the next scheduled change. An item can match today and fail again when the sale begins.\u003C\u002Fp>\u003Cp>Complete orders using the advertised discount, relevant payment methods, and shipping threshold. Check that unavailable variants cannot be purchased accidentally and that any replacement destination remains appropriate. For catalog campaigns, verify that event product identifiers correspond to the intended catalog items.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> Priority products and offers remain consistent through checkout, with no unresolved eligibility issue affecting planned activity. Record who pauses or replaces ads when a promoted product sells out.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Test the products that will absorb the budget\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Build the audit sample from the promotion's actual commercial priorities: the products forecast to generate most sales, the items likely to receive the largest advertising allocation, and products with unusual variants or fulfillment rules. Sampling only the top-selling full-price item can miss the bundle or newly created sale page that will carry the campaign.\u003C\u002Fp>\u003Cp>For each sampled item, retain its product identifier, campaign or product-set coverage, destination, advertised price, checkout price, availability, and expected shipping condition. Check the exact variant rather than accepting a parent product page whose cheapest option is unavailable. Where the offer depends on a code, test exclusions, minimum spend, and whether the claimed saving survives at checkout.\u003C\u002Fp>\u003Cp>Include a changeover test. Ask ecommerce to explain how the sale price reaches the website, structured data, and feed, and how those values return to normal afterward. Inspect an actual scheduled update or a representative test rather than relying on an assurance that the sync runs regularly. If the update fails, identify who can correct it and which campaigns must remain inactive until the values match.\u003C\u002Fp>\u003Ch2>\u003Cstrong>3. Inspect the goals each campaign actually uses\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> Google campaign conversion-goal settings and the conversion-action list; Meta ad set conversion location, dataset, and optimization event.\u003C\u002Fp>\u003Cp>A campaign can receive accurate purchase events while optimizing toward something else. If reported conversions look strong but orders do not, inspect the mix before blaming the offer: legacy goals may include easier actions such as registrations or add-to-carts.\u003C\u002Fp>\u003Cp>In Google, review account-default, campaign-specific, and custom goals.\u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F11461796?hl=en\"> Primary conversion actions\u003C\u002Fa> participate in bidding when their relevant standard goal is used; secondary actions normally support observation. Actions included in a custom goal can be used for bidding regardless of that label, so inspect the campaign's selected goal rather than relying on the action list alone.\u003C\u002Fp>\u003Cp>In Meta, confirm that the chosen dataset, conversion location, and optimization event match the campaign's intended role. An earlier funnel event may be deliberate for a separate objective, but its results should not be presented as purchase acquisition performance.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> Every planned campaign has a documented objective and a verified configuration that supports it. Exceptions are intentional and visible in reporting.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Build a campaign-to-goal record\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>For each campaign receiving BFCM investment, record the intended business outcome, selected goal or event, conversion source, reporting column used to judge it, and person responsible for approving changes. This makes exceptions visible across a large account and helps a second buyer understand the setup during coverage.\u003C\u002Fp>\u003Cp>A useful test case is a Google sales campaign with both a native purchase action and an analytics import. Inspect which goals the campaign uses and which actions contribute to its purchase reporting. If both paths describe the same business purchase, establish whether the duplication is intentional observation or an unintended input to bidding. Resolve the goal configuration before using the campaign's reported CPA to approve expansion.\u003C\u002Fp>\u003Cp>For Meta, verify the connected dataset on the campaign's actual ad sets, not just in a central integration screen. An old duplicated campaign may retain a different event or destination setup. When an upper-funnel campaign is intentional, give it its own evaluation criteria so an inexpensive registration is not compared with a purchase as if both outcomes were equivalent.\u003C\u002Fp>\u003Ch2>\u003Cstrong>4. Trace every control that can change spending\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> Campaign and shared budgets where applicable, automated rules, scripts, schedules, account limits, connected optimization tools, billing, and access permissions.\u003C\u002Fp>\u003Cp>Compare the approved promotion allowance with the mechanisms that can alter it. Inspect the scope, time zone, trigger, maximum change, and notification recipient for each material rule, then review a recent execution where history is available.\u003C\u002Fp>\u003Cp>A rule that increases spending above a particular ROAS may still use full-price economics, while another pauses campaigns before delayed conversions arrive. If several tools modify the same setting, define which takes precedence and how their actions are reviewed.\u003C\u002Fp>\u003Cp>\u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F10486637?hl=en\">Google explains that most campaigns can be charged up to twice their average daily budget on a given day\u003C\u002Fa>, subject to applicable limits. Verify delivery against the actual promotion allowance instead of treating the daily budget field as a strict spending cap.\u003C\u002Fp>\u003Cp>Check payment methods and billing issues, then confirm that the people covering the sale can access the accounts and resolve alerts. Temporary rules and settings need an owner and an end-of-promotion review date.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> Every material route to a spending change has a known owner and operates within the approved authorization process.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Test the rules that will run while the team is busy\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Create an inventory of every active automation with its trigger, lookback window, action, scope, time zone, maximum exposure, owner, and notification route. Include manual routines performed by agencies or other team members, since a documented script is not the only source of unexpected changes.\u003C\u002Fp>\u003Cp>Review conditions against a concrete scenario. Suppose a rule raises budgets when same-day ROAS exceeds 4x. Ask what happens early in the day when only a handful of orders have reported, whether repeat executions can compound the increase, and whether the condition uses revenue consistent with the sale's economics. Then check what another rule or tool might do to that same campaign later.\u003C\u002Fp>\u003Cp>Where a rule offers preview or history, use it to inspect which entities would qualify and what previous executions changed. If a safe test cannot be run, review the logic and exposure with the owner, and decide whether the rule should remain active during the event. Preserve its original configuration and document the approved replacement or manual control.\u003C\u002Fp>\u003Cp>Also verify that someone receiving an overspend alert can actually change the relevant setting. Record a backup owner and how the team will confirm that an action succeeded, especially when the primary buyer is unavailable.\u003C\u002Fp>\u003Ch2>\u003Cstrong>5. Test targets against the discounted basket\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> The approved offer economics, campaign CPA or ROAS targets, bidding configuration, and thresholds in automation rules.\u003C\u002Fp>\u003Cp>Ask finance or ecommerce for expected net order revenue, variable costs before advertising, and required contribution. Compare the resulting acquisition allowance with what the campaigns and rules currently permit.\u003C\u002Fp>\u003Cp>For a hypothetical order with $80 in net revenue, $44 in variable costs, and $12 required contribution, allowable acquisition cost is $24. A legacy rule that expands at $30 CPA would breach that requirement even if it worked for a different basket. Reconcile platform-reported revenue with the model's definition before translating the target into a displayed ROAS threshold.\u003C\u002Fp>\u003Cp>Also review temporary seasonality settings.\u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F10369906?hl=en\"> Google recommends seasonality adjustments for major expected conversion-rate changes during short events, ideally one to seven days\u003C\u002Fa>, since Smart Bidding already handles seasonal patterns. Verify the evidence, eligibility, scope, and dates rather than retaining a previous sale's adjustment automatically.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> Targets and rules reflect the approved sale economics, with documented reasons and review dates for temporary settings.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Carry the target into the settings that use it\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>The approved CPA can exist in a planning document while the account still acts on several older numbers. Search the campaign targets, rule thresholds, dashboards, and connected tools for conflicting definitions, then identify which values are controls and which are merely reporting references.\u003C\u002Fp>\u003Cp>Use separate checks where product economics differ materially. If a campaign includes both a high-contribution bundle and a low-contribution single item, verify whether the blended target could allow spending to migrate toward the less profitable product. Record how the team will inspect that mix during the sale and who can change product coverage or authorization.\u003C\u002Fp>\u003Cp>Avoid changing every target merely to standardize the account. If an existing target differs from the commercial limit, establish whether it is an intentional operating setting, whether the actual results remain acceptable, and what evidence would justify an edit. Any change should have a clear purpose and enough time for the team to evaluate its effect.\u003C\u002Fp>\u003Ch2>\u003Cstrong>6. Agree on reporting before the sale tests it\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> Store orders and revenue, Google Ads and Meta reporting settings, analytics definitions, and conversion-delay reports.\u003C\u002Fp>\u003Cp>Create a short reference stating which system supplies total orders and net revenue, how first-time customers are identified, which attribution views support campaign decisions, and how refunds, tax, shipping, currencies, and time zones are handled.\u003C\u002Fp>\u003Cp>Platforms can attribute the same purchase to different interactions, so adding their reported orders does not produce a unique sales total. Investigate unexplained discrepancies while documenting the differences expected from the measurement setup.\u003C\u002Fp>\u003Cp>Review how recent performance changes as conversions arrive.\u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogle-ads\u002Fanswer\u002F9347065?hl=en\"> Google's conversion lag reporting\u003C\u002Fa> helps assess whether the latest results are incomplete. Use the account's evidence to choose a review window instead of applying a universal waiting period.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> The team can explain material differences and knows which numbers are sufficiently complete for a budget decision.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Leave the next buyer a reporting reference they can use\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Save a repeatable review view with spend, purchase volume, purchase value, CPA, ROAS, and the traffic metrics needed for diagnosis. Separate purchase outcomes from broader conversion totals. Include product, market, or customer views only where the underlying data can support them reliably, and note any classification limits.\u003C\u002Fp>\u003Cp>Alongside that view, document the store's order and revenue definitions, platform attribution settings, account time zones, and the expected delay before recent results become useful. Compare the same scope and period when investigating a discrepancy. A transaction-date store report and a platform view assigning purchases to an earlier advertising interaction can disagree without either being broken.\u003C\u002Fp>\u003Cp>For a material unexplained change, identify when it began and compare that timing with tracking releases, account linking, checkout changes, currency changes, and goal edits. Keep the diagnosis specific. A sudden revenue increase without a corresponding increase in store orders deserves an implementation review before it becomes evidence for scaling.\u003C\u002Fp>\u003Ch2>\u003Cstrong>7. Review structure without rebuilding for appearance\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> Active and scheduled campaigns, geographic and audience settings, exclusions, product coverage, and destination controls.\u003C\u002Fp>\u003Cp>Give each campaign a clear role in the promotion. On Google, inspect brand versus non-brand reporting, geographic settings, relevant exclusions, selected products, and dynamically selected destinations. Confirm that the configuration supports the intended offer and does not expose excluded products or unsuitable pages.\u003C\u002Fp>\u003Cp>On Meta, check audience controls, purchaser exclusions where appropriate, retargeting logic, product sets, and destinations. Inspect what the selected setup actually permits rather than assuming a campaign name establishes its delivery boundary.\u003C\u002Fp>\u003Cp>For similar campaigns with little purchase volume, ask whether separation serves a real difference in margins, markets, or customer needs. Overlap merits investigation but does not automatically prove waste. Make material changes only where the findings justify them, preserving the previous settings and allowing time to validate the result.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> Campaign roles and controls are intentional, with no confirmed configuration error or unnecessary duplication left unresolved.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Inspect settings that campaign names do not reveal\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Export or record the live and scheduled campaigns with their objective, bid strategy, budget source, market, product coverage, destination, and status. Compare that record with the promotion plan so an old scheduled campaign does not restart outside the review.\u003C\u002Fp>\u003Cp>For Google, inspect actual location options, search traffic where available, exclusions, and product eligibility rather than relying on naming conventions. For automated destinations, check the controls available in the specific campaign type and test whether selected pages are suitable for the promotion. A general information page may be relevant to the brand while still being a poor destination for a time-limited product offer.\u003C\u002Fp>\u003Cp>For Meta, examine the audience inputs and controls supported by the chosen setup, including any expansion behavior and exclusions. Review overlapping campaigns as a question of purpose, evidence, and manageable complexity; similar audiences alone do not demonstrate that consolidation will improve results.\u003C\u002Fp>\u003Cp>Preserve a before-and-after record for material edits. Write down the failure being corrected, the expected benefit, and the result that would prompt another review. This gives the team a basis for assessing the change beyond whether the account looks tidier.\u003C\u002Fp>\u003Ch2>\u003Cstrong>8. Follow the ad's promise through the buying journey\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> Priority ad previews, landing pages, recent creative performance, the approved asset library, and replacement schedules.\u003C\u002Fp>\u003Cp>Open the formats that will actually run, then follow each priority destination. Verify the offer, exclusions, available product, and readability on mobile. A bundle should explain what is included, while the landing page should make the advertised price and variant easy to find.\u003C\u002Fp>\u003Cp>Separate confirmed errors from performance concerns. Incorrect prices, expired claims, and broken destinations need repair before delivery. Falling CTR or rising frequency calls for analysis alongside purchase results, audience changes, and placement mix before concluding that the creative is fatigued.\u003C\u002Fp>\u003Cp>Check that backups solve foreseeable problems: a sold-out product, a weak concept, an unavailable format, and the end of the offer. The person covering the account should be able to find approved replacements and destinations without waiting for the original creator.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> Core ads are accurate and usable, with working destinations, approved replacements, and a clear end-of-sale plan.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Keep a usable creative readiness record\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>For each priority concept, record the product, buying argument, offer version, available formats, destination, approval status, and replacement. Describe concepts by what they help the customer understand, such as product capacity, assembly, or bundle value, so the team can distinguish a new argument from a visual variation.\u003C\u002Fp>\u003Cp>Review evidence at a level the data can sustain. If an ad has very few purchases, do not declare it the account's best acquisition concept solely because its CTR is high. For ads with more history, inspect changes in spend, audience, placement, and offer alongside response and purchase performance before attributing deterioration to fatigue.\u003C\u002Fp>\u003Cp>Finally, rehearse the substitution process. If the hero item sells out, can the covering buyer locate an approved replacement, confirm its margin and destination, and remove the old promise? A backup asset that requires a new offer approval and an unfinished product page is not ready to use.\u003C\u002Fp>\u003Ch2>\u003Cstrong>9. Retest the repairs and approve the affected launch\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Cstrong>Where to look:\u003C\u002Fstrong> The findings log, changed settings, repeated purchase tests, and the final campaign schedule.\u003C\u002Fp>\u003Cp>A finding remains open until its repair passes the required test. After tracking or checkout changes, repeat the affected purchase journey; after feed changes, inspect the updated items and destinations; after goal or rule changes, verify the actual campaign configuration.\u003C\u002Fp>\u003Cp>For example, an audit might find duplicate purchase actions, a delayed feed update, and insufficient creative backups. Measurement, ecommerce, and creative owners should receive distinct tasks with their own closure evidence. Treating all three as a single readiness concern makes accountability harder.\u003C\u002Fp>\u003Cp>The launch decision should identify what can run, what remains inactive, and what still needs investigation. An isolated product issue may be contained by excluding that item, while a corrupted purchase signal used across campaigns needs a broader decision. Retest relevant checks after subsequent material changes, even if the October audit passed.\u003C\u002Fp>\u003Cp>\u003Cstrong>Pass when:\u003C\u002Fstrong> Launch-blocking findings are repaired or verified as contained, remaining risks have named owners, and the final configuration matches the approved plan.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Make the final handoff explicit\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Use a single findings log rather than separate lists in messages and dashboards. A useful record reads: “Purchase action includes an unintended duplicate source; affects campaigns A and B; measurement owner to correct; media owner to verify selected goals; close only after a new test order and campaign-setting review.” Attach the evidence and dates so the next person does not have to reconstruct the investigation.\u003C\u002Fp>\u003Cp>Before approving launch, have the relevant owners confirm three things: the repair is deployed, the defined retest has passed, and no subsequent change has invalidated it. If an issue remains, specify the activity being withheld and how that containment was checked. Do not label an unresolved item as passed merely because its deadline has arrived.\u003C\u002Fp>\u003Cp>Schedule the next verification around changes that can undo earlier work, including a checkout release, a tracking deployment, a feed migration, a new sale page, or a material campaign duplication. The October audit establishes a baseline; the final check confirms that the launch still uses that baseline or a documented, tested update.\u003C\u002Fp>\u003Ch2>\u003Cstrong>Use Prism to identify where an audit needs a closer look\u003C\u002Fstrong>\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fpixis.ai\u002Fproducts\u002Fprism\u002F\">Pixis Prism\u003C\u002Fa> supports conversational campaign analysis, monitoring, and optimization recommendations. Use it to focus an investigation, for example by comparing spend, purchase volume, and acquisition cost across equivalent periods and identifying material changes before the promotion.\u003C\u002Fp>\u003Cp>Confirm the connected data and reporting scope, then take the findings into the relevant check. An abrupt improvement after a tracking update might warrant testing purchase events for duplication; it does not establish duplication by itself. Stock and margin assumptions also need separate verification where they are not connected.\u003C\u002Fp>\u003Cp>The useful outcome is a specific task with evidence and an owner.\u003Ca href=\"https:\u002F\u002Fpixis.ai\u002Fproducts\u002Fprism\u002F\"> Explore Pixis Prism\u003C\u002Fa> to discuss how campaign analysis can support your team's audit and ongoing optimization workflow.\u003C\u002Fp>\u003Ch2>\u003Cstrong>Frequently asked questions\u003C\u002Fstrong>\u003C\u002Fh2>\u003Ch3>\u003Cstrong>When should a pre-BFCM audit happen?\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Start in October so repairs can be tested before the sale. If you begin later, prioritize measurement, checkout, offer accuracy, and spending controls. Repeat affected checks after material changes and shortly before launch.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Should platform revenue match store revenue?\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Not exactly. Attribution, reporting dates, consent, processing delays, and revenue definitions can differ. Document expected differences and investigate unexplained ones rather than forcing the totals to match.\u003C\u002Fp>\u003Ch3>\u003Cstrong>Should an audit lead to a complete campaign rebuild?\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Only when the findings justify it. Fix verified problems first and evaluate structural changes against a defined benefit, with enough time to assess their effects before the promotion.\u003C\u002Fp>\u003Ch3>\u003Cstrong>What should block launch?\u003C\u002Fstrong>\u003C\u002Fh3>\u003Cp>Confirmed failures that prevent purchases, materially misstate the offer, corrupt bidding signals, or permit unauthorized spending should block affected launch or expansion until repaired or contained. A suspected improvement opportunity requires investigation rather than an automatic stop.\u003C\u002Fp>",[],{"blogBanner":477},{"bannerIcon":478,"bannerBrandName":483,"bannerHeading":488,"bannerCta1Text":489,"bannerCta1Url":79,"bannerCta2Text":490,"bannerCta2Url":259},[479],{"url":480,"title":481,"width":482,"height":482},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002Fv-logo.svg","V logo",78,[484],{"url":485,"title":486,"width":487,"height":60},"https:\u002F\u002Fd191k2rrohvvg6.cloudfront.net\u002Fimages\u002Fvisibility-logo.svg","Visibility logo",191,"Increase your visibility on Google and AI search","Book a demo","Signup for free",1793339196238]