Finding & Inviting Creators

Use smart matching to find eligible creators and invite them to your campaigns.

Instead of waiting for creators to find your campaign, you can proactively find and invite the right creators.

Smart Creator Matching

Click the sparkles icon in the campaign action bar to open the Matching panel. Gamosy analyzes your campaign requirements and finds creators who:

  • Meet your platform follower/view minimums
  • Have content in relevant game genres
  • Have strong Trust Scores and CCR ratings
  • Have availability (not currently overcommitted)

Match Scores

Each recommended creator shows a match score indicating how well they fit your campaign. Higher scores mean better alignment between your requirements and the creator's profile.

Match scores consider:

  • Platform eligibility — Does the creator meet your minimums?
  • Creator tier — Higher-tier creators score higher
  • Engagement quality — Views-to-follower ratio
  • Genre relevance — Does the creator cover similar games?
  • Reliability — Trust Score and CCR history

Batch Invite

Select multiple creators and invite them in one action:

  1. Check the boxes next to creators you want to invite
  2. Click Invite Selected (up to 20 at a time)
  3. All selected creators receive an invitation notification

Invited creators see your campaign in their Pending Invitations section and can accept directly, bypassing the normal application process.

Use the search combobox to find specific creators by name or platform username. This is useful when you already know who you want to invite.

Direct Invite Panel

Click the mail icon in the action bar to open the Invite panel. From here you can:

  • Search for specific creators
  • Send individual invitations
  • Track invitation status (pending, accepted, declined, expired)

Invitation Status

Track your invitations:

  • Pending — Creator hasn't responded yet
  • Accepted — Creator accepted and is now part of the campaign
  • Declined — Creator chose not to participate
  • Expired — Invitation was not responded to within the time window