Real MYM conversions, into Meta
MYM has the same blind spot as OnlyFans — the payment happens on a site you can’t pixel. A server-to-server postback carries the real paid conversion, with its actual value, back to Meta’s Conversions API. Because MYM subscriptions are genuinely paid, that real value can unlock value-based optimization.
The MYM blind spot
Just like OnlyFans, MYM’s subscription and payment happen on a domain you don’t control and can’t install a pixel on. So a browser pixel never sees the conversion, Meta gets no signal, and your MYM ads optimize toward nothing. The mechanism that fixes it is a postback.
How the postback round trip works
- Tag the clickWhen a fan clicks the ad, a click identifier is attached and carried into the MYM funnel.
- MYM reports the conversionWhen the paid subscription happens, MYM’s system fires a server-to-server postback — carrying that identifier and the real paid value.
- Forward to MetaThe conversion is delivered to Meta’s Conversions API with the identifier matched back to the original click, so it attributes to the right ad.
Because the postback carries an actual payment amount, Meta receives a genuine value — the missing ingredient for value optimization that a free-subscription funnel has to work around.
Browser pixel alone vs a postback
A browser pixel on your landing page sees the click and then goes dark — MYM is off-domain. The postback is what carries the paid conversion the whole way to Meta:
| What reaches Meta | Browser pixel only | MYM postback |
|---|---|---|
| The landing-page click | ✓ | ✓ |
| The MYM paid subscription | ✗ | ✓ |
| The real paid value | ✗ | ✓ |
| Matched back to the ad | ✗ | ✓ |
| Survives iOS / ATT & ad blockers | ✗ | ✓ |
| Value-based bidding | — | ✓ |
Same destination as OnlyFans
Whether a conversion starts on OnlyFans or MYM, it ends up the same way: a real, matched, server-side event in Meta. Run both platforms and they feed one coherent picture of what your ads actually earn — see the funnel and creator stats.
- Subscriberead server-side and forwarded
- Purchase · with valuetips, PPV & renewals
- Subscribepostback fired by MYM’s system
- Purchase · with valuereal paid amount on the round-trip id
Questions
What is a postback?
A server-to-server message. When a conversion happens on MYM’s side, MYM’s system calls a URL to report it — no browser involved. That postback carries an identifier tying the conversion back to the click that started it, plus the real paid value, which is then forwarded to Meta’s Conversions API.
How does the conversion get matched back to the ad?
Through a click identifier that makes the round trip: it’s attached when the fan first clicks, carried through to MYM, and sent back on the postback. That round-trip ID is what lets Meta attribute the MYM payment to the specific ad and person.
Why does the real value matter?
Because MYM subscriptions are genuinely paid, the postback can carry an actual monetary value — not a zero or a guess. Real value is exactly what Meta’s value optimization needs, so a MYM funnel can unlock value-based bidding that a free-subscription funnel struggles to.
Is this different from the OnlyFans setup?
Same principle, different source. OnlyFans conversions are read from the account and sent server-side; MYM conversions arrive as a postback from MYM’s system. Both end up as real, matched, server-side events in Meta.
