Project: Analysis and simulation of fake conversions in Scaleo (CPA tracker)

Data Parsing, Web Programming — incorrectly specified categories?

Project translated automatically. Log in or register, to view the original

🎯 Goal:

Understand what data needs to be transmitted to the CPA system Scaleo so that it displays events such as "registration" or "deposit" for a specific offer.

🔍 Tasks:

Analyze how Scaleo receives events from the integrated product.
- There is a click link of the type:
  https://supabets.scaletrk.com/click?o=1&a=9317&c=43
- Check whether events are sent directly from the site or through a third-party "bridge" (Keitaro, another backend).
Extract the postback endpoint and parameters accepted by Scaleo.
- Find the structure of the link for event tracking (event=registration, event=deposit).
- Example parameters: click_id, event, amount, currency, sub1, status, etc.
Determine the mandatory fields for the conversion trigger.
- Which parameters are critical for registering the event?
Perform a test simulation of fake events.
- Create a simple script (or Postman instruction) that allows manually or automatically:
  - send a "registration" event;
  - send a "deposit" event;
  - check if they appear in Scaleo statistics.

⚙️ Infrastructure:

Tracker: Scaleo.
Offer link: https://supabets.scaletrk.com/click?o=1&a=9317&c=43
If needed — access to Keitaro and examples of click_id.

✅ Expected result:

You have identified where the real conversion is sent.
An example postback URL and a list of mandatory parameters are obtained.
It is possible to simulate an event manually via GET/POST request.
(Optional) There is a script or .sh/.py file for mass event generation.

🧰 Bonus if:

You can obtain the conversion token or bypass access restrictions to postback in Scaleo.
You have experience with Keitaro or bypass methods (API proxies, webhook traps).

Proposals 2 Discussions 5