Create conversion by click ID
Creates a conversion using an existing click_id for attribution. Affiliate and offer are resolved from the click record. All lead/conversion data fields are accepted. If the offer has a Lead Management Receive Leads campaign with required fields configured, empty or missing required fields will result in conv_status=trash.
Authorizations
Preferred authentication method. Pass the API key in the X-API-Key HTTP request header. The user account must have api_status enabled.
Body
(Required) Click ID from the clicks table. Used to resolve affiliate, offer, and geo data.
Conversion status. Values: pending, approved, rejected, hold.
Goal ID. If not provided, default goal is used.
Goal alias. Alternative to goal_id.
Affiliate click ID (external).
IP address. If provided, overrides geo data from the click.
Conversion timestamp. Format: Y-m-d H:i:s.
Click timestamp override. Format: Y-m-d H:i:s.
Forwards the created lead to the external systems configured for its goal. With yes the lead is posted out; with no (the default) it is only recorded in Scaleo. Delivery needs the Leads Management Module, an active Receive campaign bound to the lead's goal_id, and at least one active Deliver vendor on that campaign - without them, or when a vendor's posting instructions are empty, yes has no effect. Each vendor is called with its own posting instructions (URL, method, headers, tokenized body); its answer is matched against the vendor's success reply and sets the lead's delivery status - success, fail, or empty when the vendor has no success reply configured. Every attempt is stored in the leads log as an Outgoing Lead record. Leads that end up in the trash conversion status (failed campaign validation, geo check, or cap) are never delivered. If the vendor has "return reply" enabled, its raw response is added to the response payload as delivery_reply.
yes, no