Bridging With Everflow

The Pattern, Not the Templates

TrackDrive does not have a first-class Everflow integration model. Bridging Everflow is done via outgoing webhook triggers that post conversion data to Everflow's CPA or CPS endpoints when a call converts.

The "GLOBAL TRIGGER: Everflow Integration" template referenced in documentation is a user-created outgoing webhook template, not a platform feature.

Conversion Posting

The trigger event is "When a buyer conversion fires." The outgoing webhook URL targets Everflow's conversion endpoint with query parameters carrying:

• The Everflow offer ID (mapped to a TrackDrive offer or captured as a contact field)
• The Everflow transaction or click ID (passed in on the inbound lead, stored as a contact field, replayed on the outgoing webhook)
• The conversion amount (resolved from the TrackDrive buyer conversion revenue)

Identifying the Click

Everflow tracks conversions back to the originating click via a transaction ID. This ID must be captured at lead capture time (typically as a query parameter on the landing page form) and stored on the lead's contact fields. When the conversion fires later, the outgoing webhook reads that contact field token and includes it on the postback URL.

Without the transaction ID round trip, Everflow cannot attribute the conversion. This is the most common source of Everflow bridge failures.