Skip to main content
Send an incoming event to record an action for a tracked visit. The sending system must return the Metricanic click ID that it received with the visit.

​
Connect one purchase event

For a new campaign with one conversion, use Simple in 2. Events. For an existing Advanced setup, keep that mode. Configure the intended event with Count as conversion and From incoming event revenue. The steps below use Event 1:
  1. Copy the campaign’s Incoming event URL for Event 1.
  2. Replace its click ID placeholder with the sender’s macro for the stored Metricanic click ID.
  3. Replace the payout placeholder with an amount or the sender’s payout macro.
  4. Add txuid with the sender’s order ID.
  5. Set the trigger to the action you want to measure, such as a completed payment.
  6. Save the postback in the sending system and test one purchase.
The completed request has this form:
Replace the domain and click ID with values from your test visit. With these settings, this event adds one Event 1, one Conversion, and USD 24.50 revenue. It can also send an outgoing postback if you enabled one.

​
Preserve the correct identifier

Pass {click_id} in the offer URL. Store that full value with the lead or order, then return it in the incoming event. Use the parameter and return macro specified by your affiliate network. See Affiliate networks for setup.

​
Check the result

Open Events and find the test event. Then check the campaign report for the original visit date. See Dates and filters if the event and report dates differ. The incoming event URL returns a small image and can look like a blank page. Use reports to check whether the event was recorded. If the event is missing, follow Find why a conversion is missing.

​
Choose the fields you need

Use a decimal point for amounts. value appears in Value N and does not set revenue. Configure conversion counting and revenue and cost in the event settings.

​
Make retries repeat the same event

Include txuid when the sender can retry. Use an order or action ID of no more than 64 characters. Keep the same click ID, idx, and txuid for another attempt to send the same event. Use a new txuid for a new purchase. You can reuse the order ID with a different idx for another stage, such as approval.
You can send event fields as JSON or form data. For example:
Put all event fields in the body for this setup.
To send an event from a page with the tracking script, use logEvent().