---
name: create-facebook-instagram-campaigns-with-location-targeting
description: "Set up a small local ad test with the right post, place, cost and end date."
category: Dollar a Day Campaigns
stage: Promote
definitive_article: /dad
status: needs-work
---

# Create Facebook/Instagram campaigns with location targeting

You want more people in the area you serve to see a useful post. This guide helps you set up a small local ad test. Start with your service area and one post that has worked.

**The path:** Service area → proven post → saved test → delivery check.

**Use this when:** The business has a proven post, a defined local goal and authorized scope for a Meta campaign.

## Inputs
- Exact business portfolio, ad account, Page and Instagram identity with the roles needed for the planned action.
- Actual service area, current offer, verified content rights and original post ID.
- Goal and success target, account currency/time zone, billing owner, spend ceiling and dates; required tracking evidence for that goal.

## First-run prompt

> Prepare this Facebook/Instagram test using the existing approved post and service area. Check the identity, goal, current audience controls, budget type and end date. Launch only within the supplied authority, then re-read the saved settings and delivery. Report any unsupported minimum or location requirement without broadening it.

## Steps
1. Read the agreed [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) and prerequisite record. Confirm the offer is real, customer proof is usable and the post already earned relevant signal. Paid distribution is not the repair for an unproven offer.
2. Open the exact authorized account and confirm which Page/Instagram identity will appear. Reuse existing valid assets; do not create a duplicate account or transfer ownership to solve a role gap.
3. Choose the objective that measures the stated job. An on-platform engagement test needs its own platform metric; a website-lead test also needs a checked destination and the required conversion path. Do not install every tracker for every goal.
4. Enter the supported location controls for the real service area and check any special-category restrictions. Do not default to guessed ages, home ownership or every available interest. Read expansion/suggestion labels before claiming a tight local audience.
5. Use the original eligible post, then inspect each chosen placement with sound off. Check captions, crops, identity, claims, destination and mobile usability. Save a distinct creative only if the authorized plan calls for it and note the new ID.
6. Set the method’s small seven-day test where accepted. Record ad-set versus campaign budget control, account minimums, budget pacing and actual total limits. Calculate all concurrent commitments; $1/day is not a promise that every day bills exactly $1.
7. Re-read the final summary before an authorized launch, including currency, dates and budget. After saving, record actual IDs and status. A draft or approved ad without impressions is not verified delivery.
8. Check spend, delivery, link and location-quality evidence early. Protect the existing ceiling and correct harmful errors within scope. At day seven, score against the original target and route the next action rather than extending the end date by default.

## Definition of done (QA checklist)

- [ ] Correct owner/account/Page/Instagram and original post IDs are recorded.
- [ ] Service-area settings and any expansion or policy limits are explicit.
- [ ] The goal’s actual tracking works or the exact affected step is pending.
- [ ] Budget level, pacing, combined ceiling and end date pass read-back.
- [ ] Saved, reviewed, delivering and successful are separate reported states.

## Example(s)

**Fictional teaching example:** A shop serves Cedar Town and wants local people to watch a repair tip. Its real service boundary is recorded before settings are chosen. The preview shows the same post on both chosen placements with legible captions. A seven-day test is staged at $1/day where supported, with the account’s spend controls documented. If the location option includes people only recently in the area, that limit stays in the log. The report checks actual inquiries for service fit rather than promising every viewer lives nearby.

## Handoff and Content Factory context

Give the campaign owner the saved settings and due dates for [analyze cost per result and engagement](https://local-service-spotlight.github.io/task-library/?task=analyze-cost-per-result-and-engagement#task-analyze-cost-per-result-and-engagement). Route a tracking defect to [set up digital plumbing pixels tracking](https://local-service-spotlight.github.io/task-library/?task=set-up-digital-plumbing-pixels-tracking#task-set-up-digital-plumbing-pixels-tracking); a content defect returns to the content owner before a new test.

This task is in Promote within the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. Use the proof and checked posts from earlier stages; a Promote task does not automatically redo all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

One campaign setup and one dated test. Routine delivery checks follow the existing campaign arrangement. Further boosts, recurring reports or larger budgets need the scope and a working trigger already in place.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Promote
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 5, gating 4 (runs every factory cycle or weekly; ads/revenue path; gates a phase)
- **Suggested previous station:** `set-1-day-budget-per-ad-set`
- **Suggested next station:** `create-new-saved-audiences-from-audience-insights`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Organic metrics CSV (or Ads Manager export), pixel ID, creative filenames, kill/scale log. Next week's ranking starts from this file.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Maintained method: https://blitzmetrics.com/dollar-a-day/
- Source mapping needs reconciliation: the preserved `definitive_article: /dad` points to the coaching program. The method page above is `/dollar-a-day/`; this record does not certify the coaching page as a task recipe.
- Exact task: [Create Facebook/Instagram campaigns with location targeting](https://local-service-spotlight.github.io/task-library/?task=create-facebook-instagram-campaigns-with-location-targeting#task-create-facebook-instagram-campaigns-with-location-targeting)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Dollar-a-Day method](https://blitzmetrics.com/dollar-a-day/)
- [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/)
- [Digital Plumbing training](https://blitzmetrics.com/digital-plumbing/)
- [Meta budget help](https://www.facebook.com/business/help/190490051321426)
- [Meta Advantage+ audience help](https://www.facebook.com/business/ads/meta-advantage-plus/audience)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- The current Meta help bodies were access-blocked; no account UI was inspected during authoring.
- The live account must supply its supported minimums, controls and policy category.