Esta página aún no está en su idioma. Está leyendo el texto en inglés.
Blog
A Meta ad account in its first two weeks: the ceilings that get noticed
El equipo de ARMANOS7 min
What counts as one action here
The platform counts its own things: a campaign created, a budget raised, a card added, a login from an unfamiliar device.
The browser on your machine sees something else: a page opened in the profile. The two tallies do not add up, and reconciling them is left to you.
- 1
A page opened
A top level navigation goes into the day's count, a frame inside the page does not.
- 2
A move inside the console
A screen opened without reloading the page never enters that count.
- 3
A new day
A new calendar day starts the count over, and every profile has its own.
Daily numbers for a fresh account
An ad profile gets five numbers a day, and they sit on its card under Safe daily ceiling, next to the Safe pace bar that counts pages opened.
The platform publishes none of its own, so these are taken with room to spare. The warm up trims them on day one and hands them over in full on day seven.
| Action in the console | On day one | From day seven |
|---|---|---|
| Campaign edits | 2 | 12 |
| Budget changes | 1 | 4 |
| New campaigns | 1 | 3 |
| Account switches | 1 | 3 |
| Payment edits | 1 | 1 |
The first week climbs in steps
There are exactly seven steps, and each one is a share of that day's full number: a fifth on day one and all of it on day seven.
Pages and campaign edits grow together, because the share behind both steps is the same one.
| Day | Pages in the profile | Campaign edits |
|---|---|---|
| Day 1 | 8 | 2 |
| Day 2 | 14 | 4 |
| Day 3 | 20 | 6 |
| Day 4 | 26 | 8 |
| Day 5 | 32 | 10 |
| Day 6 | 36 | 11 |
| Day 7 and after | 40 | 12 |
The second week adds no new steps
Day eight carries the same numbers as day seven, and so does day fourteen. What grows in that week is your spending history, not the number.
So the second week goes into finished campaigns and the first quality data on the account, not into the warm up.
- 1
Days one to three
One console, one campaign, and leave the budget alone.
- 2
Days four to seven
A second campaign and one budget change a day.
- 3
Days eight to fourteen
Full numbers, but add a new console one a day.
Payment details move once a day
This is the only action whose number never grows: one edit on day one and one on day fourteen.
Changing who pays brings a manual review faster than anything else, and one card across two consoles ties them together on the platform side.
Account switches are counted apart
Three switches a day is the full number, and on day one you have one of them.
Two consoles in one window leave the platform a shared login, a shared device and a shared exit address. A profile per console removes the first two, and the exit address stays shared until you give the profiles different proxies.
What the console sends outside
An ad profile takes two rule lists: a general one and an ad one. The second is laid out across four ad platforms and third party collectors.
An event log request such as /ajax/bz on Meta hosts does not get through in such a profile, while the login and the console itself open as usual.
| Rules in the ad list | How many |
|---|---|
| 8 | |
| Meta | 4 |
| TikTok | 2 |
| Microsoft | 4 |
| Third party collectors | 7 |
Four platforms in one scenario
The Ad accounts scenario names four platforms: Google Ads, Meta Ads, TikTok Ads and Microsoft Ads. Their numbers are shared because they count the same things: campaign edits, budget changes, new campaigns, payment edits and account switches.
Shared numbers do not mean a shared account. The profile is still one per console, and the scenario only suggests a pace.
How the per-action numbers grow by day
Every per-action number follows the same curve as the daily one: a fifth on day one and the full figure on day seven. Campaign edits run two, four, six, eight, ten, eleven and twelve.
Budget changes and new campaigns start at one, and that is not rounding down to zero: a number that ought to be at least one stays one.
Payment edits stand apart: one a day from the first day to the last. There is nothing to ramp, because the full number is one as well.
| Action in the console | Day one | Day seven |
|---|---|---|
| Campaign edits | 2 | 12 |
| Budget changes | 1 | 4 |
| New campaigns | 1 | 3 |
| Payment edits | 1 | 1 |
| Account switches | 1 | 3 |
What gets cut for an ads profile
An ads profile carries two counter lists: a general one of thirty-one entries and an ads one of twenty-five. Fifty-six together.
Inside the ads list there are eight Google entries, four each for Meta and Microsoft, two for TikTok and seven third-party ones. Those are the addresses by which the console and its neighbours recognise you on other sites.
A rule written on a path fires on other sites too
Some entries of the ads list are not a domain but a piece of a path. Such a rule looks at the whole address and does not ask about the host.
Checked on three addresses: a request for the Meta counter file is cut both on the platform itself and on an unrelated shop, while an ordinary file of that same shop goes through. For your console that means the counter does not follow the profile onto somebody else's storefront.
Domain rules behave differently: they are locked to the platform's hosts and stay quiet elsewhere.
Two profiles for one console are not needed
A console and its account live in one profile, and splitting them across two gains nothing: the platform sees the same machine from both sides.
Two different consoles in one window, though, hand the platform a shared login and a shared device. A profile per console removes the first and the second, while the exit address stays shared until you give the profiles different proxies.
What the app does not know about a console
Meta publishes no thresholds, and nobody outside knows them. The numbers in this entry are ours: they come from the app's scenario rather than from the platform.
The app counts only moves between pages inside a profile window. A campaign edit, a budget change or an account switch is invisible to it and cannot be counted: these are guides for you, not counters.
Test your own pixel from elsewhere
The ad list cuts the platform pixel too: its request to connect.facebook.net does not get through in this profile.
So watch the event from your landing page in a profile on another scenario, or you will be repairing a pixel that works.
What these numbers do not promise
- Not one number here was published by a platform. These are cautious values per kind of work, and we chose them.
- The warm up counts from the day the profile was created. A profile made today for a console from 2024 still starts on day one of seven.
- Only the count of pages opened is marked by colour. The per action numbers sit beside it as guidance, with the «warning at N» threshold on a second line and no colour, and adding up your own edits is left to you.
- A separate profile removes one cause out of several. Your ads, your landing page and your spending history weigh more than a browser.
Where you can see this yourself
Every number above comes out of code you can open and run.
- The five daily numbers of the Ad accounts scenario and the seven steps of the week sit as data in one file
- packages/shared/src/index.js
- The day's number is computed by one call for every scenario and every warm up day and stays a number, not a permission
- packages/shared/src/index.js · apps/web/test/потолок-это-ориентир.js
- The day counter is driven ten times past the highest number: it keeps counting and refuses nothing
- apps/desktop/src/lib/pace.js · apps/web/test/потолок-это-ориентир.js
- The day count belongs to the profile and leaves with it
- apps/desktop/src/lib/pace.js · apps/desktop/test/delete-leaves-nothing.js
- A top level navigation is counted, while frames inside the page and our own start page are not
- apps/desktop/src/main/browser-preload.js
- First-party tracking rules are locked to the platform's hosts, and a scenario without its own set takes nobody else's
- apps/desktop/src/lib/tracker-rules.js · apps/desktop/test/rules-and-runs.js
- The ad rule list, laid out platform by platform
- apps/desktop/assets/trackers_ads.json
Questions
- How many campaigns can I create on day one?
- One. Two from day three, three from day six, and three is the full number: the warm up goes no higher.
- What happens if I go past these numbers?
- Nothing happens: the per-action numbers are shown, not counted. The bar on the profile card changes colour on a DIFFERENT count, the moves between pages, and has nothing to do with the number of campaigns.
- The account is two years old and the profile is a day old. Which day is it?
- The first. The platform knows the age of the account, while the browser on your machine counts the age of the profile and invents nothing beyond it.
- Do I need a separate profile for every console?
- Yes, unless the consoles are meant to read as one person. An account switch in one window leaves a shared login and a shared device.
- Why does the pixel not fire on my landing page?
- Inside an ad profile its request does not get through, along with the rest of the tracking. Watch the event from a profile on another scenario.
- Will this get my account through a review?
- No. A review looks at the ads, the landing page and the spending history, and a browser has nothing to do with any of them.
Next to this
Make a profile for the console
The numbers for the day sit on the profile card from the first minute, and typing them in by hand is not needed.