Why it matters
Default platform events (Purchase, Lead, CompleteRegistration) are coarse. Teams need rules that match business language: high-AOV orders, qualified leads, or trial starts with predicted subscription value. Custom conversions translate raw events into optimization-ready labels the media buyer understands.
The risk is definition drift. A custom conversion that mixes prospecting and retargeting URLs, or fires before identity stabilizes, teaches the platform the wrong pattern. Multiple overlapping custom conversions split signal volume and extend learning phase.
For pLTV programs, custom conversions are often the named target campaigns optimize toward, while the value field carries the modeled score. Naming and schema discipline matter as much as model accuracy.
Custom conversion
Custom conversions label the event; pLTV supplies the value:
- First-party data in your data warehouse defines which users and outcomes belong in each business conversion definition.
- Churney models user-level pLTV and maps scores to the correct server event and parameter set.
- Events send directly to ad networks via Meta CAPI (and pixel dedup where used) with consistent
event_nameand custom data fields custom conversions reference. - Campaigns optimize toward value optimization or custom conversion goals with differentiated values, not flat counts.
- Calibration and holdout tests validate that the custom conversion plus pLTV value improved cohort outcomes vs business as usual (BAU).
Avoid creating many near-duplicate custom conversions; consolidate on one primary value event per funnel stage.
Category variants
| Model | How custom conversions show up |
|---|---|
| Ecommerce / DTC | URL or event rules for purchase tiers, new customer checkout, or category-specific orders. |
| Subscription app | Trial start or subscribe events as custom conversions; value parameters carry modeled LTV. |
| SaaS / PLG | Qualified lead or activation milestones; sales-assisted funnels may need offline import rules on Google. |
Common mistakes
- Too many overlapping custom conversions. Splits volume; none exit learning phase reliably.
- Rules that do not match server events. Custom conversion expects URL rule while CAPI sends different
event_name. - Optimizing count without value. Custom conversion maximization ignores LTV variance; add value parameters or switch to value goals.
- Changing rules mid-pilot. Invalidates before/after comparisons and holdout readout.
Advertiser lens
| Role | What they ask | What good looks like |
|---|---|---|
| Head of Performance / UA | Which custom conversion should this campaign use? | One primary rule per stage, documented mapping to CAPI event_name and value field. |
| VP Growth / CMO | Do our conversion definitions match finance? | Custom conversions aligned to new customer, paid subscriber, or qualified lead definitions. |
| Marketing Analytics / Data Science | Is volume sufficient? | Weekly event counts per rule, overlap analysis, and value distribution on optimized campaigns. |
| Data Engineering | Do server payloads satisfy rule filters? | Test events in Events Manager; parameter completeness for EMQ. |
| Finance / Procurement | What are we paying vendors to optimize? | Named conversion plus value definition in pilot scope documents. |
FAQ
What is a custom conversion?
A custom conversion is a user-defined conversion rule on an ad platform, typically based on URL patterns, standard events, or parameters. It creates a reporting and optimization label without new SDK instrumentation in many cases.
How are custom conversions different from standard events?
Standard events are fixed schemas (Purchase, Lead). Custom conversions filter or rename those events for business-specific definitions (for example, purchases over a threshold).
Can custom conversions optimize for value?
On Meta, campaigns can optimize for value of conversions tied to purchase or eligible custom setups. Value must be present on the underlying server or pixel events; custom conversion rules select which events count.
How do custom conversions relate to pLTV?
pLTV usually arrives as a value parameter on a server event. Custom conversions (or campaign optimization settings) tell the platform which labeled conversion to maximize with that value.
Should pLTV use a new custom conversion or existing Purchase?
Depends on funnel design. Many teams keep a stable event_name and vary value parameters; others create a dedicated predictive event. Consistency and volume matter more than label novelty.
Do custom conversions work with Google Ads?
Google uses conversion actions (often imported from GA4 or tagged directly) rather than Meta-style URL custom conversions. Concept is similar: defined actions campaigns optimize toward.
What breaks custom conversion optimization?
Low volume, rule/event mismatch, missing values, and frequent rule edits. Monitor Events Manager diagnostics and match quality.
Not the same as
| Term | Difference |
|---|---|
| Standard event | Fixed schema; custom conversion is a rule on top. |
| Custom audience | Targeting segment; custom conversion is measurement/optimization unit. |
| Offline conversion import | Uploads from CRM; custom conversion is usually online rule-based. |
| pLTV | Predicted value; custom conversion is the named conversion target. |
