Readiness checked first
Checks your account against Meta's requirements before anything is built, and tells you plainly if it is not ready.
SOLUTIONS / VALUE OPTIMIZATION
Tell Meta what a new customer is likely to be worth over time, early in their life with you, so value optimization finds more of the customers who stay. Datahash is a Meta Business Partner.
WHEN THIS IS YOU
Meta's public requirements for pLTV, checked on 28 September 2026.
Source: Meta's pLTV integration guidance
Checks your account against Meta's requirements before anything is built, and tells you plainly if it is not ready.
Connects the prediction to the conversion event on the Signals delivery path, deduplicated and matched like the rest of your Meta events.
Verifies the setup in Events Manager until the dataset clears onboarding, then designs the first test against your current campaigns.
Illustrative. No client numbers.
Business model, conversion event, data sources, and Meta eligibility reviewed.
Which prediction to send, with the event or later, and the test plan agreed, with a go or no-go on fit.
Prediction delivered with the conversion event through Signals and verified in Events Manager; Meta advises allowing roughly two weeks for its models to train before the first campaign.
pLTV campaign read against your baseline, documentation handed over, owner named on your side.
IN ONE SENTENCE
Predicted lifetime value (pLTV) optimization is a Meta value optimization option where an advertiser sends its own prediction of each new customer's long-term value through the Conversions API, and Meta optimizes delivery toward people expected to be worth the most over time.
Meta requires a prediction that has been validated in some way before it will optimize on it. Where that prediction comes from, and what it takes to get one in place from the data you already hold, is something our consultants work through with you in discovery. Book a working session and bring whoever owns your customer data.
Not today. Meta's published guidance supports pLTV on web Conversions API integrations only. If most of your acquisition runs through app campaigns, we will say so in scoping and look at what value signal your app stack can send instead.
Purchase value tells Meta what the first order was worth. pLTV tells Meta what you expect the customer to be worth over time. For businesses where first orders are small or similar and later behaviour varies a lot, that difference is exactly what bidding needs to see.
No. Meta receives a predicted value per conversion, not the model, its inputs, or its logic. The value travels on the same hashed, consented Conversions API path as the rest of your events, so nothing about how you predict customer value leaves your control.
Meta's published minimum is 100 conversion events per week attributed to Meta, for each of the last four weeks. Below that, the priority is usually fixing signal coverage and match quality first, which we can do on the same engagement.
Meta recommends running the pLTV campaign against your existing baseline and reading results on pLTV ROAS in Ads Manager. ROAS across different optimization settings is not directly comparable, so the test design, the comparison, and the read date are agreed upfront, before the first campaign spends.
NEXT STEP