Share and promote

Promote the brand through posts, videos, reviews, and social platforms to reach the audience.

1

Affiliate link is the most important tool.

Affiliates will find it at the top of the dashboard — simply copy and start sharing.

2

Share coupon code (if provided)

Many programs offer a personalised coupon code that the audience can apply when buying products from the store.

This helps affiliates drive conversions by giving their followers a discount.

Types of coupons affiliates may receive:

  • Static coupon (assigned by the merchant)

  • Anti-leak coupon (auto-applied when someone clicks their affiliate link).

👉 Learn more about Static coupon and Anti-leak coupon.

3

Promoting the brand

Create content that fits affiliates' style and audience.

This can include:

  • Product photos or unboxing videos

  • Tutorials or “how-to” posts

  • Honest reviews

  • Before/after photos

  • Recommendations in comment sections or communities

Affiliates use affiliate coupon or link in every post to make sure the referrals are tracked.

4

Grow the results

To earn even more:

  • Share regularly on social platforms

  • Repost top-performing content

  • Highlight discounts during sales

  • Share affiliate link in YouTube shorts, TikToks, email footers, and more

  • Ask the merchant for product collaborations or exclusive codes

Next steps

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.

Last updated