01
CPL
Payment for a defined lead event, subject to validation.
01 / Operational context
A conversion name is not a full specification
“Lead” can mean a form submission, account creation, email confirmation or a validated user. Before traffic launches, the payable event and rejection conditions must be explicit.
02 / Operational context
SOI and DOI change the funnel economics
Single opt-in generally reduces friction but may require stronger validation. Double opt-in adds confirmation and often changes both conversion rate and quality. Buyers should compare approved EPC rather than raw front-end conversion rate.
03 / Operational context
Caps and holds are part of inventory management
Advertisers may limit volume while evaluating quality. A routing network must respect caps, pause unavailable routes and send eligible traffic to fallback destinations.
System components
What the operating model includes.
02
CPA
Payment after a specified user action or approved outcome.
03
SOI
A single user action without a separate confirmation step.
04
DOI
A registration followed by a second confirmation event.
05
Approval
The difference between raw conversions and payable conversions.
06
Payout value
The commercial value returned through reporting and postback fields.
Launch checklist
What to validate before volume increases.
Ask which event is payable
Confirm approval and rejection reasons
Track raw and approved conversions separately
Calculate EPC after approval
Monitor cap utilisation
Avoid comparing offers only by headline payout
Operational principle
SmartLink routing does not replace transparent traffic acquisition, stable tracking or partner communication. It makes those inputs more useful by connecting them to eligible dating inventory.
Continue reading
Related Smartlinkella resources.
Apply
Bring us your traffic. We’ll bring the routing.
Tell us the source, GEO mix and approximate monthly volume. The same application endpoint records the page that generated the request, so topic-level lead attribution remains available.