How to promote a contest entry under IP and device limits

What does an IP or device limit change for contest promotion?

An IP or device limit can prevent another vote from the same connection or device, even when the next supporter is a different person. Promotion still works, but the message and timing must account for people sharing Wi-Fi, computers, tablets, or mobile connections.

The first task is not to estimate how many votes a group might deliver. It is to make participation clear and voluntary, and to avoid sending a large group to vote from one shared network at the same moment. A useful plan gives each supporter the contest link, explains the stated rule, and says what to do if the page reports a previous vote.

For a campaign, CoinMarketingCap can prepare an audience map, group-specific vote requests, and a Proof Log to record supporter reports and the visible counter at planned check-ins. These are practical records, not a claim to see the contest's internal detection method. For broader planning, see contest marketing and the guide to voting protection types.

How can you check what supporters are being asked to do?

Start with the published contest rules and the voting page. Record the exact language about network, device, or repeat voting, then compare it with what supporters can actually see when they try to participate.

Do not infer a platform's hidden method from one message. A notice such as “already voted” does not tell you whether the contest recognised a shared network, a device, or another condition. Keep the distinction between observation and interpretation visible in your notes.

Before you write an outreach message, collect:

• The contest link and the relevant rule text.
• A screenshot or exact wording of any blocked-vote notice, with personal details removed.
• The supporter’s setting, such as home Wi-Fi, office, school, public Wi-Fi, or mobile data.
• Whether the supporter believes they have already voted, and what they did next.

A short Evidence Pack makes it easier to spot a pattern and ask the organizer a precise question. If the contest rule is unclear, use contest rules and risk consulting before sending a wide outreach wave.

Which shared-network situations need a different outreach plan?

Supporters who connect through the same router, workplace network, school connection, venue Wi-Fi, or shared device may encounter the same restriction. Grouping people by their usual setting helps you choose a suitable message and timing without telling anyone to alter or disguise their connection.

This map is for planning, not predicting which specific supporter will be accepted. Treat each report as a description of what happened, not proof of how the contest identified a visitor. For contests involving young participants, involve a parent or guardian and review the guidance for youth contests before outreach.

What should a vote request say to someone on shared Wi-Fi?

A good request makes the one-person, one-vote expectation clear and gives a calm next step if a shared connection causes a block. It should not pressure someone to keep retrying or suggest ways to get around the restriction.

For example, a message to a household could read:

If you’d like to support my entry, please read the contest rules and vote once on your own device: [entry link]. People sharing Wi-Fi may see an “already voted” notice. If that happens, please stop and let me know what the message says so I can ask the organizer.

For a school, office, or community group, send the invitation in a way that lets each person decide for themselves. Avoid putting a voting form on a shared screen and asking everyone to submit at once. If you need several versions of the request, the vote-request templates offer a starting point, while community, email and messenger outreach covers consent-based ways to share it.

Before sending, check that the link works, the voting instruction matches the published rules, and the message explains how to report a block. Keep the request brief enough that supporters can understand it before opening the contest page.

How should you pace group outreach and keep a useful record?

Separate outreach to groups that are likely to share a connection, and keep a simple record of when each invitation went out. Staggered messages avoid directing a whole room or workplace to the voting page together, and make it easier to understand which group is reporting problems.

A practical working sequence is:

1. Confirm the rule and the wording on the voting page.
2. Sort intended supporters by setting, such as home, school, work, or public venue.
3. Prepare one clear invitation for each relevant group.
4. Send messages at separate times and invite people to vote individually.
5. Record blocked reports, the group setting, and any visible counter changes.
6. Ask the organizer for clarification when a genuine supporter remains blocked.

Keep records factual: time of report, setting, visible message, and the action taken. Do not turn a change in the visible counter into a claim about how many attempts the contest rejected. A contest campaign calendar can help organize outreach waves, and contest methodology explains how to review campaign activity without overstating what the available evidence shows.

Where is the line between helpful guidance and bypassing a limit?

Helpful guidance explains the rules and gives supporters a respectful way to participate once. It does not coach them to create an additional vote or make a vote appear to come from somewhere else.

The organizer decides how a network or device is recognised, and a shared connection may block a genuine participant; only the organizer can clarify or change that handling. We do not sell votes, followers, or engagement, and we do not use bots, scripts, fake accounts, or click farms; our work follows white-hat methods and the contest’s rules.

If a supporter reports a block, ask them to stop rather than test multiple devices or connections. Save the notice, note the setting, and contact the organizer with a concise explanation. If the rules prohibit outside promotion, stop and review the situation before continuing. The no-bots policy sets out our boundaries, and contest promotion rules and risk checks can help you review the requirements before a campaign begins.

What should you prepare before asking for help with an IP or device limit?

A clear starting file lets an adviser check the rule, the supporter experience, and the proposed outreach in one review. Gather the contest URL, your entry link, the published rules, the voting deadline, and any reports from supporters who share a network or device.

Add a brief note describing the groups you hope to reach: household members, colleagues, students, event visitors, or mobile users. Include the exact wording of any block message and remove names, phone numbers, and other personal information from screenshots. If you have already sent invitations, include the message and when it was shared; this helps distinguish a wording issue from a connection issue.

The review can then identify unclear instructions, suggest questions for the organizer, and shape group-specific outreach that respects the rules. The agreed work may include promotion planning, creative, paid advertising, or consent-based outreach; paid promotion for contest entries and contest creative and copy explain those options. Send these materials through the free contest analysis. We’ll review the rules and your supporter map, then recommend a clear next step before any campaign work begins.

How it works

1. Read the contest ruleNote whether the published instructions mention a network, device, or repeat-vote restriction. Save the wording so your outreach matches it.
2. Map supporter settingsGroup people by likely connection type, such as home, school, office, venue, or mobile data.
3. Write a clear invitationExplain the one-vote expectation and tell supporters to report a block rather than keep trying.
4. Stagger outreachSend invitations at separate times and avoid organizing a shared-room voting session.
5. Record reports and reviewNote the visible notice and setting, then ask the organizer for clarification when needed.