Reports & Moderation

Understanding the reporting system and how to handle flags on your codes

Reports & Moderation 🚩

Community-driven quality control keeps the platform trustworthy!

What is the Reporting System?

Users can report codes that have issues.

Why Reporting Exists

Protects shoppers from:

  • Broken/expired codes
  • Misleading descriptions
  • Offensive content
  • Scam attempts

Protects creators from:

  • False information
  • Bad actors
  • Platform abuse

Protects the platform:

  • Maintains quality
  • Builds trust
  • Fair competition

It's not about "getting in trouble" - it's about maintaining quality!

What Can Be Reported?

Users can flag your codes for:

1. Broken Link

Issue: Affiliate URL doesn't work

Common causes:

  • Link expired
  • Typo in URL
  • Brand changed links
  • Tracking parameters broken

Example:

Report: "Link goes to 404 page"

2. Code Doesn't Work

Issue: The discount code doesn't apply

Common causes:

  • Code expired
  • Wrong code entered
  • Restrictions not met
  • Already used (single-use)

Example:

Report: "Code says 'invalid' at checkout"

3. Misleading Information

Issue: Description doesn't match reality

Common causes:

  • Discount amount wrong
  • Restrictions not mentioned
  • Expires sooner than stated
  • Deal changed by brand

Example:

Report: "Says 20% but only gives 10%"

4. Offensive Content

Issue: Inappropriate language or content

Common causes:

  • Slipped through AI filter
  • Interpreted differently
  • Cultural misunderstanding
  • Genuinely inappropriate

Example:

Report: "Description contains offensive language"

5. Spam

Issue: Low-quality or promotional content

Common causes:

  • Keyword stuffing
  • External link spam
  • Repeated content
  • No real value

Example:

Report: "Just spam with random keywords"

6. Other

Issue: Doesn't fit other categories

Common causes:

  • Technical glitches
  • Duplicate codes
  • Wrong brand
  • Unusual circumstances

How Reporting Works

The reporting flow:

1. User Sees Issue

Shopper tries your code and encounters a problem.

2. User Submits Report

They click "Report Issue" and fill out form:

  • Select issue type
  • Provide details (optional)
  • Submit anonymously

Takes 30 seconds.

3. Report Enters Queue

Your code gets flagged for review:

  • Status: Under Review
  • Visible: Still shows on platform
  • Your notification: Email sent

4. You Get Notified

Within 24 hours, you receive email:

Subject: Action Required: Code Report

Code: BEAUTY20
Issue: Code doesn't work
Details: "Returns 'invalid code' error at checkout"
Reporter's note: "Tried 3 times, doesn't apply"

Action needed: Please review and update or respond

5. Admin Review

Our team investigates:

  • Checks the code
  • Reviews description
  • Tests the link
  • Considers context
  • Makes decision

Usually within 24-48 hours.

6. Resolution

Three possible outcomes:

Valid Report:

  • Code deactivated (if serious)
  • Required to fix
  • Re-review after fix

Invalid Report:

  • No action needed
  • Code stays active
  • Report dismissed

Partial Issue:

  • Asked to update details
  • Add clearer instructions
  • Fix specific elements

Types of Reports & Responses

How to handle each:

Broken Link Reports

If report is valid:

  1. Check the link

    • Test it yourself
    • Confirm it's broken
    • Find correct link
  2. Update the code

    • Edit code entry
    • Fix the URL
    • Save changes
  3. Respond to report

    • "Fixed! Updated URL"
    • Thank the reporter
    • Mark as resolved

If report is invalid:

  • Test and confirm link works
  • Provide evidence (screenshot)
  • Explain any requirements (e.g., VPN issues)

Code Not Working Reports

If code really doesn't work:

  1. Contact the brand

    • Verify code status
    • Get correct code
    • Check restrictions
  2. Options:

    • Update code if you got new one
    • Add instructions if restrictions apply
    • Deactivate if truly expired
    • Delete if no longer valid
  3. Update description

    • Add any new restrictions
    • Update expiration date
    • Clarify requirements

If code DOES work:

  • Test it yourself
  • Screenshot proof
  • Explain requirements
  • Update instructions to prevent future reports

Misleading Info Reports

If description is wrong:

  1. Review your content

    • Check discount amount
    • Verify restrictions
    • Confirm expiration
    • Test yourself
  2. Update immediately

    • Fix wrong information
    • Add missing details
    • Clarify restrictions
    • Be more specific
  3. Learn for future

    • Double-check before posting
    • Keep descriptions updated
    • Be conservative with claims
    • Under-promise, over-deliver

If description is accurate:

  • Provide evidence
  • Explain potential confusion
  • Improve clarity anyway
  • Add more details

Offensive Content Reports

If content IS inappropriate:

  1. Acknowledge the issue

    • Take it seriously
    • Don't get defensive
    • Learn from it
  2. Fix immediately

    • Rewrite description
    • Remove offensive parts
    • Use appropriate language
    • Run through AI again
  3. Apologize if needed

    • Brief acknowledgment
    • Shows professionalism
    • Builds trust

If content is NOT inappropriate:

  • Explain context
  • Cultural differences
  • Intended meaning
  • Consider revising anyway

Spam Reports

If it IS spam:

  1. Rewrite completely

    • Use natural language
    • Add real value
    • Be specific
    • Help the shopper
  2. Remove spam elements

    • No keyword stuffing
    • No all caps
    • No repeated words
    • Professional tone
  3. Follow content rules Review guidelines

If it's NOT spam:

  • Explain your intent
  • Show value provided
  • Improve clarity
  • Make it more helpful

Responding to Reports

Best practices for handling flags:

1. Act Quickly

Timeline:

  • Check email daily
  • Respond within 24 hours
  • Fix issues ASAP
  • Don't ignore reports

Why speed matters:

  • Shows professionalism
  • Maintains trust
  • Prevents escalation
  • Protects ranking

2. Be Professional

Good response:

Thank you for reporting this! I've tested the link
and updated it. The code should work now. I appreciate
you taking the time to let me know.

Bad response:

This is fine, you did it wrong.

Remember:

  • Reports help improve quality
  • Be grateful for feedback
  • Stay calm and professional
  • Fix real issues

3. Fix Don't Fight

If there's an issue:

  • βœ… Acknowledge it
  • βœ… Fix it fast
  • βœ… Thank reporter
  • βœ… Move forward

Don't:

  • ❌ Argue about technicalities
  • ❌ Blame the shopper
  • ❌ Get defensive
  • ❌ Make excuses

4. Learn and Improve

Use reports to:

  • Identify patterns
  • Improve processes
  • Update templates
  • Prevent future issues

Track:

  • Common issues
  • What triggers reports
  • How to prevent them
  • Better practices

Consequences of Reports

What happens with multiple reports:

First Report: Warning

  • Email notification
  • Asked to fix
  • No penalties
  • Learning opportunity

Action: Fix the issue, improve quality.

Multiple Reports: Review

3+ reports in 30 days triggers:

  • Account review
  • Manual investigation
  • Pattern analysis
  • Intervention if needed

Action: Review all your codes, improve quality across the board.

Repeated Violations: Penalties

Consistent issues may result in:

Soft Penalties:

  • Lower search ranking
  • Verification badge removed (Pro)
  • Feature restrictions
  • Probation period

Hard Penalties:

  • Code removal
  • Account suspension
  • Permanent ban (extreme cases)

We rarely reach this point - most creators fix issues quickly!

False Reports

What if someone reports you unfairly?

How We Handle

We investigate every report:

  • Don't auto-remove codes
  • Test codes ourselves
  • Review context
  • Consider patterns

One false report won't hurt you.

Malicious Reporting

If someone is abusing the system:

  • We track reporter patterns
  • Ban malicious reporters
  • Protect creators from abuse
  • Keep it fair

Don't worry about competitor sabotage - we're watching for that!

Appealing Decisions

Think we got it wrong?

  1. Email: [email protected]
  2. Include:
    • Your code
    • The report
    • Your evidence
    • Why it should stay
  3. Human review: 24-48 hours
  4. Decision: Final decision emailed

We're fair but firm.

Preventing Reports

Best defense is quality:

1. Test Everything

Before publishing:

  • βœ… Test the link
  • βœ… Verify the code works
  • βœ… Check discount applies correctly
  • βœ… Confirm restrictions
  • βœ… Verify expiration date

5 minutes of testing prevents hours of fixing reports!

2. Be Accurate

In descriptions:

  • Exact discount amount
  • All restrictions listed
  • Correct expiration
  • Clear instructions
  • Honest representation

Accuracy = trust = fewer reports.

3. Update Regularly

Maintenance schedule:

  • Weekly: Review all codes
  • Monthly: Test all links
  • Quarterly: Update descriptions
  • Always: Fix expired codes

Keep everything fresh!

4. Clear Instructions

Include:

  • How to apply
  • What's excluded
  • Minimum requirements
  • Special steps

Reduces confusion = fewer reports.

5. Monitor Performance

Watch for:

  • Low conversion (might be broken)
  • No clicks (possibly expired)
  • Sudden drops (check it!)
  • User feedback

Catch issues before reports.

Report Analytics (Pro)

Track your report history:

What You Can See

Dashboard shows:

  • Total reports received
  • Report types breakdown
  • Resolution status
  • Average response time

Per-Code:

  • Reports on each code
  • Common issues
  • Fix history
  • Quality score

Using Report Data

Identify patterns:

  • Same issue recurring?
  • Specific codes problematic?
  • Certain brands?
  • Time-based trends?

Improve systematically:

  • Address root causes
  • Update processes
  • Better quality control
  • Prevent future reports

Best Practices Summary

Quick reference:

βœ… DO This

  • Respond to reports quickly
  • Fix legitimate issues
  • Thank reporters
  • Learn from feedback
  • Test before publishing
  • Update regularly
  • Be accurate and honest
  • Follow content rules

❌ DON'T Do This

  • Ignore reports
  • Argue with reporters
  • Leave broken codes up
  • Make excuses
  • Repost bad content
  • Blame others
  • Get defensive
  • Violate guidelines repeatedly

Getting Help

Report-related questions:

General Help:

  • πŸ“§ Email: [email protected]
  • πŸ’¬ Subject: "Report on Code [CODE]"
  • ⏰ Response: 24-48 hours

Urgent Issues:

  • ⚠️ False takedown
  • ⚠️ Malicious reporting
  • ⚠️ System errors
  • ⚠️ Urgent corrections

Include:

  • Your code details
  • Report information
  • Evidence/screenshots
  • Your side of story

Community Standards

We're all in this together:

Be a Good Creator

  • Maintain high quality
  • Update promptly
  • Help the community
  • Report issues you see
  • Follow the rules
  • Stay professional

Be a Good Reporter

(For shoppers reading this)

  • Report real issues only
  • Provide helpful details
  • Be constructive
  • Give creators time to fix
  • Don't abuse the system

Quality benefits everyone!

Next Steps

Maintain your quality:

High quality = fewer reports = more success! ✨