How to write a UGC ad script for an app (with a full example)

A good UGC ad script for an app is not a list of features read to camera. It is a 20 to 35 second story in three beats: a hook that names a moment your user knows, a body where the creator shows the app solving it on screen, and a call to action that removes the last doubt about trying it.

Short answer: to write a UGC ad script for an app, pick one angle from real user language, write a hook that lands in the first 3 seconds, show one core action in the app instead of a feature tour, and end with a low-friction CTA. Keep it to about 60 to 80 spoken words, written in a two-column "say / show" format.

Below is the exact process, a full worked example, hook lines you can adapt, and the mistakes we see most often in app scripts.

What makes an app UGC script different

Most UGC script guides are written for physical products. Apps have three problems those guides skip.

• The product lives on a screen. The viewer has to see the app doing something, so your script needs screen recording moments, not just a talking face.
• The value comes after the install. Nobody feels the benefit in the ad. They need to believe they will get it in their first session, so the script should show that first payoff.
• The ask is bigger than it looks. Installing, signing up and starting a trial are real effort. The CTA has to lower that effort, not just say "download now".

Step 1: Pick one angle from real user language

The angle is the reason someone should care. One script, one angle. If you try to cover "saves time", "it's cheap" and "it looks nice" in 30 seconds, none of them land.

Don't brainstorm angles in a meeting. Pull them from places where users already describe the problem in their own words:

• Your App Store and Google Play reviews, especially 4 and 5 star reviews that mention life before the app.
• Support emails and onboarding survey answers ("What made you download us?").
• Competitor reviews, especially the 2 and 3 star ones. They tell you what people wish existed.

Copy the exact phrases. "I kept forgetting what I'd already spent this week" is a better script line than anything a marketer would write, because it is how your buyer talks.

Step 2: Write the hook for the first 3 seconds

The hook decides whether anyone hears the rest. TikTok's own creative best practices recommend introducing your value proposition within the first 3 seconds. In practice, write the hook so it works even if the viewer only hears the first sentence.

Good app hooks usually do one of four things:

• Name a specific moment: "It's Sunday night and I have no idea what I'm eating this week."
• Call out the viewer: "If you've started a budget three times this year, this is for you."
• Confess a habit: "I used to pay for four streaming apps and use one."
• Show a surprising result first: "This is my whole month of expenses, sorted in 10 seconds."

Write 3 to 5 hooks for every script and keep the body identical. That way you can film them all in one session and test which opening stops the scroll. It is the same logic we explain in how many UGC ads to test on Meta: change one thing at a time so the results teach you something.

Step 3: Show one core action, not a feature tour

This is where most app scripts go wrong. The founder wants every feature in the ad. The viewer remembers none of them.

Pick the one action that delivers the payoff from your angle, and show it from start to finish on screen. For a budgeting app, that might be connecting a card and seeing spending grouped by category. For a SaaS tool, it might be pasting a messy document and getting a clean summary back. Use a real screen recording at normal speed so it feels honest.

A simple structure for the body:

1. One line on the problem, in the user's words.
2. "So I tried [app]" or a similar natural turn, with the app on screen.
3. The core action, narrated plainly: what they tap, what they see.
4. One line on how it feels now, or what changed.

Step 4: Write a CTA that lowers the effort

"Download now" asks for effort without giving a reason. A better CTA answers the viewer's real question: "Is this going to be a hassle?"

• "It's free to try, you don't even need a card."
• "Took me two minutes to set up, link's right there."
• "Try the first week and see if you actually stick with it."

Only promise what is true for your app. If there is no free trial, don't say there is one. Both Meta and TikTok review ads, and a misleading line also costs you the trust of the users you just paid to acquire.

UGC ad script example for an app

Here is a full script for a fictional budgeting app called "Penny", in the "say / show" format we use: what the creator says, and what the viewer sees.

1. 0 to 3s. Say: "I checked my bank app and could not tell you where 600 dollars went." Show: creator on face cam, phone in hand, text on screen "where did it go??"
2. 3 to 8s. Say: "I'm not a spreadsheet person. I tried, it lasted four days." Show: quick cut to an abandoned spreadsheet.
3. 8 to 20s. Say: "So I tried Penny. You link your card and it sorts everything. Look, food delivery, 212 dollars. That's the one." Show: screen recording of linking a card, categories filling in, zoom on the total.
4. 20 to 26s. Say: "Now I get one message on Sunday with my week, and that's it." Show: creator relaxed, insert of the weekly summary.
5. 26 to 30s. Say: "It's free to try. Took me two minutes." Show: creator points down to the CTA button area.

That is about 70 spoken words for 30 seconds, which leaves room for natural pauses. Most people speak at roughly 130 to 160 words a minute, so if your draft has 120 words for a 30 second ad, it will either be rushed or run long. Cut it.

How long should a UGC script be?

For app and SaaS ads on Meta and TikTok, 20 to 35 seconds is a sensible default for a first test. That is long enough to hook, show the app working and ask for the install, and short enough that the core action isn't buried. Shoot vertical 9:16 and keep captions and key screen moments away from the edges, where the platform interface covers them.

Script mistakes we see most in app ads

• Opening with the app name. "Hi, I'm using Penny" gives the viewer no reason to stay. Lead with the problem, introduce the app at second 5 to 10.
• Writing like an ad. Lines like "revolutionary all-in-one solution" sound fake in a creator's mouth. If your friend wouldn't say it, cut it.
• Over-scripting every word. Script the hook and the key claims exactly. Give the creator bullet points for the rest so it sounds like them. Our guide on how to brief UGC creators shows how to split the two in a brief.
• No screen time. A face talking about an app for 30 seconds without showing it asks the viewer to imagine the product. Show it.
• Three angles in one video. Split them into three scripts and test them against each other instead.

Recap: your UGC script checklist

• One angle, taken from real user or review language.
• 3 to 5 hooks written for the first 3 seconds, same body.
• One core action shown on screen at normal speed.
• A CTA that lowers the effort and only promises what is true.
• 60 to 80 spoken words for about 30 seconds, in a say / show format.

Still deciding whether you need UGC creators or influencers at all? Read UGC vs influencer marketing for apps first.

If you'd rather hand this part off, here is how our UGC scripting and production process works: we write the scripts from your reviews and onboarding data, then real creators film them face cam.

FAQ

What should a UGC ad script for an app include?

A hook in the first 3 seconds, one line on the problem, a screen recording of one core action in the app, and a CTA that makes trying it feel easy. Everything else is optional.

How many words should a 30 second UGC script have?

Around 60 to 80 spoken words. That leaves time for pauses, reactions and screen moments without the creator rushing.

Should I give UGC creators a word-for-word script?

Script the hook and any product claims word for word, and give bullet points for the rest. Creators sound more natural when they can phrase the middle in their own words.

Is a UGC script for a SaaS product different from one for a mobile app?

The structure is the same. The main difference is the screen: SaaS ads usually show a laptop or browser recording, and the CTA is more often a free trial or demo than an install.