Postback configuration lets you send server-to-server notifications to your affiliate network when order status changes (e.g. success, declined, pending). Your network gives you a postback URL; you enter it in the campaign and choose which status events trigger the call and how commission is reported. This enables real-time conversion tracking and commission settlement.

Step 1: Open Postback Configuration

1. Open CRM > Campaigns.

2. Click Edit on the campaign you want to configure postbacks for.

3. In the left panel, select the Postback Configuration tab.

Step 2: Configure postback settings

1. Postback URL — Enter the endpoint URL provided by your affiliate network (e.g. https://network.com/conversions/postback). Use Test to verify the URL before saving.

   

2. Token Mappings — Optional. Use this when your affiliate network expects its own parameter names. Each row pairs a Custom Key (the name the network expects, e.g. cid) with a Token (the Admoji value it carries, e.g. Click ID). Click + Add Token Mapping for each pair you need, or the × next to a row to remove it. Every mapped key is renamed in the payload before it is sent.

   You can also drop a token straight into the URL as a {token} placeholder — for example https://network.com/postback?cid={click_id}&val={commission}. Once you have defined a mapping, its key appears as a chip below the URL field; clicking the chip appends that parameter to the URL for you.

   Note: A token used as a {token} placeholder in the URL is not appended to the query string a second time. Its value is URL-encoded for you, and a placeholder that does not match a token resolves to an empty string.

   

3. Status Triggers — Choose which order status events send a postback. The available options are All Status Events, Success, Declined, Error, Pending, Cancelled, Chargeback, and Partial. Selecting All Status Events subscribes the campaign to every status, including Partial. Partial is not an order status — it is what enables the cart abandon postback described below.

   

4. Commission Type — Select CPA (Fixed Amount) or CPC (Percentage).

   

5. Commission amount — Enter the fixed amount (e.g. in dollars) or the percentage (0–100), depending on the commission type.

   

   

6. Available Postback Tokens — Select which data to send in the postback. The full list is: Customer ID, Customer First Name, Customer Last Name, Customer Email, Customer Phone, Customer Address, Customer Address 2, Customer City, Customer State, Customer Zip, Customer Country, Order ID, Order Total, Transaction ID, Products, Status, Click ID, Affiliate ID, Sub Affiliate ID, Sub Affiliate ID 2, Sub Affiliate ID 3, Sub Affiliate ID 4, Sub Affiliate ID 5, Commission, Commission Type, Campaign ID, Campaign Name, and Timestamp. If you leave every token unselected, the postback carries all of them.

   

7. Send Payload in Request Body — Turn on to send the payload as JSON in the request body; leave off to send it as URL query parameters.

   

8. Click Save Postback Configuration.

Cart abandon postbacks

Cart abandon postbacks reuse this same configuration — there is nothing extra to set up. Whenever Partial is one of your Status Triggers (on its own, or through All Status Events), Admoji fires a postback as soon as a partial customer is created, before any transaction runs.

• The payload carries the customer and affiliate tokens you selected, with no order data, and status is sent as CartAbandon.

• It fires when you save the customer step of For Customers > Add New Order, and when a partial customer is created through the Add Customer API endpoint.

Implementation requirements

For postbacks to work, your backend must capture and store the affiliate’s click ID when the customer lands on your landing page. That click ID is sent back in the postback so the network can match conversions to clicks. Capture the click ID from the URL parameter and pass it to the Add Customer API as ClickID. See the API Add Customer documentation for the exact request format.