Playable Ad End Card: Design the Last Moments

The end card is where a playable ad asks for the install. Here is what to put on it, when to show it, and how to test that the button actually works.

By the PlayableRun team··8 min read

Key takeaways - The playable ad end card is the point where interest turns into a store visit. It deserves as much design attention as the gameplay. - Show one dominant end card CTA, your icon and name, and a line that echoes what the player just did. Remove everything that competes with them. - Trigger the end card from a clear moment (success, failure, or inactivity) so nobody gets stuck on a dead-end screen. - Test the store handoff on real devices for every network you export to. A beautiful end card with a broken button earns nothing. - When you test variants, change one element at a time so you know what caused any difference.

What the end card is actually for

A playable ad has one job: get the right person to open your store page. The tutorial and core loop create interest, but the end card is where you ask for the action.

At that point the viewer has just finished a small experience. They have some momentum and some curiosity. The end card either channels that into a tap or lets it fade. Most of the design choices below come down to not wasting that moment.

If you want the wider picture of how the end card fits with the tutorial and core loop, Playable Ad Best Practices covers the full structure. This article stays on the closing screen.

What belongs on the end card

Keep the list short. Each extra element divides attention, and attention is the thing you are spending.

  • App icon and name. This confirms what was advertised and matches what the viewer will see in the store. A mismatch creates hesitation.
  • One primary CTA button. Large, high contrast, and unambiguous.
  • A short headline tied to the experience. For a puzzle game, "Level cleared. Ready for the next one?" works better than a generic tagline because it continues what the player just did.
  • Optional social proof you can verify. A store rating is fine if it is current and real. Do not hard-code a rating that will go stale when the listing changes.
  • Optional secondary action. A replay option can help, but only if it is clearly lesser than the main button.

What does not belong: long feature lists, legal paragraphs beyond what the network requires, multiple competing buttons, or a second mini-tutorial.

Designing the end card CTA

The end card CTA is the most important single element on the screen. A few practical rules, each with its reason:

  1. Use a verb the viewer understands. "Install", "Play now" and "Get the app" are all clear. Cute phrasing makes the viewer wonder what happens next, and doubt is a reason not to tap.
  2. Match the promise to the destination. If the button says "Play now" and opens a store page with an install button, that is normal and expected. If it says "Free reward" and the store page shows no reward, you create distrust.
  3. Make it big enough for a thumb. People tap with one hand, often while doing something else. A small button in a corner invites missed taps.
  4. Give it contrast against the end card background. The button should be the first thing the eye lands on. Test it against the actual background, not only against your brand palette.
  5. Place it where the thumb already is. The lower-middle of the screen is usually comfortable. Avoid the very edges, where system gestures or the network's own overlay controls may interfere.

A subtle animation, such as a gentle pulse, can help the button stand out. Keep it calm. A frantic animation looks like a different ad and can feel like an attempt to trick a tap.

Choosing when the end card appears

The end card needs a trigger. There are three common ones, and good playables support all of them.

On success

The player completes the goal: merges the final tiles, clears the board, crosses the finish line. The end card appears right after the success feedback. Give the win animation a moment to register before the card arrives. Cutting it off feels abrupt and throws away the best emotional beat in the ad.

On failure

The player fails. This can be a strong moment because many people want to try again. Show the end card with a headline that frames the failure as a near miss, and make the CTA the clear next step. Failure should feel like an invitation, not a punishment.

On inactivity

Some viewers stop interacting. Without a fallback they sit on a frozen scene and eventually leave without ever seeing the install prompt. An inactivity timeout moves them to the end card so the prompt is still shown. Set the limit relative to your tutorial pace. Playable Ad Length discusses how long the whole experience should run, which helps you pick a sensible threshold.

Making it an interactive end card

An interactive end card goes beyond a static image with a button. Used with restraint, it keeps the viewer engaged a little longer and makes the final ask feel earned.

Examples that tend to work:

  • A reward reveal. The player taps a chest or card to see what they "earned", and the CTA sits right beside it.
  • A final-score screen. Show the score or star rating the player just achieved, then the button.
  • A next-level teaser. The player sees a locked or blurred next stage, and the CTA invites them to continue in the full app.

Examples that tend to backfire:

  • Extra mini-games on the end card.
  • Several tappable areas that all do different things.
  • Anything that puts another interaction between the viewer and the CTA.

The rule of thumb: if an interaction does not make the main button more attractive, remove it.

This also applies outside games. A budgeting app might end on a summary of the savings the viewer just "unlocked", and a fitness app might show a completed workout streak. Playable Ads for Apps Beyond Games has more examples by vertical.

Layout, orientation and safe areas

End cards get cropped, overlaid and resized in ways the gameplay screen often does not. Plan for that.

  • Design for every orientation the network allows. A layout that looks right in portrait can push the button off-screen in landscape. Check the network's current spec for which orientations it supports.
  • Leave margins for network overlays. Close buttons, timers and sound toggles are often placed on top of your creative. Keep key content and the button clear of those zones.
  • Respect device cutouts. Notches and rounded corners can hide content near the edges. In web content, the CSS env() function exposes safe-area insets, though not every ad container passes them through, so verify on devices.
  • Scale text for small screens. A headline that fits on a large phone can wrap badly on a small one. Keep it short enough that wrapping is not a problem.

Handling the store handoff

The CTA only works if it triggers the network's own click-through mechanism. Each network expects a specific call or setup in the creative, and a button that merely navigates somewhere will not register correctly or may be rejected. Google Ads, for example, has particular requirements for how the click is declared in an HTML5 asset. Check the network's current documentation rather than relying on memory.

Related practical points:

  • Make the whole flow tappable only where intended. Accidental taps on the background that open the store feel deceptive and can cause policy problems.
  • Confirm the destination. The right store, the right app, the right platform for the device. Test with both an iOS and an Android device if you run both.
  • Keep sound and motion considerate. Do not start loud audio on the end card.

If an export gets rejected, HTML5 Ad Disapproved in Google Ads walks through common causes. For limits that differ between networks, Playable Ad Specs is a useful checklist before you export.

Testing the end card

Treat the end card as its own test surface. Gameplay changes may shift engagement. End card changes shift what people do after engaging.

  1. Test the mechanics first. On real devices, reach the end card by success, failure and inactivity. Tap the CTA each time and confirm the correct store page opens.
  2. Check every orientation and a couple of screen sizes. Look for clipped text, hidden buttons and overlay collisions.
  3. Then test the design. Vary one element: the button label, the headline, the reward reveal, or the layout. If you change three things at once you will not know which one mattered.
  4. Let each variant run long enough. Early results are noisy. Avoid calling a winner from a thin sample.
  5. Record what you changed. A short note per variant saves you from repeating old tests.

Reviewing machine-generated output follows the same logic. If you generate a draft, check the end card yourself with this list. AI Playable Ad Generator: How to Review the Output covers what to look for.

Common mistakes

  • A CTA that looks like decoration. Low contrast, small size, or a label the viewer does not recognise as tappable.
  • Too many choices. Two or three equal-looking buttons split the decision.
  • An end card that arrives too early. The viewer has not yet felt any payoff, so the ask feels premature.
  • No fallback trigger. Inactive viewers never see the end card.
  • Mismatched branding. The icon, name or art style differs from the store listing, so the viewer wonders if they are in the right place.
  • Skipping device testing. Previews in a browser do not reveal overlay clashes or handoff failures.

Where to go from here

Open a few finished playables and tap through to the end card on your own phone, noticing what you look at first and what you would change. PlayableRun's demos include complete examples you can try that way, and if you want to build your own end card from a store listing, you can create a free account and see what the first draft looks like.

Frequently asked questions

›What should a playable ad end card include?

Your app icon and name, one dominant call-to-action button, and a short line that continues what the player just did. Everything else, such as extra buttons, long feature lists and legal text beyond what the network requires, competes with the button and should usually go.

›When should the end card appear in a playable ad?

After a clear trigger: the player succeeds, the player fails, or the player stops interacting for a while. Supporting all three means nobody gets stuck on a frozen scene without seeing the install prompt.

›Should the end card be interactive?

It can be, as long as the interaction makes the main button more attractive. A reward reveal or a final score screen works. Extra mini-games or several competing tap targets usually hurt.

›How do I test the end card CTA?

Tap it on real devices in each network's preview or test tool and confirm it opens the correct store page. Also check both orientations the network supports and look for overlap with the network's own close or sound controls.

›Can I A/B test end cards?

Yes. Change one element at a time, such as the button label, the headline or the layout, so you can tell which change caused any difference. Give each variant enough delivery before drawing conclusions.

Sources

Turn your store listing into a playable

Paste an App Store or Google Play link and get an HTML5 playable you can test in minutes. The first one is free.

Keep reading