Postbacks are used to transfer information about events (registration, sale, resale) from your platform (for example, an affiliate system or tracker) to the MVP Project system.

✅ GENERAL PRINCIPLES

All three postbacks are sent using the GET method and pass parameters via the URL.

The parameters must be substituted into the corresponding fields on your platform side when the corresponding action occurs:

• registration - when the user registered;
• sale - when the user made the first payment;
• repeat payment - when the user made the second and subsequent payments.

To create custom goals, go to the “Goals” section

🔹 1. Postback for registration

https://thedinator.com/api/v1/api_send_postback/?clickid={sub_id1}&goal=reg&playerid={playerid}&ow=0

Explanation of parameters:

• clickid — click ID, transferred from the tracker or affiliate. Used to link the user to the traffic source.
• goal=reg — event type. In this case, registration .
• playerid — unique ID of the player (buyer) on your side.
• ow — ID of your account in the MVP Project system.

When to call:

Immediately after a user has successfully registered on your platform.

🔹 2. Postback for the first sale (deposit)

https://thedinator.com/api/v1/api_send_postback/?clickid={sub_id1}&goal=dep&sum={sum}&playerid={playerid}&ow=0

Explanation of parameters:

• clickid — click ID, the same as during registration.
• goal=dep — event type. In this case, deposit (first payment).
• sum — deposit (sale) amount.
• playerid — player ID.
• ow — ID of your account in the MVP Project system.

When to call:

Upon the user's first successful deposit.

🔹 3. Postback for resale (deposit)

https://thedinator.com/api/v1/api_send_postback/?clickid={sub_id1}&goal=redep&sum={revenue}&sumrd={sumrd}&playerid={custom1}&ow=0

Explanation of parameters:

• clickid — the same click ID passed from the tracker.
• goal=redep — event type. In this case, a repeat deposit .
• sum={revenue} — the amount of the re-deposit (sale).
• playerid — player ID, possibly another format (if custom1 in the system differs from playerid ).
• ow — ID of your account in the MVP Project system.

When to call:

For each repeated deposit of the player (second and further).

🔧 HOW TO SET UP

Collect the required data on the user's first visit:

• Save clickID on your platform (affiliate program) side

Connect postbacks to your events:

• After registration → call postback #1.
• After the first deposit → call postback #2.
• For repeated deposits → call postback #3.

Make sure variables are dynamically substituted:

• {sub_id1} , {playerid} , {sum} , {revenue} , {sumrd} , {custom1} are variables from your system and may have different names. It is better to check with your offer support. In production, they should not remain in curly brackets.

Logging/Monitoring:

• All postbacks that come to MVP Project are shown in the postback logs of a specific spot