Integration Mixplat and VK Ads + Leadform (new account) (VK Advertising + Leadforms)

Connection in 5 minutes, 30 days on tests, try.

Accepted webhooks
Done actions
New clients

Try 30 days free

Free Turnkey setting, Instructions.

What data can be transmitted from: from_Service to: to_Service

Important: Please note that the presence of events and actions between the two services does not guarantee a solution your task - the available events and actions may not connect with each other in the way you need.

If you cannot independently determine whether these events and actions will be able to solve your problem; contact support or use the Full construction setting.

Events c Mixplat

Click on the name of the event to see the available fields.

API documentation — here.

Description

Not

Available fields
Id Name
payment_id Payment ID in the MIXPLAT system
merchant_payment_id Payment ID in the TSP
payment_method The payment method that was used for the payment
amount The amount of the payment in minor units (kopecks)
amount_user The amount actually paid by the payer, including the commission (if any), in minor units (kopecks)
amount_merchant The amount to be paid to the TSP, minus the commission (if any), in minor units (kopecks)
signature Signature. The principle of formation: md5 (payment_id+API_KEY)
test The sign of a test payment
currency Payment currency
date_created Date and time of payment creation (UTC+03:00). Format: YYYY-MM-DD HH:MM:SS
date_processed Date and time of payment processing (UTC+03:00). Format: YYYY-MM-DD HH:MM:SS
project_id The ID of the TSP project in MIXPLAT to which the payment relates
recurrent_id ID of the recurrent session
init_payment_id The value of the payment_id of the first recurring/subscription payment. Present only for recurring payments
merchant_init_payment_id The value of the merchant_payment_id from the first recurring/subscription payment. Present only for recurring payments.
merchant_campaign_id Campaign ID in TSP
merchant_data Arbitrary TSP data related to the payment
merchant_fields An array of additional information about the transaction
user_email Payer's email address
user_name Payer's name
user_phone Payer's phone number
user_comment User comment on the payment
user_account_id User ID in the TSP
user_country_code Two-character code of the payer's country according to the ISO 3166 standard
user_country The payer's country. There may be discrepancies when the VPN is connected
user_region_code The payer's region code according to the ISO 3166 standard
user_region Payer's region
utm_medium UTM tag that defines the type of traffic
utm_source UTM tag that identifies the traffic source
utm_campaign UTM tag that defines an advertising campaign
mobile Additional payment information specific to the "mobile" group of payment methods
card Additional payment information specific to the "card" group of payment methods
wallet Additional payment information specific to the "wallet" group of payment methods
bank Additional payment information specific to the "bank" group of payment methods
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
payment_id Payment ID in the MIXPLAT system
merchant_payment_id Payment ID in the TSP
payment_method The payment method that was used for the payment
amount The amount of the payment in minor units (kopecks)
amount_user The amount actually paid by the payer, including the commission (if any), in minor units (kopecks)
amount_merchant The amount to be paid to the TSP, minus the commission (if any), in minor units (kopecks)
signature Signature. The principle of formation: md5 (payment_id+API_KEY)
test The sign of a test payment
currency Payment currency
date_created Date and time of payment creation (UTC+03:00). Format: YYYY-MM-DD HH:MM:SS
date_processed Date and time of payment processing (UTC+03:00). Format: YYYY-MM-DD HH:MM:SS
project_id The ID of the TSP project in MIXPLAT to which the payment relates
recurrent_id ID of the recurrent session
init_payment_id The value of the payment_id of the first recurring/subscription payment. Present only for recurring payments
merchant_init_payment_id The value of the merchant_payment_id from the first recurring/subscription payment. Present only for recurring payments.
merchant_campaign_id Campaign ID in TSP
merchant_data Arbitrary TSP data related to the payment
merchant_fields An array of additional information about the transaction
user_email Payer's email address
user_name Payer's name
user_phone Payer's phone number
user_comment User comment on the payment
user_account_id User ID in the TSP
user_country_code Two-character code of the payer's country according to the ISO 3166 standard
user_country The payer's country. There may be discrepancies when the VPN is connected
user_region_code The payer's region code according to the ISO 3166 standard
user_region Payer's region
utm_medium UTM tag that defines the type of traffic
utm_source UTM tag that identifies the traffic source
utm_campaign UTM tag that defines an advertising campaign
mobile Additional payment information specific to the "mobile" group of payment methods
card Additional payment information specific to the "card" group of payment methods
wallet Additional payment information specific to the "wallet" group of payment methods
bank Additional payment information specific to the "bank" group of payment methods
+ You can add your fields that are in webhuk.

If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.

Actions in VK Ads + Leadform (new account)

Click on the name of the action to see the available fields.

API documentation — No.

There are no actions, try Change to replace the services.

Swap Mixplat with VK Ads + Leadform (новый кабинет)

Refract turnkey