Pre-configured bet examples
This page provides practical examples of how to set up pre-configured bets that can be triggered manually from your dashboard. These examples allow you to prepare your betting strategy in advance and execute bets at the optimal moment.
Example 1: Manual Trigger Bets
Scenario: "I want to have all my bets ready on the dashboard, then I can just press 'trigger' when I want the bets to be placed."
This approach allows you to prepare your betting strategy in advance and execute bets at the exact moment you choose, giving you complete control over the timing.
Configuration Steps:
Select Trigger: Choose "Schedule - Manual" from the trigger options
Complete bet configuration: Fill in all other bet details (competition, runner, stakes, etc.)
Create the bet: The bet will be created but not immediately placed
How It Works:
When you select Manual as your trigger option:
The bet will appear on your My Bets dashboard after it is created
The bet status will show as "Pending Manual Trigger"
You can review all bet details before execution
Simply press the "Trigger" button when you're ready to place the bet
The bet will then be sent to your selected bookmaker accounts
Benefits:
Timing Control: Execute bets at the exact moment you choose
Review Before Execution: Double-check all bet details before placing
Batch Execution: Trigger multiple prepared bets simultaneously
Example Configuration:
**Trigger: Schedule**
**Type: Manual**
Bet Type: Fixed Wager
Competition: FLEMINGTON
Race Number: 5
Market: Fixed Win
Runner: 3
Stake: $20
Target Bookies: All ActiveOnce created, this bet will appear in your dashboard where you can trigger it when ready.
Tips for Manual Trigger Bets:
Prepare in Advance: Set up your bets during quieter periods when you have time to think
Monitor Odds: Keep an eye on odds movements before triggering
Check Account Status: Ensure your target bookmaker accounts are active before triggering
Batch Processing: Create multiple bets and trigger them in sequence for complex strategies
Review Sessions: Always verify your target sessions are running before execution
Last updated