Facebook Ads Account Setup: The Configuration Checklist Before Your First Campaign (2026)

Getting a Facebook ad account approved is one problem. Getting it configured so it doesn't stall, misfire, or get restricted in week two is a different one — and it is the one that gets skipped.

Most people open the account, drop in a card, and launch. The account then behaves strangely: conversions don't attribute, the pixel reports events nobody can match to a purchase, a domain warning appears, or a second user can't access anything because everything was created under a personal profile. All of these are setup problems, and all of them are cheaper to fix before spend starts than after.

This is the configuration pass, in the order the pieces actually depend on each other.

Start from Business Manager, not from the ad account

The single most common structural mistake is creating assets under a personal profile and only later trying to move them into a business.

Assets created personally are hard to transfer, sometimes impossible. Pixels in particular tend to stay attached to whoever created them. If the person who set things up leaves, or the agency relationship ends, you discover the problem at the worst moment.

The correct order is: Business Manager first, then everything else created inside it — ad account, Page, pixel, domain, catalogue. Every asset should be owned by the business, and every human should have access through their own account with an assigned role.

That last point matters more than it sounds. Shared logins are the fastest route to a security review, because one login appearing from several places is exactly the pattern platform systems flag.

Roles: assign the minimum that works

Business Manager separates admin from employee at the business level, and then separates access per asset. Two rules cover most cases:

• Only people who need to add or remove other people should be business admins. In most teams that is one or two people, not everyone senior.
• Everyone else gets asset-level access to the specific ad account, Page, or pixel they work on.

Partner access — for an agency or a freelancer — should go through the partner sharing flow rather than by adding someone as an employee of your business. It is reversible in one click, and it keeps the audit trail intact.

Payment method: get this right before the first launch

Two things worth knowing before you add a card:

Currency and time zone are permanent. Both are fixed at ad account creation and cannot be changed afterwards. Getting either wrong means creating a new ad account and rebuilding — so decide deliberately, especially if reporting has to reconcile with a finance system in a specific currency.

A backup payment method prevents the worst failure mode. When a primary card declines mid-flight, delivery stops. Restarting a campaign that has already stopped is not free — it re-enters the learning phase. A secondary method on file turns an outage into a non-event.

Domain verification and the pixel

These two are often treated as optional polish. They are not — they determine whether your conversion data is usable at all.

Verify the domain in Business Settings, using the DNS TXT record, a meta tag, or the uploaded file. Verification is what gives your business authority over how your links and conversion events are treated, and it is a prerequisite for configuring web events properly.

Install the pixel, then confirm it fires. Installing is not verifying. Load the page, use the browser extension or the events tool, and confirm the event arrives with the parameters you expect — not just that something arrived. A pixel that fires a generic PageView on a purchase page is worse than no pixel, because it looks configured.

Configure your web events in priority order. With aggregated event measurement, you rank the events that matter — typically purchase at the top, then add-to-cart, then lead or registration, then view content. This ranking determines what gets attributed when a user opts out of tracking. Configuring it after you launch means your early data is measured against a ranking you did not choose.

Consider the server-side path early. Browser-only event delivery loses a meaningful share of events to blockers and browser restrictions. Adding a server-side channel alongside the pixel is easier to design in at setup than to retrofit after your reporting baseline is established.

The pre-launch checklist

By the time you are ready to create a campaign, these should all be true:

1. Business Manager exists, and the ad account, Page, pixel and domain are all owned by it.
2. Every person has individual access with an assigned role; no shared logins.
3. Currency and time zone are correct — you cannot change them later.
4. A primary and a backup payment method are both on file.
5. The domain is verified and shows as verified in Business Settings.
6. The pixel fires, and you have watched a real test event arrive with correct parameters.
7. Web events are ranked in priority order, deliberately.
8. Someone other than the account creator can log in and reach everything they need.

Item 8 is the one people skip, and it is the one that costs the most when it turns out to be false.

Frequently asked questions

Can I change my ad account currency or time zone later?

No. Both are set when the ad account is created and are permanent. Changing either requires a new ad account.

Do I need domain verification if I only run traffic campaigns?

You need it as soon as you care about conversion measurement, and it is a prerequisite for configuring web events. Setting it up before you need it costs nothing.

Should each brand have its own ad account or its own Business Manager?

Usually separate ad accounts inside one Business Manager. Separate businesses make sense when the legal entities are genuinely different — otherwise you are creating administrative overhead for yourself.

Why did my campaign stop when nothing changed?

The most common cause is a declined payment method. This is what the backup method in step 4 exists to prevent.

Where the environment fits

One thing the checklist above does not cover: if you are operating across regions, or managing accounts for more than one client, the environment the account is operated from becomes part of the setup — a stable network path, browser state that stays separated per account, and consistent access patterns.

That is a separate layer from the configuration in this article, and it is the layer AdBegin works at: accounts, IP, and browser environment configured together rather than assembled piecemeal. The configuration checklist above still applies either way — no environment setup compensates for an unverified domain or a pixel nobody tested.

The short version

Account setup is not the approval. It is the eight items above, done in dependency order, before the first dollar moves. Currency and time zone are irreversible; ownership and role structure are painful to change later; and unverified conversion data cannot be repaired retroactively.

Twenty minutes here removes the class of problems that otherwise shows up in week two, when spend is running and the fix is expensive.