What network integration involves
- Receiving and/or posting leads to MediaAlpha
- Everflow offer setup, click tracking, and postbacks
- Source and sub-ID attribution across every network
Cross-network attribution
Everything hangs off one consistent set of source parameters read from the landing-page URL and carried through capture, delivery, and reporting, so a lead can always be traced back to the exact click that produced it.
| Parameter | What it carries |
|---|---|
| a | Affiliate / publisher ID |
| oid | Offer ID |
| r | Transaction / click ID |
| sub1-sub5 | Sub-IDs for finer source granularity |
| source_id | Traffic source ID |
On the tracking side, Everflow's SDK fires EF.click on page load with the affiliate, offer, sub-IDs, source, and transaction ID, and a conversion pixel posts back on the thank-you step keyed to that same transaction ID, so the conversion reconciles against the original click. On the monetization side, the MediaAlpha Exchange placement carries the same identifiers in its sub fields, the affiliate in sub_1, the offer in sub_2, and the transaction ID in sub_3, so revenue from MediaAlpha ties back to the same source as a form lead.
FAQ
- Can you integrate MediaAlpha and Everflow?
- Yes. Receiving/posting leads and wiring Everflow postbacks, with attribution preserved.
- Can you track lead source across networks?
- Yes. Sub-ID/source attribution travels with every lead.