Ambassador and Installer Dashboard: Codes, Tracking, and Stripe Payouts

Once your ambassador or installer role is approved, the dashboard is where the program's working parts live. It holds your unique discount code and share link, tracks every click and conversion they generate, summarizes earnings month over month, and connects to Stripe so payouts land in your bank account on schedule. This post walks through each piece, the right way to use it, and how to finish your Stripe setup so payouts actually start flowing.

You'll find the dashboard under Profile → Ambassador — that tab covers both ambassadors and installers. If the tab isn't there yet, your role hasn't been approved — see the migration thread for how to claim it.

Every approved ambassador and installer gets two assets tied to the same identity:

• A discount code customers can type at checkout on the Lone Peak Overland store
• A share link at /r/<your-code> that redirects to the store with the code already applied

How to use them:

1. In person or on a call, give out the discount code by itself. Customers remember a short string. The store will associate the order with you when they enter it at checkout.
2. Online or in any post, story, bio, or message, share the link. The redirect logs the click, drops the code into the cart automatically, and removes the "did they remember to type it" friction.
3. Use the link anywhere a URL works — Instagram bio, YouTube descriptions, an email signature, a Trailhead build post, a sticker QR code on your camper.

Both routes feed the same dashboard, so you don't have to pick one. Most people lead with the link online and fall back to the code when they're talking to someone face to face.

Watch for limited-time promo codes. From time to time, Lone Peak will issue special offer codes to ambassadors and installers — a different code from your primary, tied to a specific promotion or deal. These are code-only (no share link attached), but they track and attribute back to you the same way your primary code does. When one drops, share it however you normally share your primary code and the conversions will roll into your dashboard alongside everything else. Keep an eye on your notifications and the announcements channel so you don't miss them.

The dashboard tracks every visit to your share link and every order that gets attributed to your code. The two main views worth knowing:

• Click counts show how often your link is pulling people through to the store. Watch this when you publish new content — a YouTube video, a forum thread, an Instagram reel — to see what's driving traffic.
• Monthly trends plot clicks, conversions, and earnings over time. Use it to compare months side by side, spot seasonal patterns (rallies, holidays, new product launches), and identify which platforms or pieces of content punched above their weight.

A practical rhythm: check trends once a week, not every day. Day-to-day numbers are noisy. Weekly and monthly cuts tell you whether what you're putting out is actually moving the needle.

Earnings move through three states in the dashboard:

• Pending — orders that have been attributed to you but haven't cleared the confirmation window yet. Returns, refunds, and chargebacks can still affect this bucket, so it isn't payable yet.
• Approved — the previous month's earnings have been reviewed and locked in, but the payout hasn't gone out yet. Think of this as the queue between confirmation and Stripe. If your numbers in this bucket look right, you're set for the next cycle.
• Paid — statements covering everything that's been sent to your Stripe account. Each statement is a record you can keep for taxes and your own books.

Open any statement to see the orders behind the total — order IDs, dates, and amounts. If you spot something that doesn't look right, flag it while it's still in Pending or Approved — once it moves to Paid, reconciling it gets more involved.

Payouts run through Stripe Connect. Until you complete Stripe onboarding, earnings stack up as pending in your dashboard but nothing leaves the system. Plan to spend ten to fifteen minutes on this once, with the right paperwork next to you.

What you'll need before you start:

• A government-issued ID (driver's license or passport)
• Your legal name and date of birth
• Your Social Security number or EIN if you're set up as a business
• A bank account that can accept ACH deposits (routing number and account number)
• A phone number Stripe can verify

How to connect:

1. In the dashboard, open the Payouts section and tap Set Up Stripe (or Connect with Stripe — the exact label depends on whether you've started before)
2. Stripe opens its hosted onboarding flow in a new window. Sign in with an existing Stripe account or create one with the same email you use on Trailhead
3. Walk through the prompts — identity verification, bank account, tax form. Stripe is doing the lift here; Trailhead just hands off and receives the confirmation when you're done
4. Return to Trailhead. The Payouts section flips from "Setup Required" to your connected account and payout schedule

After that, paid statements move to your bank automatically on Stripe's schedule. You can update your bank info or tax details any time by reopening the Payouts section and tapping Manage in Stripe.

If Stripe asks for additional verification later — a clearer photo of an ID, a utility bill, an EIN letter — they'll email you. Don't ignore those emails. Unanswered verification requests pause payouts.

A few patterns cover most of what comes up:

• Payouts not arriving. Open the Payouts section and check the connection status. If Stripe is showing a pending verification or a payment method issue, resolve it inside Stripe and the next cycle should clear.
• Code or link not converting. Test the share link from a private/incognito browser. You should land on the store with your code visible in the cart. If not, DM an admin with the link you're using.
• Numbers don't match what you're seeing on social platforms. Click counts on the share link reflect redirects, not impressions. A post can rack up views without anyone tapping through. That's normal.
• A statement looks wrong. Open it, identify the specific line item, and DM an admin with the order ID. Don't wait for the next cycle — reconciliation is easier when the order is fresh.

For anything not covered here, use the Report a Bug button on your Profile page so it routes to the team with your device and browser context attached. Post in this thread if it's a question other ambassadors or installers would benefit from seeing answered.