mbfinotti/advertising-skills / skills/ad-attribution-gap
ad-attribution-gap
VerifiedQuantify and explain the discrepancy between ad platform reporting, an analytics tool, and the source of truth (CRM or order system), classifying every unit of the gap as timing, definitional, or unexplained residual. Use whenever the user says the numbers don't match, that the platform reports more conversions or revenue than the CRM or order system, or mentions cross-platform reconciliation, double-counted conversions, an attribution discrepancy, or asks whether a reporting gap is normal - even if they never say 'attribution'. Covers B2B (CRM-anchored) and B2C/ecommerce (order-system-anchored). Do NOT use to fix broken or missing tracking - use mbfinotti/advertising-skills@ad-conversion-tracking instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 33.4 KB |
| evals/evals.json | config | 33.0 KB |
| references/reconciliation-examples.md | markdown | 12.4 KB |
evals/evals.json
View on GitHub{
"skill_name": "ad-attribution-gap",
"evals": [
{
"id": 1,
"prompt": "I run growth at Maren & Oak, a DTC furniture brand on Shopify. For March, Meta reported 1,912 purchases and $412k in revenue, our analytics tool shows 1,104 purchases, and Shopify shows 1,351 paid orders and $296k. My CEO wants one number and asked me to get these three systems to agree. Can you reconcile them so they all show the same figure? One wrinkle: Meta's revenue includes shipping and tax, the Shopify report we use excludes them I think. We also processed about $18k of refunds in March.",
"expected_output": "A reconciliation setup that anchors on Shopify, normalizes all three systems to a common basis, classifies gap causes into timing/definitional/residual buckets, and explicitly refuses to make the three systems show one identical figure.",
"files": [],
"expectations": [
"Refuses to make the three systems agree on a single identical figure, and states that a perfect match would indicate a fabricated or hidden adjustment rather than rigor.",
"Anchors the conversion count and revenue on the Shopify order system, not on Meta or the analytics tool.",
"States that the ad platform and analytics explain where conversions came from, never how many there were.",
"Requires normalization to a common basis before comparing any numbers, naming at least date basis, timezone, and conversion definition as axes to align.",
"Identifies the platform's ad-interaction-date (click-date) stamping vs the order system's event-date stamping as a specific cause of misalignment.",
"Recommends one revenue basis of net revenue excluding tax and shipping, applied to every system, to resolve the Meta-includes-shipping-and-tax mismatch.",
"Treats the $18k of refunds as a definitional line (source of truth records reversals the platform and analytics rarely reverse), not as a tracking defect.",
"Carries view-through conversions as a definitional line pushing the platform's count higher, to be segmented out or quantified rather than treated as a bug.",
"Flags modeled or estimated conversions on the platform side and requires they never be compared to deterministic order counts without being labeled as modeled.",
"Classifies gap causes into exactly three buckets: timing, definitional, and unexplained residual.",
"States that an explicit unexplained residual must remain in the final report and must not be driven to zero.",
"Computes or sets up the gap per source pair (Meta vs orders, analytics vs orders) in absolute units and as a percentage of the anchor, rather than one blended three-way number.",
"Explains the analytics undercount (1,104 below 1,351 orders) through analytics-low mechanisms such as consent loss, ad blockers, or cross-device breaks, rather than suggesting the order count is inflated."
]
},
{
"id": 2,
"prompt": "Quick sanity check for my agency report at Bluewater Peak Supply. Last month Google Ads says 640 conversions, Meta says 510, TikTok says 210 - that's 1,360 total from paid - but our order system only logged 780 paid-attributed orders. So paid is over-reporting by 74%, right? Google alone claims 640 while the order data credits Google-tagged orders at about 330, which feels insane. Ad spend across everything was $96k and total revenue was $402k. How do I write up this over-count for the client?",
"expected_output": "A write-up that rejects the 1,360 sum, treats platform claims as overlapping against the 780 anchor, flags Google's roughly 1.9x ratio for double-counting investigation, and uses MER as a blended cross-check.",
"files": [],
"expectations": [
"Rejects summing 640 + 510 + 210 into a 1,360 paid total as invalid.",
"States that the true conversion count is 780 (the order system's number) with overlapping platform claims on it, not 1,360 conversions.",
"Refuses to report a '74% over-count' as the user computed it.",
"Explains cross-platform self-crediting (several platforms each claiming the same conversion) as a definitional cause to quantify, not a defect to fix.",
"Flags Google's 640 claimed vs roughly 330 anchor-credited (about 1.9x) as exceeding the roughly 1.5x ratio that suggests double-counting.",
"Labels the 1.5x ratio as a practitioner heuristic, not a standard.",
"Routes the suspected double-counting to the unexplained-residual/investigation bucket rather than accepting it as a documented definitional line.",
"Computes MER as total revenue divided by total ad spend from the source of truth (about 4.2 from $402k over $96k) as a blended cross-check.",
"Treats MER as a cross-check that sidesteps per-platform attribution, never as a target to hit, and does not present any cited MER figure as a benchmark to reach.",
"Requires normalizing date basis, attribution windows, and view-through/modeled inclusion per platform before quantifying each platform's gap.",
"Names the counting-rule difference (some platforms count every conversion per click, others count one) as a definitional candidate for part of the excess.",
"Computes each platform's gap as its own pair against the 780 anchor with sign, rather than one aggregate paid-vs-orders figure."
]
},
{
"id": 3,
"prompt": "I do marketing ops at Ferrostack, a B2B data-integration SaaS with roughly $40k ACV. I pulled all deals closed-won in Q2 from our CRM - 23 deals, $920k - and compared against LinkedIn Ads, which only claims credit for 4 of them. Our offline conversion uploads are keyed on the LinkedIn click ID we store on each lead, and the ops dashboard says only 38% of Q2 leads have a click ID on file. My CMO says this proves LinkedIn isn't working - last-touch shows it clearly - and wants me to rerun everything under a different attribution model to see if it looks better. Can you tell me how big our attribution gap really is, in percent?",
"expected_output": "A B2B reconciliation that re-cohorts by lead creation date, flags the 38% match rate as a capture defect, refuses the mid-analysis model switch, and reports absolute units alongside percentages.",
"files": [],
"expectations": [
"Rejects cohorting by Q2 close date and requires cohorting by lead creation date instead.",
"Explains that a close-date pull mixes cohorts the platforms saw months apart, because of lead-to-close lag.",
"Flags the 38% click-ID match rate as below the roughly 50% threshold that indicates a capture defect, not a normal loss.",
"States the normal practitioner-reported click-ID match-rate range as roughly 75-85%.",
"Sends the low match rate to the residual/investigation bucket with named candidate mechanisms such as cookies blocked, the ID stripped by a redirect, or the CRM not saving the field on every submission.",
"Classifies deals closing after the platform's import-acceptance window, or general lead-to-close lag, as timing with a platform-low direction, rather than as evidence LinkedIn is not working.",
"Refuses to switch attribution models mid-analysis and treats the model question as out of scope, redirecting it rather than picking a model.",
"Reports absolute units alongside every percentage, refusing the percent-only answer the user asked for, given the 23-deal volume.",
"Recommends longer comparison windows because percentage gaps swing wildly on small denominators.",
"Names offline conversion upload lag or processing latency as a timing cause of the platform undercount.",
"Notes that last-touch under-reports platform contribution on long sales cycles, and records the model difference as a definitional line rather than proof of failure.",
"Recommends attributing at account level rather than contact level, so the form-filler does not absorb credit owed to a multi-person buying group.",
"Assigns the click-ID capture fix an owner (marketing ops or RevOps) and hands the tracking fix off rather than treating it as part of the reconciliation itself."
]
},
{
"id": 4,
"prompt": "At Vanterra Skincare we check ad numbers every morning. Yesterday (Tuesday) our ad platform showed 41 purchases but the store backend had 67 paid orders - the platform is missing a third of our sales. My colleague says it's because the platform includes view-through conversions and modeled conversions, which inflate its numbers, so that explains it. The store reports in UTC-8 and the platform account is set to UTC. We also launched a new campaign Monday with a 7-day click window. What's going on and how do I fix the tracking?",
"expected_output": "An analysis that strikes the colleague's wrong-direction explanation, attributes the gap to single-day grain, timezone mismatch, and the still-open window, and declines to prescribe a tracking fix.",
"files": [],
"expectations": [
"Rejects the colleague's view-through/modeled explanation because those causes push the platform's count higher, which cannot explain a platform-low gap (direction check applied to strike the candidate cause).",
"Identifies the single-day comparison itself as manufacturing the worst-case discrepancy and recommends a 7-day-or-longer window or weekly grain.",
"Identifies the UTC vs UTC-8 timezone mismatch as shifting conversions across calendar days without any real discrepancy.",
"Identifies the still-open 7-day click window from Monday's launch as timing: the platform's number keeps growing after the pull.",
"Names ad-interaction-date stamping vs order-event-date stamping as a reason a single day cannot line up between the two systems.",
"Recommends letting recent conversions age or re-running after the window closes, rather than acting on the immature pull.",
"Declines to prescribe a tracking fix, stating that no defect is established from this comparison.",
"Anchors the order count on the store backend's 67 and treats the platform as explaining origin, not volume.",
"Explicitly classifies the candidate causes as timing or definitional rather than presenting an undifferentiated list of possibilities.",
"States that a defect requires a direction flip, a sudden jump, or a gap resisting known mechanisms, and that this gap is attributable so it does not qualify.",
"Predicts that on a short ecommerce cycle the timing share of the gap resolves within days and recommends re-running the comparison to confirm it.",
"Establishes or asks for each system's attribution window, counting rule, and conversion definition before putting a number on the gap."
]
},
{
"id": 5,
"prompt": "We finished digging into tracking at Loamworks, a B2C garden-subscription brand doing about $310k/month. Findings: (a) a duplicated purchase tag in our tag container inflating platform-reported purchases about 18%, call it $29k/month of over-reported revenue; (b) about 220 internal test orders per month polluting the order system, roughly $6k; (c) cross-device tracking losses our analytics vendor estimates at $55k/month of unattributed revenue, stable for the last four months; (d) UTM parameters stripped by our link shortener on email-to-site hops, about $9k/month misattributed to direct. Engineering is fully booked this quarter. Biggest number first means cross-device is our top priority, right? What order do we fix these in?",
"expected_output": "A fix ranking by revenue at stake per unit of fix effort that puts the duplicate tag first, keeps stable cross-device losses deferred and named, and shows the effort adjustment explicitly.",
"files": [],
"expectations": [
"Rejects 'biggest number first' and ranks defects by revenue at stake per unit of fix effort.",
"Places the duplicate purchase tag at or near the top: hour-scale, one owner, against a large over-count.",
"Ranks the test-order cleanup high despite its $6k being the smallest figure, because it is near-zero effort and owned outright by the analyst.",
"Does not place cross-device losses first despite $55k being the largest number.",
"States that cross-device identity work is weeks-scale or standing engineering effort and partly structural at any effort level.",
"Notes the cross-device gap has been stable for four months, and that a stable structural loss can wait while a growing one is what would promote it.",
"Given engineering is booked, names cross-device explicitly as deferred or struck from the ranked fix list, carried as a quantified known delta, rather than silently parked at the bottom of the ranking.",
"Identifies the stripped-UTM fix as spending a second team's hour (whoever owns the shortener or redirect chain), distinct from fixes the analyst owns alone.",
"Shows the revenue figure and the fix-effort adjustment for each defect so the reader can see why the biggest number is not first, rather than presenting a bare ordered list.",
"Instructs annotating the report history at each fix date, because the post-fix step-change is a discontinuity that would otherwise look like a defect next period.",
"Assigns an owner to each defect in the list.",
"Hands the duplicate-tag and dedup work off to a dedicated conversion-tracking process rather than detailing tag surgery inside the reconciliation."
]
},
{
"id": 6,
"prompt": "Endgame question. At Corvid Analytics (B2B, about $70k/month total ad spend) we've reconciled everything and two problems survive. First, Google and LinkedIn each claim credit for basically the same demo bookings - together they claim 118 of our 74 CRM-recorded demos each month. Second, about 9% of our monthly gap survives every explanation we throw at it, and it's been steady at that level. Our CFO will not approve turning ads off anywhere - no dark regions, no test cells, spend keeps running. Leadership wants certainty on which platform actually drives demos so we can move budget. What's the most rigorous next step - should we buy a media mix modeling platform?",
"expected_output": "A next-measurement recommendation that names the holdout as the only causal settlement, deletes it because spend cannot be withheld, challenges MMM fit, ranks the remaining options, and accepts the stable 9% residual.",
"files": [],
"expectations": [
"Identifies a holdout or geo test as the only causal answer that settles a two-platform ownership fight outright.",
"Given the CFO's refusal to withhold spend, deletes the holdout from the menu explicitly and states the causal option is off the menu, rather than parking it under 'later' or recommending it anyway.",
"Challenges the media-mix-modeling purchase: MMM fits a portfolio spanning channels no conversion record covers and requires a permanent owner for a standing pipeline and refresh cadence, which a two-platform account is unlikely to justify.",
"Recommends self-reported attribution ('how did you hear about us') as the default rung, running alongside the existing reconciliation.",
"States self-reported attribution's honest limits (coarse, self-report-biased) alongside its advantage of surviving consent loss and blocking entirely.",
"Presents server-side collection with shared event IDs as the rung that closes double-counting at the source, at the cost of about a week of engineering across two teams.",
"Ranks the remaining options on more than one axis (such as value, effort, or efficiency) instead of a single blended list.",
"Does not sum the two platforms' claims: treats 118 claimed vs 74 CRM demos as overlapping claims on 74 demos.",
"Describes the mature end state as triangulation - platform attribution for bid optimization, experiments for causal ground truth, mix modeling for portfolio allocation - with no single method trusted alone.",
"States that platform reporting is structurally self-flattering, so the corrective signal must come from outside the platforms.",
"Names the obligation the recommended rung incurs (for example a privacy-notice line for a new form field, or consent and data-residency review for server-side collection).",
"Treats the steady 9% residual as documented and acceptable under the judgment test (stable, direction-consistent), not as a defect to chase to zero.",
"Assigns the chosen next step an owner and stops there, rather than designing the study or implementation inline."
]
},
{
"id": 7,
"prompt": "Marketing analyst at Pinwheel Labs, a PLG dev-tools company with about 40k monthly sessions. Total signups in analytics vs our billing system have tracked within a steady ~12% gap for over a year. But in the last two months the 'direct' channel share jumped from 31% to 44% of signups while paid-social and organic-social shares dropped - totals are still fine, just the mix moved. Separately, my manager wants to institutionalize an 'attribution correction factor': since analytics undercounts billing by 12%, we'll multiply analytics by 1.12 in every dashboard going forward and stop doing these tedious comparisons. Two questions: is our 12% gap normal, and can we ship the correction factor?",
"expected_output": "A verdict that the stable 12% total gap is normal, the sudden direct-share jump is a defect signal with named misattribution mechanisms, and the permanent 1.12 multiplier is rejected in favor of per-period re-derivation.",
"files": [],
"expectations": [
"Distinguishes the channel-mix shift (total intact) from a total-level gap and names misattribution-to-direct mechanisms: tracking parameters stripped by redirects, link shorteners, or in-app browsers, and/or AI-assistant referrals arriving with no referrer.",
"If citing the figure that roughly 70% of AI-assistant-driven traffic arrives with no referrer, labels it directional rather than audited.",
"Treats the sudden two-month direct-share jump as a defect signal under the judgment test (a sudden jump), warranting investigation, in contrast to the stable total gap.",
"Judges the steady 12% total gap normal using the stability, direction-consistency, and decomposability test rather than a bare percentage threshold.",
"When citing tolerance bands, labels their source status: only the analytics vendor's own documented figures (up to 10% pageview and 20% user/session discrepancy) are official, while other bands come from vendors selling tracking audits and are indicative only.",
"Rejects shipping the permanent 1.12 correction factor.",
"Explains the rejection: consent rates and media mix shift continuously, so the gap must be re-derived each period rather than frozen.",
"Points out that the last two months already demonstrate the factor's failure mode: the mix shifted, and a frozen multiplier would have masked exactly this change.",
"Recommends carrying known deltas forward as documented expectations re-derived each period, instead of stopping the comparisons.",
"Notes that because the total-level comparison is intact, conversion counting is sound and the problem is channel assignment, not the count itself."
]
},
{
"id": 8,
"prompt": "I'm the first data hire at Squall & Co, a B2C meal-kit brand. Board meeting in two weeks. Our CMO wants the deck to use Google Ads' reported ROAS of 4.1 because 'Google has the most complete data,' and wants us to standardize all reporting on Google Ads numbers as our source of truth going forward. I ran a gap analysis myself: the gross gap between Google and our order system is 1,410 conversions for the quarter. I could pin 940 of them on specific causes - window differences, view-through, refunds - but 470 I can't explain yet. I'm inclined to present it as fully reconciled to keep the deck clean. Advice?",
"expected_output": "A pushback that anchors board numbers on the order system, labels platform ROAS non-incremental, computes the 67% explained share against the 80% threshold, and prescribes iteration plus an honest residual statement over a clean fabrication.",
"files": [],
"expectations": [
"Rejects standardizing on Google Ads as the source of truth: platforms report claims on conversions, and the anchor must be the system that records the money (the order system).",
"States that board- or executive-facing numbers anchor on the finance-grade source of truth.",
"Requires that any platform ROAS shown in the deck be labeled non-incremental, with platform numbers reserved for in-platform bid optimization.",
"Computes the explained share as roughly 67% (940 of 1,410) and states it falls below the roughly 80% pass threshold.",
"Refuses to present the reconciliation as fully explained, stating that claiming a clean tie-out fabricates a number.",
"Prescribes iterating on the 470 unexplained conversions by walking the timing and definitional cause lists with the direction check (each candidate cause must push the gap the observed way).",
"Recommends re-running the comparison after attribution windows close to confirm suspected timing items actually resolved.",
"Notes that a residual of this size makes a real tracking defect the likely case (most audited accounts carry at least one), so known defect mechanisms should be checked before accepting the remainder.",
"States that if the share is still below the threshold at the deadline, the deck should carry the honest figure with named exclusions of what was ruled out, which beats a fabricated 100%.",
"Justifies the 80% threshold by reference to the officially published expected-discrepancy band, rather than presenting it as arbitrary.",
"Prescribes the reconciliation report shape: per-pair verdicts, a normalization basis, a variance table with bucket, direction check, and owner per cause line, a residual statement, and known deltas to carry forward.",
"Sequences the two weeks with hour- and day-scale checks only, deferring anything that needs a full test period past the board date."
]
}
],
"trigger_queries": [
{ "query": "Facebook says we got 1,200 purchases last month but Shopify only shows 890 - which one is right?", "should_trigger": true },
{ "query": "Why does Google Ads report 3x more conversions than our CRM?", "should_trigger": true },
{ "query": "our ga4 and meta numbers never match, is that normal", "should_trigger": true },
{ "query": "HubSpot shows 40 demos from paid but the ad platforms together claim 95, reconcile this for me", "should_trigger": true },
{ "query": "I need to explain to my CFO why the ad dashboard revenue doesn't equal our Stripe revenue", "should_trigger": true },
{ "query": "attribution discrepancy between google ads and our order system - how do I break it down?", "should_trigger": true },
{ "query": "cross-platform conversion reconciliation for last quarter", "should_trigger": true },
{ "query": "Are double-counted conversions why Meta plus Google claims add up to more sales than we actually had?", "should_trigger": true },
{ "query": "Is a 25% gap between analytics and backend orders something to worry about?", "should_trigger": true },
{ "query": "My boss wants one source of truth for conversions - the ad platform, GA, or Salesforce?", "should_trigger": true },
{ "query": "TikTok claims 500 purchases, our store shows 210 from TikTok. what gives", "should_trigger": true },
{ "query": "how much of the difference between platform-reported revenue and billing revenue is normal vs broken", "should_trigger": true },
{ "query": "Every tool gives me a different ROAS. Which number do I put in the board deck?", "should_trigger": true },
{ "query": "each of our ad channels takes credit for the same signups - untangle the overlap for me", "should_trigger": true },
{ "query": "our agency's reported conversions are way above what lands in the CRM, need to audit the difference", "should_trigger": true },
{ "query": "the numbers in the weekly marketing report don't add up across tools and finance is asking questions", "should_trigger": true },
{ "query": "why did analytics suddenly start disagreeing with our sales data this month", "should_trigger": true },
{ "query": "quantify how much of our platform-vs-CRM gap is timing vs definitions", "should_trigger": true },
{ "query": "view-through conversions are inflating Meta's numbers vs GA - how do I account for that in reporting?", "should_trigger": true },
{ "query": "we spent $80k, platforms claim $500k revenue, but bank deposits say $310k - help me explain the delta to leadership", "should_trigger": true },
{ "query": "LinkedIn ads says 60 leads, our marketing automation says 38, the CRM says 41. which do I trust and why do they differ?", "should_trigger": true },
{ "query": "email platform, analytics, and our marketplace dashboard all report different order counts - reconcile them", "should_trigger": true },
{ "query": "conversion numbers between our pixel and server events don't line up - how much mismatch is acceptable?", "should_trigger": true },
{ "query": "audit why paid channel revenue in our BI warehouse never ties to what the ad platforms say", "should_trigger": true },
{ "query": "my ecommerce client thinks their tracking is broken because the platform and the store disagree by 30%", "should_trigger": true },
{ "query": "explain the difference between what Google attributes to itself and what our last-click analytics report gives it", "should_trigger": true },
{ "query": "Our Q3 numbers: ads manager 2,340 purchases, backend 1,671. Write up what's going on for the exec team.", "should_trigger": true },
{ "query": "does anyone actually get their ad platform numbers to match their CRM? mine never do", "should_trigger": true },
{ "query": "how do I reconcile offline conversion uploads with what the CRM eventually records?", "should_trigger": true },
{ "query": "the marketing team and the finance team report different customer acquisition numbers and I'm stuck in the middle", "should_trigger": true },
{ "query": "the platform says our campaign drove 900 signups but the product database logged 640 - before I kill the campaign, sanity check?", "should_trigger": true },
{ "query": "need a framework for explaining ad reporting discrepancies to non-technical stakeholders", "should_trigger": true },
{ "query": "why is revenue in the ads dashboard 40% higher than actual invoiced revenue", "should_trigger": true },
{ "query": "GA shows fewer conversions than both the ad platform and the order system - where do the missing ones go?", "should_trigger": true },
{ "query": "B2B question: our ad platform never sees the deals that close months later. how should I compare its numbers to closed-won?", "should_trigger": true },
{ "query": "is it normal that after refunds our real revenue is way below what the ad platforms report?", "should_trigger": true },
{ "query": "walk me through separating real tracking problems from expected differences between reporting tools", "should_trigger": true },
{ "query": "meta and google both take credit for the same purchases in their dashboards - how big is the overlap really?", "should_trigger": true },
{ "query": "our conversion counts jumped in the platform but not in the database - did something break or is this normal?", "should_trigger": true },
{ "query": "monthly close: marketing-reported sales vs accounting-recorded sales differ again, need to document why", "should_trigger": true },
{ "query": "how do I set up a recurring reconciliation between ad platforms, analytics, and our order system?", "should_trigger": true },
{ "query": "client asks why their dashboard shows way more leads from paid campaigns than ever reach their inbox", "should_trigger": true },
{ "query": "the gap between platform conversions and CRM conversions doubled this month, what do I check first?", "should_trigger": true },
{ "query": "modeled conversions vs actual orders - how do I compare these honestly in one report?", "should_trigger": true },
{ "query": "I think our ad platform is double counting purchases, how do I prove it?", "should_trigger": true },
{ "query": "Our CPA doubled in the last three weeks and I don't know why - diagnose our ad account", "should_trigger": false },
{ "query": "Set up conversion tracking for our new Meta campaign before launch and verify the pixel fires once", "should_trigger": false },
{ "query": "My purchase event fires twice on the thank-you page - fix the deduplication between pixel and CAPI", "should_trigger": false },
{ "query": "Which attribution model should we use - first click, last click, or data-driven?", "should_trigger": false },
{ "query": "Is our CAC too high for a $49/month SaaS?", "should_trigger": false },
{ "query": "How should I split a $60k monthly ad budget across Google, Meta, and TikTok?", "should_trigger": false },
{ "query": "Design an A/B test to figure out which ad creative wins", "should_trigger": false },
{ "query": "Our ads get plenty of clicks but the landing page doesn't convert - audit it", "should_trigger": false },
{ "query": "When can I scale my winning campaign from $200/day to $1,000/day?", "should_trigger": false },
{ "query": "Build a retargeting sequence for cart abandoners", "should_trigger": false },
{ "query": "Are we overspending against this month's budget? 60% through the month at 75% of spend", "should_trigger": false },
{ "query": "Set a maximum allowable CAC and a ROAS floor for the company", "should_trigger": false },
{ "query": "Is my top video ad fatiguing or is it just seasonality?", "should_trigger": false },
{ "query": "Write 10 headline variants for our spring sale ads", "should_trigger": false },
{ "query": "Which negative keywords should I add from this search terms report?", "should_trigger": false },
{ "query": "Help me pick between Google Ads and LinkedIn for our B2B launch", "should_trigger": false },
{ "query": "Too many ad sets stuck in learning limited - should we consolidate campaigns?", "should_trigger": false },
{ "query": "Building a lookalike audience - which customer list should I upload as the seed?", "should_trigger": false },
{ "query": "Map the buying committee for our $80k ACV product and how to target each role", "should_trigger": false },
{ "query": "Score the hooks in these three video ad scripts", "should_trigger": false },
{ "query": "What ad formats work best for brand awareness on short-form video?", "should_trigger": false },
{ "query": "Draft a creative brief for a UGC campaign", "should_trigger": false },
{ "query": "I want to promote our CEO's LinkedIn post as a paid ad", "should_trigger": false },
{ "query": "Plan our audience targeting layers for a cold prospecting campaign", "should_trigger": false },
{ "query": "Should I switch from target CPA to maximize conversion value bidding?", "should_trigger": false },
{ "query": "Collect our competitors' running ads into a swipe file", "should_trigger": false },
{ "query": "Write a UGC script with 5 hook variants for our skincare brand", "should_trigger": false },
{ "query": "How do I become a senior media buyer? review my portfolio", "should_trigger": false },
{ "query": "Write a job description for a performance marketing manager", "should_trigger": false },
{ "query": "What PPC newsletters and podcasts should I follow to stay current?", "should_trigger": false },
{ "query": "Implement server-side tagging with a tag manager on our site", "should_trigger": false },
{ "query": "Set up GA4 ecommerce purchase events on our checkout", "should_trigger": false },
{ "query": "Build a marketing mix model in Python for our channel spend", "should_trigger": false },
{ "query": "Design a geo holdout test to measure Meta incrementality", "should_trigger": false },
{ "query": "Explain how multi-touch attribution and data-driven attribution work", "should_trigger": false },
{ "query": "Our GA4 sessions dropped 40% after the cookie banner change - fix consent mode", "should_trigger": false },
{ "query": "Reconcile our bank statement against the general ledger for month-end close", "should_trigger": false },
{ "query": "Migrate our conversion tracking from Universal Analytics to GA4", "should_trigger": false },
{ "query": "Why does my Salesforce report show different pipeline than my Salesforce dashboard? both are CRM views", "should_trigger": false },
{ "query": "Set up offline conversion uploads from HubSpot to Google Ads", "should_trigger": false },
{ "query": "Which UTM naming convention should we standardize on?", "should_trigger": false },
{ "query": "Audit our data warehouse dbt models for the marketing schema", "should_trigger": false },
{ "query": "My Meta ads were rejected for policy violations, help me get them approved", "should_trigger": false },
{ "query": "Forecast next quarter's revenue from the current pipeline", "should_trigger": false },
{ "query": "Calculate the incremental lift from our latest brand campaign", "should_trigger": false }
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |