Skip to main content

CCL Online


Task Setup Guide for CCL Online

On the tasks page select create tasks.

Select CCL Online from the drop down.


Product ID/PID

You can find a PID on CCL Online by locating the URL of your desired product for example.

You can easily locate the PID by looking just after product/ for example the PID would be 190107 you can enter this into the "Product PID" section in your task creation.


Create a task

To create a task, click the green "Add Task" button in the bottom left. 
Here you'll have the following options:


Select your profile here.

CCL Online is strict when it comes to 1 per customer on limited items such as GPUs. 

Checkout Mode

Select Normal here. 

Payment Mode

There is one type of payment mode available. This is Cart Hold.

Cart Hold adds the product to cart and sends a webhook with a link to the cart. (You will have 30 minutes to checkout before the item gets released)

You must have the Carnage Bot extension installed in order successfully access the cart link.

Proxy List

Here you want to select the proxies that you would like to use. We recommend that you use a mixture of datacentre and sticky residential proxies to ensure the best likely-hood of success. 

We would not recommend that you run any more than two tasks proxyless.

We recommend a proxy to task ratio of 3:1 this is to help you avoid getting your proxies banned.


Enter the amount you would like to purchase. (limited items will be limited to 1 per person)



Below we recommend to use the following delays:

Initial Item(s) release delays to use - 1,000

Restock delays to use - 15,000

Please checkout these two pages that cover Monitor tasks and Task Timers.

If you are using proxies, you may want to increase/decrease the delays depending on your setup.

Example Task Setup For CCL Online

Correct Statuses For CCL Online Tasks

  • [200] Product OOS - This means the item is OOS.

Incorrect Statuses For CCL Online Tasks

  • 429 and 403 Error - Means your proxies have been flagged by cloudflare. Please try to use different proxies to fix this.



Powered by Zendesk