Meta Advantage+ 31 enhancements, 17 labeled AI (reported): audit sheet

LeapBuzz reports 31 Advantage+ creative enhancements, 17 labeled as AI, 10 on by default. A per-campaign audit sheet and a small Python tally to keep.

4 min readSume
All posts

Keep one row per enhancement per campaign, and mark which ones you switched on. LeapBuzz reports that Advantage+ Creative has 31 enhancements, that 17 of them are labeled as AI, and that 10 are on by default, including music on Reels ads (read 2026-10-02 from a search snippet; the page itself was not opened). Counts like these change, so treat them as a prompt to look at your own account, not as Meta's figures.

What should the audit sheet record?

The point is to know, six weeks later, what the shown ad looked like. A clip you rendered with Sume is fixed; an enhancement can change the shown version. The sheet should say which version a viewer could have seen.

Audit sheet columns
ColumnExample
CampaignFall promo
Enhancement nameAs shown in Ads Manager
On or offOn
Labeled AI in Ads Manager?Yes
Date checked2026-10-02
Source clip job idjob id from your Sume record

How do you tally it?

Export your own sheet to CSV with columns named on_or_off and labeled_ai, and count the rows. This does not call Meta; it only reads the file you keep.

import csv
from collections import Counter

c = Counter()
with open('enhancements.csv') as f:
    for r in csv.DictReader(f):
        if r['on_or_off'].lower() == 'on':
            c['on'] += 1
            if r['labeled_ai'].lower() == 'yes':
                c['on_and_labeled_ai'] += 1
print(dict(c))

Why keep the source job id?

Because the clip you uploaded is the part you control. A Sume job id points back to the request and result for that render, so you can find the original file even if the shown ad was altered.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume