Campaign rules

Every task campaign is checked by our team before it goes live, and it can be paused or removed later if reports or disputes show a problem. These rules keep workers safe and keep your approval rate high. By submitting a campaign you confirm you have read them.

What you can ask workers to do

• Visit a page, follow or subscribe, like, comment, share or repost.
• Sign up for a free account or newsletter.
• Install a free app and open it.
• Write an honest review of something they actually tried.
• Search a keyword and click your result.
• Test a website or app and report what they found.
• Simple data entry or research with clear instructions.

Every step must be doable by an ordinary person, in one sitting, with the links you provide. Put the steps in order in the Actions list so workers see them as numbered buttons.

What is not allowed

Campaigns like these are rejected, and repeat offenders lose advertiser access:

• Anything illegal, harmful or deceptive — fraud, fake identities, paying with someone else's card, gambling or adult content where it is prohibited.
• Tasks that break the rules of the site you send workers to — buying or selling accounts, mass fake reviews, vote or poll manipulation, engagement farming that the platform forbids. If the destination site would ban the worker for it, we will not run it.
• Asking for passwords, one-time codes, ID documents or payment card details, or any personal data beyond the username or email the task genuinely needs.
• Tasks that cost the worker money: deposits, purchases, paid subscriptions, "free trials" that need a card.
• Referral loops — asking workers to join GigBD or any site through your referral link as the task.
• Misleading titles, hidden steps, or requirements added after posting. The task text is frozen once the first proof arrives — use Clone to start a corrected campaign instead.
• Adult, violent or hateful content, malware, phishing or look-alike pages.

Write a campaign that gets approved

• One campaign, one task. Split unrelated asks into separate campaigns.
• The public title must describe the real task. The internal title is only for you.
• State the exact proof you need and choose the matching proof type (screenshot, text or both). A proof code is a good anti-cheat: place it where only someone who finished the task can see it.
• Give realistic effort for the pay. Very low pay for a hard task gets no takers and more disputes.
• Use Notes for moderators for anything our team should know (a test account, why the task looks unusual).

Pricing, budget and fees

• You set a base pay per completion and, optionally, a different pay per country. Workers only ever see the pay for their own country.
• Your campaign budget plus the platform fee (shown before you post) is reserved from your Spendable wallet. Each proof that comes in commits its pay; approvals spend it, rejections release it.
• When the remaining budget can no longer cover another completion — or your optional completions cap is reached — the campaign completes and whatever is left is refunded automatically. You can add budget at any time from the campaign page.
• Cancelling refunds the unused budget once every pending proof has been reviewed.

Review proofs fairly

• Review within your approval time. Anything you have not reviewed by then is approved and paid automatically.
• Approve when the proof shows the task was done as instructed. Reject only for a specific reason the worker can act on ("screenshot does not show your username"), never to avoid paying.
• Workers can dispute a rejection within 48 hours. You then have 48 hours to accept (the worker is paid) or decline with your reasons; after that our team decides. A dispute decided for the worker is paid from your campaign budget, or from your Spendable wallet if the campaign has already closed.
• A high dispute rate is shown on your Advertise page and can get new campaigns held for review.

Targeting and repeats

• Country, device and OS, gender, age, KYC-verified-only and "fewer than N tasks today" filters decide who can see and submit — they do not guarantee results. Device and OS are checked from the worker's browser when they submit.
• Frequency cap lets the same worker repeat the task after the wait you choose. Use it only for tasks that genuinely repeat (daily check-ins, recurring visits). Once per user is the default. A worker can only have one proof waiting for review per campaign.

Moderation

We may pause, edit the visibility of, or remove a campaign that draws reports, an unusual dispute rate or complaints from the destination site. Repeated violations end advertiser privileges; unspent budget is refunded, fees on work already paid are not.

Questions before you post? Open a ticket from Support in your dashboard.