Skip to main content
Athletes use MOGL to create an account, complete their NIL-ready profile, discover and apply to jobs, confirm availability after hire, submit proof of work, and maintain the social connections that power reporting.

​
1. Sign up

Athlete signup is step-by-step across web and iOS. The updated signup work removed older friction, aligned the web and iOS experiences, and instruments each step so funnel issues can be measured. For API-based onboarding, start with the Quickstart and the athlete registration path.

​
2. Complete profile

An athlete profile is considered ready for compliance when required identity, school, sport, citizenship, social, and profile-photo data are present. Profile completion also powers referral payout eligibility and athlete readiness signals. Profile-ready fields include:
  • first and last name;
  • verified contact information;
  • school;
  • date of birth;
  • gender;
  • sport;
  • citizenship status;
  • social media connection when required for deal application;
  • profile photo, often collected during job application.
The profile completion percentage used in athlete-facing experiences weights fields such as photo, name, contact number, school, DOB, height, sport, bio, email, and apparel sizes. Treat the percentage as a user-facing progress indicator and the compliance-ready state as the operational readiness check.

​
3. Apply to a deal

Athletes discover jobs in web or iOS job views. Updated signup and filter work improved job cards, aligned filters across web and iOS, and hides jobs that are no longer hiring or already applied to. Application readiness should check:
  • required profile fields;
  • required social media connection for the deliverable type;
  • eligibility and match constraints;
  • screening questions when configured by the brand.
When deliverable types require a specific social platform, the athlete must link the relevant account before applying and must later submit proof of work that matches the requirement.

​
4. Confirm availability once hired

After hire, the athlete is prompted to confirm availability. This closes the gap where an athlete applied earlier but may no longer be available. The athlete can:
  1. confirm they are still available;
  2. say they cannot complete the deal;
  3. request a new due date.
If an athlete submits proof of work before explicitly confirming availability, the system can treat the deal as auto-confirmed for the athlete side. If a deal becomes voided, the confirmation modal should no longer require action.

​
5. Execute deliverables and post proof of work

Deliverables can include platform-specific proof requirements. Deliverable Types v2 ties deliverable types to social media restrictions, so a required Instagram Reel, TikTok video, X post, or other deliverable can require a valid matching link. Athletes should understand:
  • when a deliverable opens for submission;
  • whether the deliverable has a beginning date;
  • what proof-of-work format is valid;
  • what happens if proof is rejected;
  • how long the deliverable remains open after the due date;
  • when a deliverable becomes voided.

​
6. Support reporting and performance measurement

Campaign reporting depends on connected social media data. OAuth-linked Instagram, TikTok, and X accounts can power impression, engagement, audience, and content-preview data. Athletes should know that:
  • social data refreshes periodically;
  • expired or missing social permissions can block reporting;
  • data connection errors may trigger notifications;
  • athletes may need to reconnect accounts or fix a submitted link to keep performance reporting accurate.