Ship It · student guide

Your product is the submission.

First, submit your live product and connect GitHub. Next, connect analytics and payments. One project. Two receipts.

One teammate submits for the team.

One project per team

Choose one teammate to submit and connect the repository, using the same college email they used on Shipyard. You do not need to add teammates again on Shipped. Instructors will match your submission to your existing Shipyard team later. Do not create duplicate projects or submissions for the same team.

Open shipped.money/submit

Click Start submission and sign in with your college email. Open the sign-in link in the same browser. On your first visit, create your short profile, then continue. Choose an existing project or enter your product name and live website address.

Use your own domain

Submit an HTTPS custom domain such as myproduct.in or app.myproduct.in. A university-assigned custom domain is also fine. Default addresses ending in .lovable.app, .vercel.app or similar hosting domains do not count. You may still build with Lovable and host on Vercel; connect your domain in the host’s domain settings. Wait for DNS and HTTPS to work before submitting.

Connect the product’s GitHub repository

Paste the repository link. Click Create read-only GitHub key. GitHub opens with the name and read permissions filled in. Select Only select repositories, choose this product’s repository, and generate the token. Copy the key into the protected field on Shipped. Leave Contents, Metadata and Pull requests on Read-only. The repository owner should do this step; private repositories are supported. Organisation repositories may need owner approval.

Tell us what to test, then submit

Describe one core task and the result to expect, such as Create an invoice and download its PDF. Test it yourself in a private/incognito browser window. If login is needed, explain how the instructor can request an invitation. Do not put passwords, API keys or customer data in these notes. Submitting publishes your Shipped.money project and connected progress, including search, analytics and payment totals. Credentials and code-review findings stay private. Confirm the checkbox and click Submit working product.

Check your submission

You should see Working product · submission received and the date. Your submission time is saved before website or GitHub checks finish. Check the status of each requirement. A pending connection still needs fixing; a reachable website still needs instructor review of its core task. If your app link or repository changes, use Update or finish this submission. Your earlier submission remains on record.

Save your analytics and payment setup

Open shipped.money/app/submit using your college email. Click Continue submission on your app card and scroll to Your connections. Use Set up Clarity and Set up Search Console, then Choose payment provider. The full Clarity walkthrough is at shipped.money/submit/clarity. The full Search Console walkthrough is at shipped.money/submit/search-console and included in this download. For PhonePe, select PhonePe in the payment-provider dropdown and describe your checkout and setup status for review. Return to this same page, confirm the checkbox, and click Submit tracking setup. You should see Tracking submission received and the date. Once submitted, the page checks your connections automatically; you do not need to resubmit when a connection recovers. You do not need these connections for submission 1.

Submission 2: connect, then submit

Use your existing project. Connect each service, return to Course submissions, and click Submit tracking setup. Your final proof of submission is the dated tracking receipt; connecting one service is not the final step.

Microsoft Clarity: full step-by-step guide →Google Search Console: full step-by-step guide →

Microsoft Clarity: follow shipped.money/submit/clarity. Install the tracking script on your published app, verify a visit in its dashboard, then open that same project → Settings → Data Export → Generate new API token. Only project admins can generate it. Paste the whole token in Shipped’s private Clarity field, not the project ID or script. Connecting a token alone does not install the tracker.
PostHog is optional. If you already use it, connect your numeric project ID, matching US/EU region and a project-restricted personal API key with Query Read permission. The public phc_ capture token cannot read reports. This connection is not required for your course submission.
Google Search Console: follow the complete walkthrough at shipped.money/submit/search-console. It explains Domain versus URL-prefix verification, the MU organization choice, read-only service-account access, the exact property value and JSON field, and the receipt. Search Console measures Google Search activity, not all website visits. Zero traffic is fine; a failed connection still needs fixing.
Payments: connect Dodo or the supported provider you use, using the least-privileged credential offered. Use the live account, not a sandbox/test key. Successful connection is separate from a real customer payment; you do not need to make a payment to yourself.
PhonePe: select PhonePe in the tracking submission form. Explain where checkout is on your product and what works or is pending, including merchant approval. You can submit while setup is in progress. These details go to your instructor; Shipped does not yet import PhonePe transactions or include them in verified revenue leaderboards. Do not paste PhonePe credentials into the notes.
Paste each key only into its protected connection field. Never send keys in WhatsApp, email, GitHub commits, screenshots or submission notes.

If you get stuck

Check spam for sign-in emails and use a fresh link in the same browser. For GitHub organisation approval, ask the repository owner. For domain errors, check your host’s domain settings and HTTPS. Share your receipt ID and the error with your instructor; never share a key.

There is no second final-product submission in Shipyard. Follow separate instructions for the earlier idea and spec checkpoints.

GitHub setup checked against GitHub’s token documentation on 16 October 2026.

Start submission →