Every ad, in front of you before it runs.
The creative view shows each ad the way it will run: the image in every placement, the text, the headline, the button, and the audience it will be shown to. Approve it, ask for a change, or leave a note, and our team is told as you press.
What will I see before an ad runs?
Each ad, exactly as it will run. The image appears in every placement it was built for, 4:5 feed, 9:16 Stories and Reels, and 1:1 carousel cards, each labelled with its size and a link to the full-size file. Beside the image sit the four pieces of copy Meta will show: the ad text, the headline, the description and the button. The copy on the screen is the copy rendered into the image, because one build writes both, so what you approve is what runs.
Ads are grouped by campaign. Above each campaign the view names the audiences the ads will be shown to, one by one, who they will not be shown to, where a click lands, and anything we still need from you before it can run. A set opens with a count of how many ads are approved out of how many, a short note on what the set is, and a line on what happens when you approve.
A first set for one business ran to eleven ads across its campaigns, each rendered in a feed size and a story size, every photo the business's own finished work. The screen opened at zero of eleven approved. The owner approved the ads worth running, sent one back with a note asking for a different photo and a new headline, and the count moved as each decision saved. That is the whole job on your side: read, decide, move on.
How do I approve an ad, or send it back?
Press Approve and the ad is marked approved, with the time. Press Request changes and a box opens inside the ad, under the words you are describing, asking what you would like changed; Send to my team files it. Leave a note lets you say something without changing your decision, so you can approve an ad and still say use the other photo next time. Undo clears a decision and returns the ad to Not reviewed yet. Every button saves on its own, there is no submit step at the end, and a decision that fails to save says so and asks you to try again.
Our team is told as you press. Each decision posts a message to your account's channel on our side and an email to [email protected], carrying the ad, your note, and the running count of approved and changes requested. A change request comes back as a reworked ad in the same queue, for a fresh decision. Nothing on this screen edits an ad that is already running; when we improve a live ad, the new version replaces the old one the same way, through the queue.
Approve as many as you like in one sitting, one ad at a time, as fast as you can read them. Each decision is recorded on its own, so a set of eleven leaves eleven records, not one.
What gets written down, and who can see it?
Every decision, against the ad it belongs to. The record carries the status, your note up to 2,000 characters, who decided and when. Who decided is read from the sign-in that Cloudflare Access verified on the way in, never from a name typed into a box, because a browser could claim to be anyone. Each open of the view is logged too, with the time, so the record shows when the set was looked at as well as what was decided.
Before an ad can appear here, a person on our team has opened every rendered image and written down what it shows. That note is checked against the copy: an ad whose words say schools and job sites may not carry a photo of a house, and two ads whose photos show the same subject do not both go up. Re-render an image and it drops out of the queue until someone has looked at it again. An ad that fails any of those checks is held on its own; the rest of the set stays in front of you.
Your dashboard is pinned to your business on the server, so one sign-in cannot read another business's drafts, and a set that is half built never appears at all. Our working notes on a set, what is holding it back and which claims we declined to make, stay on our side; the screen receives a fixed list of fields and nothing else.
When does an approved ad start, and can I stop it?
Approving spends nothing on its own. An approved ad goes to our team to build in your Meta ad account, which you share into our Business Manager during setup week one, and the record of what you approved is what they build from. The full-size file linked under each image is the exact file that goes into Ads Manager. Turning an ad on is a deliberate act by a person, and everything is read back from Meta after the switch; no scheduled job turns an ad on, and budget and bid changes in your ad account are made by a person, never by a schedule.
Some engagements set a run date. When one is set, each ad you have not acted on says so in its card: it runs automatically on that date and time, Eastern, unless you stop it, and no action is needed if it looks good. Approved ads run now. Stop this ad is one click, any time, even after it starts, and the activation step never touches an ad you have stopped. A reworked ad re-enters review with its own short window instead of restarting the whole round. The default window is 72 hours, set by our team per set.
This view shows what is about to run, not how it performed. Spend, reach and results from your Meta ad account are not on the dashboard today; where we also run your Google Ads search, those campaigns report on the Google Ads view with the daily change watch. Ask for a performance readout from the screen and a person answers.
Where do the images come from, and why do they load?
From your own photographs. Every set built to date was made from the business's own finished work or product photography. Our team builds each ad from your photo library and renders it to every placement the campaign needs, and that render, not a mockup, is what you see.
The screen loads a preview sized for review, 760 pixels wide, made from the master and cached beside it, because the masters run about 1.5 MB each and a review page shows a dozen at once. The full size link opens the master. Images travel through your dashboard's own secured path, behind the same sign-in as the rest of it, and are marked private so no shared cache keeps a copy.
A browser does not retry a failed image on its own, and the likeliest cause of a failed one is a service restarting for about 45 seconds. So the view retries each image three times, waiting longer each time, before it shows a caption asking you to refresh in a moment. An ad with a blank where the photo should be is the one thing this page will not show you.
Is this on my account, and what should I check in the demo?
The creative view appears where we build and run paid social creative for you. It is a per-client view rather than part of the shared engine, so a business that does not run social ads with us never sees an empty approval queue. Ad creatives are on Command; the full list of what each tier includes is on the pricing page. A Meta connection on its own does not turn it on: that connection reads your Page numbers, and approvals stay a separate screen.
The demo at demo.trulata.com runs the same engine code every client runs, for a fictional company with illustrative numbers, and it does not carry a creative view, because the view only exists where paid social is running. Check two things there instead. Open the Outbound view and look at the review-first queue: a draft, a decision, a record, which is the shape this view takes for ads. Then open the Social view, the read-only side of Meta on the dashboard; the creative view is the other side, and the two are kept apart on purpose.
Setup puts the access in place before the first set is built. In week one you share your Facebook Page and ad account into our Business Manager, alongside the Google manager invitations; that access lives on Meta's side and you can withdraw it there. There is no login form on the dashboard, no OAuth button, and we never hold your password. The first set is built from your photos, gated image by image, and lands in the queue at zero approved, waiting on you.
What the creative view reads and writes.
| What | Where it comes from | How fresh |
|---|---|---|
| Ad drafts | Built by our team from your photos; the copy is rendered into the image | As built |
| Approve, request changes, note, undo | Written to the ad's record with the time and your sign-in | Live |
| Team notice | Your account's channel on our side and [email protected] | As you press |
| Publishing | Approved ads, built by a person in your Meta ad account | After approval, or at the run date where one is set |
| Images | Your photographs; preview at 760 pixels, master at full size | Per ad |
| Availability | Accounts where we run paid social creative | Per account |
An approved ad goes to a person on our team to build in your own ad account, and the activation step never touches an ad you have stopped.
Questions, answered.
Can an ad run without my approval?
Only where a run date has been set for the engagement, and the screen says so on each ad: it runs on that date unless you stop it, and one click stops it, even after it starts. Otherwise an ad runs after you approve it.
Who is recorded as the approver?
The person signed in when the button was pressed. The record reads it from your sign-in, never from a typed name.
Can I approve several at once?
One ad at a time, as fast as you can read them. Each decision saves on its own and is recorded on its own.
Which placements does this cover?
Meta feed, Stories and Reels, and carousel cards today. A set can also carry a square size for Google Display.
Why is there no Creative tab on my account?
It appears only where we run paid social creative for you. A Meta connection alone reads your Page numbers; it does not turn this view on.
Can I edit the copy before approving?
Ask for the change from the ad: press Request changes, type what you want, and the reworked ad comes back into the same queue. Nothing edits a running ad from this screen.
Does approving spend money?
No. An approved ad goes to a person on our team to build in your own ad account. Turning it on is a deliberate step by a person, and the result is read back from Meta.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.