Test your setup

Once the foundation is in place, run a quick test to make sure tracking, conversions, and commissions work exactly as expected.

1

Add the first affiliate

Before launching publicly, test your workflow by adding your first affiliate. You can share your sign-up link, add affiliates manually, or import affiliates in bulk. It’s perfectly fine to add yourself for testing purposes.

👉 Add the affiliates to your program

2

Get the first conversion

Test that tracking works correctly:

1. Click your affiliate link

2. Place a test order in your store

3. Confirm the order appears in your BixGrow dashboard with the correct commission.

After confirming everything is working smoothly, it’s time to share your program, attract affiliates, and start growing your referral sales.

👉 Track clicks, orders, commissions and more

Next steps

Promote your affiliate program

Attract quality affiliates by sharing your program across your store, customer touchpoints, and marketing channels.

FAQs

What is GitBook?

GitBook is a collaborative, AI-native documentation platform where teams can create, review, and publish branded docs as websites. Docs sites hosted on GitBook can offer a built-in AI Assistant and connect to other AI tools via MCP.

You can edit content using the advanced visual editor using Markdown, sync your docs with a Git repository for a docs as code workflow — or use a combination of the two. However your team chooses to use GitBook, you’ll use a Git-like branching workflow with a full version history, which protects your primary content while encouraging collaboration and feedback across your entire team.

How do you publish documentation with GitBook?

Publishing in GitBook is a simple process once your content is ready to go live:

Create a new docs site (or open an existing one) and choose the content you want to publish.Choose your site audience. You can publish to everyone with the public setting, or limit the audience with share links or authenticated access.(Optional) Customize the branding, domain, and theme using the built-in options.Click Publish. Congrats — your docs are live! You can add more spaces later as site sections or variants.

To find out more, check out our Quickstart guide above, or read the complete guide to creating and publishing documentation in GitBook.

Is GitBook open source?

GitBook itself is not open source. However, GitBook’s published docs platform — which is used to host and display documentation on a docs site — is open source. You can visit the repository to see the code and submit changes for review.

While GitBook itself isn’t open source, open source projects can publish documentation on GitBook for free. Teams can sign up for the Community plan and publish content using a Sponsored site plan, both of which are free to qualifying teams.

What’s the difference between a site and a space in GitBook?

In GitBook, a docs site is your overall documentation hub, hosting all content accessible to your audience and featuring customizable options like theme and domain.

Each site contains one or more spaces, which serve as individual sections within the site, organizing related content for better modularity and ease of management. Spaces let you focus your collaboration on specific topics, and you can combine multiple spaces on a single site to build structure or enable options like translations (for localized documentation) or multi-product support.

What are the differences between GitBook’s visual editor and Git Sync?

GitBook offers two main methods for editing documentation — the visual editor and Git Sync. The visual editor is an advanced, block-based editor that allows you to create and modify content directly within GitBook using a traditional user interface that includes Markdown support. It's ideal for those who prefer a more intuitive, hands-on editing experience without directly dealing with code.

Git Sync integrates your documentation workflow with a Git repository, enabling a ‘docs as code’ approach. This option is ideal for developers and teams who prefer managing documentation alongside their codebase, using familiar Git commands and workflows.

Your team can choose one of these workflows, or use a combination of them both. And whichever method they prefer, editing follows a consistent, Git-like branching workflow with a full version history and content review process. This doesn’t just promote collaboration and quality across your docs — it also safeguards primary content from accidental edits.