Does the app install make this contest a good fit for your audience?
App-only voting is easiest to promote when your likely supporters are comfortable installing an app and already have a reason to help. Before planning reach, check whether the extra step is reasonable for the people you want to ask.
Start with three practical questions:
- Can they install it? Check which phone systems the app supports and whether the official store listing is available where your supporters live.
- Will they complete the route? Ask a few people who resemble your audience to follow the instructions. Notice where they hesitate, not just whether they reach the voting screen.
- Is the route worth explaining? If the app requires an account, a confirmation code or a search for your entry, make sure you can describe each part briefly.
A close community may be willing to install an app for someone they know. A broad audience that has never heard of the entrant may need more context before taking that step. If the route feels too involved, adjust the audience or the message before putting effort into promotion. Our wider contest marketing guide helps you compare campaign approaches, while the contest protection overview explains how voting requirements affect the ask.
What does a supporter need to do between the first tap and the vote?
Write down the actual route in the order a supporter experiences it. That gives you a reliable basis for instructions and makes hidden points of friction easier to spot.
| Stage | What to check | What to explain |
|---|---|---|
| Open the link | Does it lead to the official app listing or the app? | Which app name and publisher to look for |
| Install and open | Does the app open normally after installation? | That installing and opening are separate steps |
| Sign in, if required | Does the app request an account or identity provider? | Which sign-in step the contest requires |
| Find the entry | Is there a direct entry link, or must supporters search? | The entrant name, category or entry number |
| Submit the vote | Is there a final button or confirmation screen? | How to tell that the action has been completed |
Do not assume a tap on a link means someone has voted. The supporter may still need to install, open, sign in, locate the entry and finish the voting action. Ask the organizer to confirm the current steps, then test them yourself. If voting requires an account, review the details on registration and login; if the app offers social sign-in, check the social-login guide as well.
How should you check app-store links and deep links before sharing?
Test each link on a phone before it appears in a post, message or ad. A deep link may open a particular screen inside an app, but the result depends on whether the app supports that route and how the link is opened.
Check these situations separately:
- The app is installed: Tap the link and see whether it opens the entry, a general app screen or an error page.
- The app is not installed: Confirm that the link reaches the organizer’s official store listing. After installing, check whether the app returns to the intended entry or requires the supporter to start again.
- The link opens inside another app: Try it from the social platform’s built-in browser as well as a regular phone browser. If the handoff fails, add a short instruction to open the link in a browser.
- The entry has no direct link: Provide a name, number or category so the supporter can locate it without guessing.
Use store links supplied by the organizer and verify the app name and publisher shown on the listing. If there are separate listings for different phone systems, label each one clearly. Never ask supporters to install an app from outside official stores or to change their device protections. When a link behaves differently after an app update, test it again before sending another campaign message.
What should your request say before someone opens the app?
A good request gives people the steps before they tap, without turning a friendly message into a long instruction manual. Tell supporters that voting takes place in an app and name the main actions they should expect.
A useful message usually includes:
- The entrant’s name and a short reason you are asking for support.
- The official app name and a clearly labelled store link.
- A plain description of any sign-in, entry search or confirmation step.
- The entry name, number or category they will need to find.
- A reminder to follow the contest’s voting rules, including any stated limit.
Keep the first message easy to scan. Put the link and the essential steps near the top; put extra help, such as a fallback route if a deep link fails, after them. Read the message on a phone and ask someone unfamiliar with the contest to follow it. If they have to ask what to do next, revise the instruction rather than adding more promotional language.
We can adapt the request to the entrant’s own voice and prepare versions for different channels. The vote-request templates offer a starting point, and contest creative and copy can help make the instructions fit the wider campaign.
How do you plan reach and understand the activity you can see?
Plan outreach around people who can access the app and are likely to understand why you are asking. That can include messages to an existing community, consent-based email or messenger outreach, creator outreach, and paid promotion where the relevant platform permits it.
For paid campaigns, decide where a person should land before creating the ad: a store listing, a contest page with clear instructions, or another destination that makes the next step understandable. Prepare the destination and message together, then review the ad platform’s current rules. Our guide to paid promotion of contest entries covers that channel in more detail.
Reporting should separate what is visible from what is not. You may be able to compare link clicks from platform analytics with a public entry counter or information shared by the organizer. Those signals do not, on their own, show who installed the app or which click resulted in a vote. Record them consistently and use them to compare messages or identify a broken link, not to claim a precise path from ad to vote.
Agree in advance who will share any information the organizer can provide, how often you will review it and what changes you can make during the campaign. A short report that labels each signal clearly is more useful than a single number without context.
Which app-voting limits should you resolve before a campaign?
The organizer’s rules and the app’s actual voting route determine what supporters may do. Check them before drafting a request or choosing an outreach channel, and make the instructions match the current voting process.
Confirm that outside promotion is allowed, whether repeat voting is permitted, and whether the rules set a daily limit or other conditions. If those details are unclear, ask the organizer rather than filling in the gaps. For a structured review, use the contest rules and risk check. We never arrange purchased votes, followers or engagement, and our methods exclude bots, scripts, fake accounts and click farms. We also decline projects that require those practices or promotion that the contest rules forbid.
The app’s publisher and store control its availability and updates, while the organizer controls the contest instructions and may change the voting route. We cannot promise that supporters will install the app, submit votes or secure a win; we commit to the agreed preparation, promotion work and reporting, and label projections as projections.
What should you gather before asking for an app-voting plan?
A useful campaign plan starts with current details, not assumptions about what the app or contest allows. Send the materials below so we can review the route and identify questions before launch.
- The contest page, full rules and closing date, including its time zone.
- The organizer’s official app-store URLs for every supported phone system, and the publisher shown on each listing.
- Your entry’s name, number or category, plus a direct link if the organizer provides one.
- A description of the voting steps, including sign-in or confirmation requirements.
- The places and phone systems your likely supporters use, along with any channels you already have permission to contact.
- Any organizer-provided information you can use in campaign reporting.
At Brand Community, we review the rules and links, then walk through the install-to-vote route on a phone and note where instructions need clarification. We return practical recommendations for the supporter message, link handling, audience fit and visible reporting signals. Start with the free contest analysis: send the contest page, app links and entry details, and we’ll identify the next checks before you commit to a campaign.
How it works
- Review the contest routeWe check the rules, official app listings and the voting steps the organizer provides. We flag missing details before campaign planning moves ahead.
- Walk through the app on a phoneWe test the store link, install, opening route, entry search and vote confirmation. The notes show where supporters may need a clearer instruction.
- Prepare supporter messagesWe draft concise requests with the app name, link and expected steps, plus a fallback if a deep link does not reach the entry. You review the wording before it is used.
- Match outreach to accessWe plan channels and audiences around the app’s availability and the contest rules. Where paid promotion is part of the plan, the destination and message are prepared together.
- Review visible activityWe report link activity from platform analytics alongside entry information that is available to you. Each signal is labelled so clicks are not presented as confirmed app installs or votes.
Frequently asked questions
Do all app-voting contests require supporters to install an app?
Only if the organizer makes the app the voting route. Check the contest rules and the voting page to see whether a web option also exists. We plan around the route the organizer actually provides, rather than assuming a separate voting page is available.
What if the app is missing from a supporter’s store?
Check store availability for the regions and phone systems you hope to reach before promoting the entry. If someone cannot access the app, do not send them through an unofficial download route; ask the organizer whether another voting option is available and adjust the audience plan accordingly.
Can one deep link work for people with and without the app installed?
It may, if the app and link support both routes, but test each case rather than assuming. Check what happens when the app is installed and when it is not. If the destination is not preserved after installation, give supporters a short fallback with the entry name or number.
Can campaign reporting show who installed the app?
Not from link-click information alone. Platform analytics can show activity on the link, while the entry counter or organizer may provide separate voting information. We keep those signals distinct and do not label clicks as confirmed installations.
How long does app-voting campaign preparation take?
Preparation begins with reviewing the contest rules and testing the app route, then moves to supporter messages and campaign setup. The time needed depends on how quickly the organizer’s links and instructions can be checked, so share the closing date and current app details at the outset.
Can you promise a certain number of app votes or a win?
No. We deliver the agreed review, campaign materials, promotion work and reporting, but supporters decide whether to install the app and vote, and the organizer controls the contest process. Any projections are identified as projections, not outcomes.
Free starters on WhatsApp
Pick one. It opens a prepared message so we know what you need.
Replies usually arrive within 10-30 minutes in working hours (Mon-Fri 09:00-21:00 GMT+3). We do not share your contest details.
Tell us about your contest
Answer four quick questions and we reply with a plan and the next step. The free contest analysis comes first, and any quote is confirmed in writing before work starts.
Loading the form…