Capabilities

See every ad as it will run, before it runs.

Each ad draft lands on your own dashboard with its image in every placement, its copy and the audience it will reach. Press Approve or Request changes and our team is told as you press. Approving builds the ad paused in your ad account; switching it on is a separate step.

Illustration: A floating browser window showing a glossy ad card with an image thumbnail, a copy panel, a paused toggle switch, and two rounded buttons glowing green and gray beside it.

What do 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 linked to the full-size file. Beside it sit the four pieces of copy Meta will show: the ad text, the headline, the description and the button. One build writes both the screen and the image, so any words in the picture are the words you read beside it. What you approve is what runs.

Ads sit under their campaign. Above each campaign the view names the audiences one by one, who the ads will not be shown to, where a click lands, and anything we still need from you before the campaign can run. A set opens with its count, approved of total, a short note on what the set is, and one line on what happens when you approve.

The queue tells you plainly where it stands. When it is empty, the view says so in one line: no ad creative waiting on you right now, and new work shows up the moment it is ready. If the service behind the view is briefly unreachable, the view says that too, and the rest of your dashboard carries on.

4:5feed
9:16Stories and Reels
1:1carousel cards
4pieces of copy: text, headline, description, button

Every placement an ad was built for, labelled with its size and linked to the full-size file.

How do I approve an ad, or send it back?

Press Approve. The ad is marked approved, with the time, and the screen confirms it. 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, so each decision is recorded the moment you make it, and a decision that fails to save says so and asks you to try again. Approve as many as you like in one sitting, one ad at a time, as fast as you can read them. A set of eleven leaves eleven records, not one.

Our team is told as you press. Each decision posts to your account's channel on our side and emails [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. A live ad is improved the same way: the new version comes through the queue for your decision and replaces the old one once you approve it.

Every button saves on its own

  • Approve
  • Request changes
  • Leave a note
  • Undo
One record per decision
  • Posted to your account's channel on our side
  • Emailed to [email protected]
  • A reworked ad, back in the same queue

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, and the time. Each open of the view is logged with the time as well, so the record shows when the set was looked at, not only what was decided. Opens are logged, not announced; only a decision reaches our team.

Every rendered image is opened by a person on our side, who writes down what it shows, before the set reaches the queue. That note is checked against the copy: an ad whose words say schools and job sites carries a photo of a school or a job site, and of two ads whose photos show the same subject, one goes 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 a sign-in reads that business's drafts alone, and a set appears once it is fully built. The screen receives a fixed list of fields: our working notes on a set, what is holding it back and which claims we declined to make, stay on our side.

Illustration: A rounded ledger card stamped with a small padlock and a clock face, with a subtle timestamped tag attached to its corner.

When does an approved ad start, and can I stop it?

Approving records the decision and builds the ad, paused, in your Meta ad account, from the record of what you approved. The full-size file linked under each image is the file uploaded to your ad account. Switching an ad on is a separate step, taken against that record, and everything is read back from Meta after the switch. Budget and bid changes in your ad account are made within the limits set for your engagement and land in your account's own change history.

What you approved is what Meta shows. When the ad is built, Meta's automatic creative changes are switched off one by one: brightness and contrast edits, image templates, touch-ups, button enhancement and generated text. Each ad's link carries the campaign and the ad name, so a visit from it is traceable in your analytics to the ad that sent it.

Some engagements set a run date. When one is set, each ad you have not acted on says so in its card, with the date and time, Eastern, and no action is needed if it looks good. At that time a scheduled step switches on the ads you have not stopped, working from the record; every ad you have stopped stays exactly where you left it, and the result is read back from Meta. Stop this ad opens a box for one line on why, and Send to my team files it, any time: before the run date that keeps the ad off, and after it starts our team pauses it in your ad account. 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. Spend, reach and results from your Meta ad account are read into our reporting today and arrive on the dashboard as that view is built. Where we also run your Google Ads search, those campaigns report on the Google Ads view with the daily change watch at 7:05am Eastern. Ask for a performance readout from the screen and a person answers.

From approval to running

  1. Built, pausedIn your Meta ad account, from the record of what you approved
  2. Automatic changes offBrightness, templates, touch-ups, button and generated text
  3. The default windowWhere an engagement sets a run date
  4. Switched onEvery ad you have not stopped, read back from Meta
  5. Stop this adOne line on why, and our team pauses it
Illustration: A glossy toggle switch mid-flip beside a paused badge, a small budget dial, and a linked thumbnail card reflecting the same image.

What you approved is what Meta shows.

Where do the images come from, and will 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. The masters run about 1.5 MB each and a review page shows a dozen at once, so the preview keeps the page quick; the full size link opens the master, and a re-rendered master gets a fresh preview on the next load. 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. The likeliest cause of one failing is the service behind it restarting, which takes 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 reaches you with its photo in place, or with a caption asking you to refresh in a moment.

760 pxwide: the review preview, made from the master
1.5 MBabout the size of each master
3retries per image, each waiting longer
45 sabout how long a service restart takes

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 it appears with real work in it, where there is creative to decide on. Social media management is on Command; the full list of what each tier includes is on the pricing page. A Meta connection reads your Page numbers; the creative view is switched on for your account when we start building paid social for you, and approvals stay their own screen.

The demo at demo.trulata.com runs the same engine code every client runs, for a fictional company with illustrative numbers. The creative view is a per-client screen, switched on where paid social runs, so check two things in the demo 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, labelled read-only on the screen; it is the reading side of Meta, and the creative view is the deciding side, kept apart on purpose.

Setup puts the access in place before the first set is built. First 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. Our team collects it during setup, so the connection is done for you, and we never ask for your account password. The first set is built from your photos, checked image by image, and lands in the queue at zero approved, waiting on you.

  1. Share accessYour Facebook Page and ad account, into our Business Manager
  2. We collect itDuring setup, alongside the Google manager invitations
  3. The first setBuilt from your photos, checked image by image
  4. Your queueIt lands at zero approved, waiting on you
The spec

What the creative view reads and writes.

WhatWhere it comes fromHow fresh
Ad draftsBuilt by our team from your photos; the copy shown is the copy that runsAs built
Approve, request changes, note, undoWritten to the ad's record with the timeLive
Team noticeYour account's channel on our side and [email protected]As you press
PublishingBuilt paused in your Meta ad account from the approved record; switched on as a separate stepAfter approval, or at the run date where one is set
ImagesYour photographs; preview at 760 pixels, master at full sizePer ad
AvailabilityAccounts where we run paid social creativePer account
Approving and switching on are separate steps

An approved ad is built paused in your own ad account from the record of what you approved, and the activation step leaves every ad you have stopped exactly where you left it.

FAQ

Questions, answered.

Can an ad run without my approval?

Only where a run date is set for the engagement, and each ad's card says so with the date and time. It runs on that date unless you stop it: press Stop this ad, say why in a line, and send it. Otherwise an ad runs only after you approve it.

Can I approve several at once?

One at a time, as fast as you can read them. Each decision saves and is recorded on its own.

Which placements does this cover?

Meta feed, Stories and Reels, and carousel cards. A set can also carry a square size for Google Display.

Why is there no Creative tab on my account?

It appears once we build and run paid social creative for you. A Meta connection on its own reads your Page numbers; the creative view is switched on for your account when paid social starts.

Can I edit the copy before approving?

Through Request changes: type what you want, and the reworked ad comes back into the same queue for a fresh decision. A running ad is improved the same way, with the new version replacing the old one once you approve it.

Does approving spend money?

Approving builds the ad paused in your own ad account from the record of what you approved. Switching it on is a separate step against that record, 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 your name and email in front of it. Pricing is three published tiers.

Open the live demo See pricing

New here? See what TruLata is. Prefer to write? Send us the one thing you want to know.

Start here: AI marketing platform · AI marketing software · all-in-one marketing platform · marketing automation software · marketing software for small business.

  • 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
  • Seen in AI answersHow often ChatGPT, Gemini, Claude and Grok name you, measured
  • Every send loggedProspect emails leave from a review-first queue, and every send is logged.