Thailand (TH) · Native ads (Taboola, Outbrain, MGID)

    Weight Management on native ads in Thailand

    A slower, steadier source than social. Modeled on the published 2.4% CR and the $18–$32 payout band.

    Team C — native ads team (anonymized)

    Spend

    $8,200

    Approved

    765

    Profit

    $10,925

    ROI

    133.2%

    These are modeled scenarios, not audited partner reports. Network inputs — 47.8% average approve rate, published payout bands and the 14-day payment cycle — are the same figures used across this site. Campaign inputs (spend, clicks, leads) illustrate a 30-day run. Every result below is calculated from those inputs, and the full method is shown so you can reproduce it.

    Numbers

    Full metric table

    GEO
    Thailand (TH)
    Vertical
    Weight Management — metabolism and appetite control
    Traffic source
    Native ads (Taboola, Outbrain, MGID)
    Period
    30 days
    Ad spend

    Campaign input

    $8,200
    Clicks to lander

    Campaign input

    66,700
    Leads

    Clicks x 2.4% published CR

    1,601
    Approval

    Leads x published average approve rate

    765 orders (47.8%)
    Payout

    Published band $18–$32 per approved order

    $25 per approved order
    Revenue

    Approved orders x payout

    $19,125
    Profit

    Revenue - ad spend

    $10,925
    ROI

    Profit / ad spend

    133.2%
    Effective cost per lead
    $5.12
    Effective cost per approved order
    $10.72
    Payment cycle
    14 days

    Campaign

    Angle and execution

    The angle

    Advertorial-first: a Thai lifestyle article about metabolism after 35, leading into the offer instead of selling from the headline.

    What worked

    • Advertorial pre-lander doing the persuasion, short form doing the conversion
    • Widget-level whitelists rebuilt weekly from lead quality, not clicks
    • Urban-female-skewed placements matching the published audience profile
    • Steady daily budget instead of aggressive scaling — native punishes spikes

    What was cut

    • Direct-to-lander traffic without the advertorial step
    • Widgets with high click volume but consistently low approve rates
    • Desktop placements, which underperformed mobile throughout

    Takeaway for affiliates

    Native rewards patience: the profit came from cutting sources on approve rate rather than on click cost.

    Methodology

    How these numbers are produced

    Definitions, formulas, data sources and what has been anonymized.

    How each metric is calculated

    • Leads = clicks to the lander x the conversion rate published for that vertical in the offers vault.
    • Approval = leads x 47.8%, the network average approve rate on quality traffic. An approved order is a lead confirmed by the Thai call-center and accepted for delivery.
    • Payout = the midpoint of the payout band published for that vertical, per approved order.
    • Revenue = approved orders x payout.
    • Profit = revenue - ad spend. No other costs (creative production, tooling, taxes) are deducted.
    • ROI = profit / ad spend, expressed as a percentage.
    • Effective cost per lead / per approved order = ad spend divided by leads or approved orders.

    Where the inputs come from

    • Network inputs — approve rate, per-vertical conversion rates, payout bands and the 14-day payment cycle — are the figures published on this site's offers vault and affiliate pages. Nothing here uses a better number than we publish elsewhere.
    • Campaign inputs — ad spend and clicks — are illustrative for a single 30-day run. They are the part of any case that is campaign-specific, and yours will differ.
    • Period — every case covers 30 consecutive days, with leads counted on the day they were generated and approval measured after the call-center cycle closes.

    What is anonymized, and what is not

    • Partner names, account identifiers, advertiser brand names and creative assets are withheld. Teams are labeled A–D.
    • Verticals, traffic sources, angles, formulas and all metrics are shown in full.
    • No third-party dashboard screenshots are used, because a screenshot proves nothing that the arithmetic above does not already show.
    • These cases are modeled from published averages. They are not audited results and are not a guarantee of your performance.