Overview

Every click and every conversion in Everflow gets its own ID. You'll see these IDs in API responses, postback payloads, webhooks, and reports. Knowing which is which keeps your attribution accurate and your dedupe logic correct.

The two identifiers

Both IDs are 32-character hexadecimal strings (e.g. 868c44c49aad4c8d9091b7a2a74c716c).

How they relate

One transaction_id can be associated with multiple conversion_ids. A single click can lead to:

Each one generates its own conversion_id, but they all share the same transaction_id because they're attributed to the same original click.

An everyday example

Imagine a shopper sees an Instagram post from one of your partners, taps the link, and lands on a sneaker store. That tap creates the transaction_id — let's call it abc123. Now follow what happens next:

Four conversions, four conversion_ids, all sharing the same transaction_id abc123 — because they all trace back to that one Instagram tap. The partner who drove the original click gets attribution for every one of them. For a deeper look at how to model multi-step flows like this, see Practical Funnels Using Additional Conversion Events.

Deduplication

SQL examples

-- Correct
SELECT * FROM conversions WHERE conversion_id = 'def456...';

-- Wrong — will miss upsells and post-events
SELECT DISTINCT ON (transaction_id) * FROM conversions;

Getting a transaction ID

The transaction_id is only generated by a click. You can't derive or construct it from an offer ID + affiliate ID combination, and there's no API that returns a transaction ID for a given offer/affiliate pair without a real click happening.

How to obtain one

You obtain a transaction_id in one of these ways:

Using the transaction ID on conversions

When you fire a conversion, passing transaction_id explicitly is the most reliable form of attribution:

JavaScript SDK example

// JavaScript SDK
EF.conversion({
  offer_id: 1,
  transaction_id: EF.getTransactionId(1),
  amount: 49.99
});

Server-side postback example

# Server-side postback
curl "https://www.your-tracking-domain.com/?nid=1&transaction_id=abc123...&event_id=2"

For a full conceptual overview of all three ways to fire conversions, see Introduction to Conversion Tracking Methods, Introduction to Conversion Events, and How to Set Up Conversion Events. To verify your postbacks are firing correctly, walk through How To Test Partner Postbacks.

Looking up events for a transaction

To see every conversion and post-conversion event attached to a single transaction_id, use the lookup endpoint:

GET /v1/networks/reporting/conversions/transactions/{transaction_id}

This returns the full tree of conversion events that share the transaction ID — useful for debugging attribution issues or auditing upsell flows.

Finding IDs in the UI

Most of the time, you'll spot a transaction_id or conversion_id in a report first, then come here to figure out what to do with it. Here's where each ID lives in Core Platform.

Investigator — trace one transaction → full event tree

Investigator is the purpose-built UI for what we just covered with the lookup endpoint: paste a transaction_id in, see every conversion and post-conversion event linked to that one click. It's the fastest way to debug an attribution question.

From the left rail, open Investigator, click Add Investigation, set the Target to Transaction ID, and paste the IDs you want to inspect into the Suspects field.

The summary view lists every Click Transaction tied to your suspect IDs, with Offer, Partner, and manager context for each. From there you can click into a row to see the full breakdown:

The detail view shows the click and every conversion event attached to it — a base sale, any upsells, and any partner postbacks that fired. Each row includes its transaction_id and conversion_id so you can cross-reference back to your own data.

Read more in How To Use Investigator.

Conversion Report — browse all conversions

Each row in Conversion Report is one conversion event — so each row has its own conversion_id plus the parent transaction_id. Filter by date, offer, partner, status, or any sub parameter to narrow down what you're looking for.

If the Transaction ID or Conversion ID columns aren't showing, open the table-actions menu (the three dots in the top right of the table) and toggle them on under Column Customization. Read more in Conversion Report.

Click Report — browse all clicks

Click Report is the other side of the coin: each row is one click, so each row has one transaction_id. Useful when you have a partial transaction ID and need the full one, or when you're debugging which clicks fired without converting.

The Transaction ID column is hidden by default. Open the table-actions menu, choose Column Customization, and toggle Transaction ID on:

Once enabled, the column shows the full ID for every logged click:

Read more in Click Report.

Filtering by ID

For a deeper look at the funnel-style flows that share a transaction_id, see Funnel Report — it visualizes how one click chains through multiple events (the same shape as the sneaker example above).

Summary

Related help desk articles

If you want the full picture on how clicks, conversions, and tracking methods fit together, these are the next reads:

Tracking fundamentals

Conversion events & funnels

Conversion tracking methods

Technical reference

If you're building an integration that records clicks or fires conversions, head to the developer docs for full SDK references, request/response shapes, and code samples.

SDK references

Endpoint references

Endpoint references for transaction-aware conversion APIs: