Prompt library

Build your system. Here are the prompts.

Twelve prompts for the work a PME hands to agents. Fill in the highlighted parts, paste them into the assistant or agent you use, and judge the answer against the checklist under each one.

Evidence firstEvery prompt asks for the numbers and their source before any recommendation.
The decision stays humanPrompts ask for proposals. Changes above your limits wait for a yes.
Open to contributionsHave a prompt that works? Send it in. Accepted prompts carry your name.
SignalWeekly, before any budget decision

Reconcile purchases

Compare purchases recorded in the CRM with purchases each ad platform reports for {date range}. Show a table: platform, platform count, CRM count, gap in %. For each gap above 10%, list the most likely causes in order of likelihood and the check that would confirm each one. Do not change any settings.
A good answer includes
    SignalAfter a site release or a tag change

    Audit the event setup

    Review our conversion events for {platform}. For each event list: name, where it fires (browser, server or both), whether it carries an event_id for deduplication, value and currency, and consent handling. Flag anything that could double-count or drop conversions, and say how you would test it.
    A good answer includes
      SignalMonthly

      Check match quality

      Report the match rate or event match quality for our server-side conversions on {platform} for the last 4 weeks, by week. Explain which customer fields we send, which are missing, and what each missing field would likely add. Only suggest fields we are allowed to send under our consent setup.
      A good answer includes
        DecisionsBefore any budget increase

        Marginal CPA before scaling

        For each campaign in {account}, estimate the cost per purchase of the last 20% of spend over {date range}, not the average. Compare it with our target CPA of {target}. Recommend where spend could move, but do not move anything: I approve every change above {limit}.
        A good answer includes
          DecisionsEvery Monday

          The morning ledger

          Build last week’s ledger: total marketing spend, revenue, MER, new customers and contribution margin, with the source of every number named. Then list what each platform claimed in conversions and how far that is from the CRM. Keep the platform claims in a separate column from the business numbers.
          A good answer includes
            DecisionsBefore trusting a channel’s ROAS

            Design a holdout

            Propose a geo holdout to measure the incremental effect of {channel}. Give: the regions in each group and why they are comparable, the test length, the minimum effect we could detect at our current volume, the budget at risk, and the decision we will make for each possible result. Flag anything that would make the result unreliable.
            A good answer includes
              DecisionsWhen CPA or ROAS moves sharply

              Explain a jump

              CPA on {campaign} changed by {change} on {date}. List every change made in the 7 days before, by us, by the platform or by the site: budgets, bids, creatives, audiences, tracking and landing pages. Rank the likely causes and say which data would separate them. Do not revert anything yet.
              A good answer includes
                CreativeAt the end of each creative test

                Group results by hook

                Group last month’s ads by hook rather than by ad. For each hook give spend, impressions, CTR, conversions and CPA, and whether it reached at least {n} conversions. Do not call a winner for any hook below that threshold; mark it as inconclusive instead.
                A good answer includes
                  CreativeBefore briefing new variants

                  Size the next test

                  Our CPA is about {cpa} and each variant needs about {n} conversions for a verdict. With a test budget of {budget}, how many variants can we test properly, and for how long? If the answer is fewer than we planned, suggest which variants to drop and why.
                  A good answer includes
                    CreativeBefore a new ad goes live

                    Check the promise

                    Read the ad copy and the landing page at {url}. List every promise the ad makes and whether the page repeats it above the fold. Flag any claim the page does not support, and any step between the click and the conversion that the ad did not prepare the user for.
                    A good answer includes
                      The loopBefore the weekly review meeting

                      Draft the weekly review

                      Draft the agenda for this week’s performance review: the three numbers that moved most and why, every change the agents made with its result, every proposal waiting for approval, and one question we cannot answer yet. Keep it to one page.
                      A good answer includes
                        The loopWhen you add a new agent

                        Set the limits

                        Write the operating limits for a {type} agent on {account}: what it may change without asking, the maximum size of each change, what always needs my approval, how every change is logged, and how to roll it back. Use plain sentences I can sign off.
                        A good answer includes
                          Contribute

                          Publish your prompt. Credited by name.

                          The library is written by the people who use it. Send a prompt that has worked for you on a real account. We check it against the three rules above and publish it with your name and link.

                          1. 01You send the prompt and what a good answer includes.
                          2. 02We test it: evidence first, decision stays human, no secrets or client data.
                          3. 03It goes live in the library with your name. Usually within a week.

                          Keep going

                          Learn the job, one free chapter at a time.

                          Four short courses, each ending in a project you can show. Free and open to everyone.