How to make a product ad for Meta Ads from a shop page

Last updated 2026-08-24 · 7 min read

What is the short version?

A paid ad is judged on the first two seconds and on whether the price and product are legible. Everything else follows from getting real product detail off the page and putting it on screen without anything clipping at the frame edge.

1. Go to Vizard Agent and give it the product page link.
2. Say it is for Meta Ads and how long it should be.
3. Say which products to feature if the page has several.

What do you need before you start?

A link. Vizard Agent reads the page, collects the photographs, pulls the branding and generates the in-context shots, so a URL is genuinely the whole brief. Naming the products helps when the page lists a range, since a twenty-second ad holds a handful rather than a catalogue.

• The product page. Vizard Agent reads it and its source.
• The products. Which ones, if there is a range.
• The length. Fifteen to thirty seconds for a paid placement.
• The language. It decides the typeface search.
• Your own photos. Optional; Vizard Agent finds the page's own.

What do you type into Vizard Agent?

Name the platform, not just the format. Vizard Agent treats "for Meta Ads" as a set of constraints on length, aspect and how much text can sit on screen, which is different from the same brief for an organic post.

Prompt

Variants worth knowing:

• A price card. It performs, and it has to be legible at a glance.
• In-context generated shots. For products photographed only on white.
• Macro crops. For anything where the material or texture is the selling point.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real product ad. Two habits stand out: it went into the page source when the visible layout did not show prices, and it examined the top and bottom edges of every card separately at the end.

1. Reads the product page and collects the product images from it.
2. Digs into the page source for the prices the rendered layout does not display.
3. Reads one product page in full for the size and material details.
4. Hunts for higher-resolution photographs and collects a second image of each product.
5. Pulls the brand's colours and logo, screenshotting the site header and cropping the mark cleanly.
6. Generates music and in-context product shots, then reads the music's beat grid.
7. Builds the card graphics, re-renders them with bigger type after review, and starts upscaling the product photographs.
8. Finds and tests a bold typeface that renders the language correctly, then measures the products to prepare macro crops.
9. Assembles the ad, measures how far the graphics extend, inspects the card animations over time, cleans up clipped card tops and re-renders until the edges are correct.

Step 9 is the unglamorous finish that decides whether the ad looks professional. A card animating in from the edge can clip a pixel row at the top or bottom, and on a paid placement that single artefact is what a viewer registers before the product.

What does the result look like?

From the run this page is written from, probed on the delivered file: 1080x1920, H.264, 30fps, 21.37 seconds, AAC audio. Vertical, twenty-one seconds, the shop's own upscaled product photographs cut with generated in-context shots, macro crops, price cards in the brand's colours and cuts placed on the music's beat grid.

Twenty-one seconds sits in the middle of the paid range for a reason. It is long enough to show four products and a price and short enough that the cost per completed view stays sensible, which is the constraint an organic post does not have.

When does this not work well?

An ad built entirely from a shop page inherits every limitation that shop page has. Vizard Agent upscales the photographs, generates the shots that are missing and crops around the rest, and a thin product page still puts a ceiling on how good the finished ad can be.

• Low-resolution photographs limit everything. Vizard Agent upscales them and cannot add detail.
• Prices change. An ad with a price card needs re-rendering when the shop does.
• Generated in-context shots are illustrative. They are not photographs of your product in use.
• Platform ad policies apply. Claims, pricing and category rules are yours to check.
• A range does not fit. Four products in twenty seconds is already brisk.

How do you fix a result that came back wrong?

Name the card or the product. Vizard Agent keeps the page content, both photographs of each item, the brand colours, the beat grid and every card version, so a price change or a swapped product is a re-render rather than a fresh read of the shop.

• "That price is wrong now." Corrected from the page and the card re-rendered.
• "The card is clipped at the top." Measured and cleaned, as this run did.
• "Show the texture closer." A macro crop, prepared from the measured product.

How does Vizard Agent compare to doing it yourself?

By hand this means saving product photos at whatever resolution the shop serves them, building price cards in a template, and hoping the type renders correctly in your language. The clipped card edge is the failure that survives review, because it appears for three frames during an animation and nobody scrubs that closely.

Common questions

Does a paid ad differ from an organic post? Yes, and Vizard Agent builds to that. A paid placement is shorter, front-loads the product and carries a price, because it is bought by the view rather than found by chance.

Is a link enough? Yes. Vizard Agent reads the page, digs into its source and collects its images.

What if the prices are not on the page? Vizard Agent digs into the source, which is where shop templates often keep them.

How long should a Meta Ads video be? Fifteen to thirty seconds. This run delivered at twenty-one.

Can it show the product in use? Yes, as generated in-context shots. They illustrate rather than photograph.

Why check the card edges so carefully? Because a graphic that animates in from off-screen can leave a clipped row of pixels at the frame edge for a few frames. It is invisible in a timeline and unmistakable on a phone, and on a paid placement it undermines everything else in the ad.

Will it match our brand colours? Yes, sampled from the site and its header rather than approximated.

Does it cut to the music? Yes. Vizard Agent reads the beat grid and places the cuts against it.

Does Vizard Agent check the finished ad? Yes. It reviews the cut, fixes what it finds and has the render watched for beat and sync problems.