◆ JavaScript

Automate advertising processes

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a JavaScript function called `trackAdImpressions` that takes `adId` and `userId` as…+
Write a JavaScript function called `trackAdImpressions` that takes `adId` and `userId` as arguments, and sends a POST request to `/api/impressions` with a JSON body containing these two IDs. Make sure to handle potential network errors gracefully and log them to the console.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptI need to automate our ad campaign launches. Before I write the full automation script, help me…+
I need to automate our ad campaign launches. Before I write the full automation script, help me structure the logic for creating a new ad campaign. It needs to accept campaign details like `name`, `budget`, `startDate`, and `endDate`, validate these inputs to ensure the budget is positive and dates are in the future, and then return a structured object ready for an API call. Flag any potential issues that might arise when integrating this with an existing ad platform API.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new ad creative isn't showing up for our target audience, and the campaign launch is…+
The new ad creative isn't showing up for our target audience, and the campaign launch is tomorrow.
The new ad creative isn't showing up for our target audience, and the campaign launch is tomorrow. I pushed the code for the new targeting rules last night, but the impression counts are flat for the specific segments. I'm afraid I've introduced a scope issue or a data type mismatch that's silently failing. The marketing lead is already asking for updates, and I can't tell them I'm not sure what's broken. What's the most likely diagnostic step to pinpoint where the targeting logic is failing, and what's the quickest way to get a temporary fix in place if it's a small bug?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time debugging ad tracking discrepancies between our internal logs and the ad…+
I keep losing time debugging ad tracking discrepancies between our internal logs and the ad platform reports.
I keep losing time debugging ad tracking discrepancies between our internal logs and the ad platform reports. It feels like every other week there's a small difference that takes hours to reconcile. I suspect our tracking events aren't always firing reliably or consistently across all browser types and network conditions. What habit should I change in how I implement or test these tracking scripts to build more robust and trustworthy ad impression data from the start?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.