Postback goals allow you to send custom events (e.g. withdrawal amount, turnover amount, number of transactions, etc.) and display this information in the client card and statistics .

By default, three goals are available, which are inserted into the postback link and record information in the corresponding fields in the client card in the messenger and in the statistics:
reg - Registration

dep - First sale (Deposit).

redep - Repeated sale (Repeat deposit).

How to add a new goal?

To add a new goal, click the “Add goal” button and fill in the required fields.

Name

The name of the goal for your convenience and how it will be displayed in statistics.

Token

The target name in the postback. For example, if we have a payout token, the postback link will look like this:

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

Read more about postbacks in the article “ Setting up postbacks for deals ”

Google Analitycs, Facebook, Tik-tok, Yandex

Event name in ad networks. All postbacks will be sent to the ad network whose pixel is configured for the spot, and you can subsequently optimize campaigns for these events.

External postback
An external postback allows you to forward events to your tracker.

Available macros:
{action} - event name (reg, dep, redep, etc.).
{user_id} - Telegram user ID.
{username} is the Telegram user's username.
{name} - Telegram user name.
{click_id} - ClickID of the lead in our service for our landing pages.
{sum} - deposit/re-deposit amount.
{cl_id} - ClickID of the lead in our service for your tracker (or other custom landing pages).
{advert__pixel} - Facebook / TikTok / other source pixel ID.
{advert__campaign_id} - Advertising campaign ID.
{advert__adset_id} - Ad group ID (ad set).
{advert__ad_id} - ID of a specific ad.
{advert__campaign_name} - Name of the advertising campaign.
{advert__adset_name} - Name of the ad group (ad set).
{advert__ad_name} - Ad name.
{advert__placement} - Placement location (location of ad display).
{advert__site_source_name} - Traffic source (e.g. Facebook, Instagram, etc.).
{geo} - transfer of data about the lead's GEO.
{advert__landing_id} - Landing page ID.
{params__PASSANYVALUEFROMPARAMSHERE} - you can pass any value from the parameters we're writing. Example: uid {params__uid}.

Display in statistics

Enables displaying information about incoming postbacks in statistics . If you select "Yes," two checkboxes will appear: "Show sum of values" and "Show count of values." Selecting these will add two display columns to the statistics table editor (in our example, they will be called "Summary" and "Count" outputs).

Create a system message

If you use a CRM ( available if CRM is enabled in the spot settings ), you can send a system message to the messenger about an incoming postback.

Available macros:

{sum} - the number received in the sum parameter in the postback

{player_id} - Client ID received in the playerid parameter

{manager} - a unique employee ID within the MVP system, used to link system messages to CRM.