How to Create a Listing

Category

Choose the category based on the primary thing the customer receives, not the support method, delivery method, result, or extra items included.

Images (Optional)

Images can make the offer easier to understand, but they should support the listing, not replace the listing fields.

• Use a 16:9 landscape image. The existing marketplace guidance uses 1280 × 720 px.
• Keep the file reasonably small. The existing guidance recommends under 300KB where practical.
• Keep important text and details away from the edges so cropping does not hide them.
• Use the image to reinforce the title, product, bonus type, or main customer benefit.

Title

The title should make it obvious what useful action, setup, access, support, or progress the bonus gives the customer.

• Use 1–2 main elements only.
• Include the product name when it improves clarity.
• Keep it short enough to scan quickly.
• Do not use “free”, “bonus”, “bundle”, prices, fake value claims, guarantees, or unsupported results.

Required Product

Enter the third-party product the customer must sign up for, subscribe to, upgrade to, or buy to qualify for your bonus.

Example: GoHighLevel

BagABonus does not sell the required product. The customer purchases it externally through your affiliate link.

Purchase Requirements

Explain the exact purchase path the customer must complete to qualify.

• State the required plan or tier.
• State the required billing term when it matters.
• Explain any trial or conversion condition.
• Use one clear affiliate path for the listing.

Separate listings are usually safer when the plan, billing term, affiliate link, proof requirement, bonus package, delivery, support, or claim conditions differ. Do not use “any paid plan” as the normal default.

Example: A new customer must purchase the GoHighLevel Starter plan on monthly billing through my affiliate link.

Affiliate Link

Add the exact affiliate link the customer must use for this listing’s qualifying purchase path.

• Use the correct link for the plan or offer shown in this listing.
• Do not put multiple affiliate links into one normal listing.
• If a different link creates a materially different purchase path or bonus package, create a separate listing.

Product Website

Add the official website for the required product, not your affiliate link.

Example: https://www.gohighlevel.com/

Use current official product information where possible. Do not present uncertain plan names, prices, trial lengths, or promotions as confirmed.

Bonus Summary

Give a short, scannable explanation of what the customer receives. This is a compressed overview, not the full description.

• Focus on the main bonus value and the most useful supporting deliverables.
• Use plain, direct wording.
• Do not overload it with proof rules, claim steps, every limitation, or Premium Add-On details.

Example: A ready-to-copy GoHighLevel funnel snapshot with landing, thank-you, booking, and confirmation pages, plus a basic follow-up automation and a walkthrough showing what to customize before using it.

Support Included (Optional)

Select only the support the customer genuinely receives with the free bonus. The form uses fixed support options.

• 1-on-1 Call
• Chat Support
• Private Community Support
• Group Call
• Email Support
• Technical Setup Support

Be precise: Do not imply live, ongoing, or unlimited support when you only provide one reply, one call, one review, or message-only support. State meaningful limits clearly.

How The Customer Gets Access (Optional)

Choose the access type the customer actually receives, then explain the exact access details and where the link, file, folder, call details, code, or instructions are provided.

• Platform Access: use when the customer accesses the bonus inside a platform, account, app, portal, software workspace, template link, base, snapshot, dashboard, or similar environment. This also includes setup or implementation completed by the creator directly inside the customer’s account or platform when the completed result remains there for the customer to use.
• Shared Folder: Google Drive, Dropbox, OneDrive, or another resource folder.
• Direct Download: PDF, ZIP, checklist, spreadsheet, worksheet, template file, or other downloadable file.
• Community Access: private group, forum, Discord, Skool, Slack, or member environment.
• Message / Email Delivery: the bonus itself is delivered directly in the message or email, such as a coupon code, license key, short written note, or simple instruction.
• Live Call: live review, strategy session, onboarding, walkthrough, or group session.
• Recorded Training: recorded video, audio, course access, walkthroughs, lessons, or training material.
• Physical Shipment: a physical item delivered by post or another real-world delivery method.

If the bonus uses more than one access method, add one row per access type.

Delivery Time (Optional)

Enter the normal timeframe in which you expect to deliver the bonus after the customer has completed the required steps and you have what you need to deliver it.

Example: Within 5 business days after I receive the required information and account access.

Use this field for the normal promised delivery timeframe. Repeat timing elsewhere only when it materially clarifies claim, access, or Premium Add-On conditions.

How To Claim (Optional)

Turn the qualification, proof, verification, and delivery path into a clear sequence the customer can follow.

Structure: Use 2–5 numbered steps in the order the customer should complete them. Do not merely repeat Purchase Requirements as a paragraph.

1. Use my affiliate link on this listing and purchase the required plan.
2. Return to BagABonus and send me the account email, plan purchased, and required proof through BagABonus Messages.
3. I will review the proof and confirm whether the purchase qualifies.
4. After approval, I will send or arrange access using the delivery method shown in this listing.

Use natural “you” and “I/my” wording where appropriate. If the claim path depends on manual review, say so clearly.

How It Helps The Customer (Optional)

Explain the practical difference the bonus makes. This field is for decision support, not another description of the deliverables.

• What confusion does it reduce?
• What setup or implementation task does it make easier?
• What mistake may it help the customer avoid?
• What next step does it make clearer?

Example: Gives you a clearer starting point for your GoHighLevel setup so you can see what to configure first instead of guessing.

Keep the benefit tied to what you actually provide. Avoid guaranteed outcome claims.

Best For (Optional)

Describe which type of customer the bonus is most useful for, based on their situation, skill level, product stage, support need, or use case.

• Best for GoHighLevel beginners who want setup guidance before building their first funnel.
• Best for creators who already use Systeme.io but need a clearer email automation setup.

Avoid broad phrases such as “everyone”, “all businesses”, or “anyone who wants success”.

Bonus Breakdown

This is the detailed explanation of the free bonus. It should clearly show what is included, why it is useful, and anything important the customer needs to know.

• One main bonus: name or describe the main bonus, then use Why It Matters: and Includes: to explain the meaningful components.
• Several distinct bonuses: use one overall “What You Get:” summary, then number and name each distinct bonus. Give each its own Why It Matters: and Includes:.
• Use one overall Important: section at the bottom only when shared requirements, limits, exclusions, or prerequisites genuinely help the customer.

Do not automatically add monetary values. If you choose to show a real standalone value or credible estimate, keep it supportable and clearly separate it from what the customer pays.

Do not include Premium Add-On deliverables inside the free Bonus Breakdown.

Offer Early Bonus Access

Early Bonus Access applies only when the required product has a trial and the creator would otherwise delay delivery of the free bonus until the customer reaches the normal qualifying paid point, such as becoming a paying subscriber after the trial.

• Use it when the customer can benefit from receiving the bonus during the trial and early delivery creates practical value, while the creator would otherwise wait for paid continuation or proof before delivering it.
• Do not use it when the product has no trial, when the creator already delivers the bonus during the trial without a separate early-access payment, or when early delivery provides no practical benefit.

Simple rule: Early Bonus Access is a timing and trust mechanism. It is not a Premium Add-On and must not turn the free bonus into a paid bonus.

Early Bonus Access Fee (Optional)

Set the refundable early-access amount based mainly on what you genuinely risk by delivering the bonus early.

• Consider non-recoverable labour, direct costs, customization, booked call time, or work that cannot be reused.
• Reusable files with little marginal delivery cost usually justify a lower fee or no Early Bonus Access.
• Do not use the fee as the “price” of the free bonus or as a disguised Premium Add-On.

Offer Premium Add-On

Choose whether to offer an optional paid upgrade alongside the free bonus. It can provide deeper implementation, customization, extended support, priority access, review, or done-for-you work.

Premium Add-On Fee (Optional)

Enter the actual price the customer pays for the optional paid upgrade only.

• Do not include the required third-party product cost.
• Make the paid scope clear enough that the fee is understandable.
• For a defined 3, 6, or 12-month support term, show the full upfront amount covering that complete term.
• Do not describe the current Premium Add-On as recurring monthly billing, a subscription, instalments, or automatic renewal.

Premium Add-On Title (Optional)

Write a short, clear name for the optional paid upgrade. The title should tell the customer what they are paying for.

• Done-For-You GoHighLevel Funnel Setup
• 60-Minute Systeme.io Funnel Review Call
• 6 Months of Implementation Support

Avoid vague titles such as “Premium Upgrade”, “VIP Option”, or “Advanced Package” unless the title also explains the actual service.

Premium Add-On Benefit (Optional)

Write a short, outcome-focused line explaining the practical advantage of buying the optional upgrade.

Example: Supports customization so the free resources fit your business or funnel instead of leaving you to adapt everything alone.

Keep the benefit tied to what you actually deliver. Do not imply the customer must buy the Premium Add-On to receive meaningful value from the free bonus.

Premium Add-On Description (Optional)

Use this field for the full details of the paid upgrade. Keep it separate from the free Bonus Summary and Bonus Breakdown.

If the Premium Add-On covers a fixed support period, make the exact duration, support channel, limits, start point, end point, and any requirement to maintain the qualifying product subscription clear.

Ready to shape your listing?