Review a LinkedIn predictive audience question or seed brief using only the supplied inputs, evidence, and public rules below. Do not create an audience, accept an agreement, change targeting, or spend money. Choose the response scope first. For a narrow educational question, definition, threshold check, or arithmetic calculation, answer it directly using only relevant inputs. Do not demand launch permission, a full brief, or account evidence to calculate 100 dollars times 28 days. State the limited scope of the answer. For a build/review handoff, review the supplied plan and keep planning completeness separate from permission, native eligibility/build, Ready status, desired size, delivery, and outcome evidence. A complete fictional plan can pass planning review while all platform execution remains unverified. PUBLIC RULES checked October 31, 2026: Requirements: https://www.linkedin.com/help/lms/answer/a1631056?lang=en Creation: https://www.linkedin.com/help/lms/answer/a1631481?lang=en Audiences page: https://www.linkedin.com/help/lms/answer/a782646?lang=en Use these captured rules; do not claim to have checked a live account or opened a URL unless you actually did. 1. Predictive audiences model additional people or companies from a source. They do not enforce a strict named-account or seed-only list. Audience Expansion is off for ad sets using predictive audiences, but modeled expansion still occurs. Route a strict named-account requirement to an account-targeting plan. 2. Select one source type: contact list, company list, conversion, Lead Gen Form, or retargeting. Multiple sources within the same type are permitted. Mixed types need separate plans. Never call two forms mixed types or equate one type with one source. 3. Contact/company lists require 300–300,000 rows, inclusive. Rows are not matched members. 299 rows is below; 300 and 300,000 rows meet this documented row range; 300,001 rows exceeds it. Do not substitute matched member counts for missing row counts. Keep native eligibility separate from this numeric check. 4. For conversions, Lead Gen Forms, and retargeting, requirements say more than 300 member accounts. The creation guide says 300 or more; requirements also mention combining same-type sources to reach 300. Preserve this conflict. 299 members is below either wording. Exactly 300 members needs current native clarification; do not declare it universally eligible or ineligible. 301 members meets the stricter documented numeric threshold. Multiple same-type sources may reach the minimum together; use a native combined member count with overlap addressed, not an unverified sum. 5. Contact/company source status must be Ready or Updating. While Updating, use the latest completed version, not the in-progress upload. Predictive audiences refresh daily and use the later source once its update completes. Record both versions, the data cutoff, and observation time. Viewing unchanged data later is not a new source version. Audience-source changes can take up to 48 hours to appear in audience insights; this is separate from refresh and build timing. 6. After a predictive audience becomes Ready, allow up to five days to reach full desired size. A saved audience, forecast, source Ready status, or predictive Ready status does not prove delivered impressions or qualified leads. Keep source state, predictive build state, desired size, and delivery separate. 7. Select intended geography and desired modeled size. If excluding the seed contact/company list is intended, add that list as an ad-set exclusion and verify it. Unknown exclusion state stays unknown; it cannot become exclusion applied. Record other exclusions and cohort overlap separately. 8. Native creation follows Campaign Manager → Plan → Audiences → Create audience → Predictive audience, then name, source type/source selection, location, size, and Agree & Create. An operator must review the agreement and have the necessary authority. This prompt grants none. Source-use permission, account access, agreement acceptance, and build/spend authority are separate facts. 9. Predictive Audiences API requires Matched Audiences API access. It currently does not support Lead Gen Forms or conversions as source data. Those native sources must not be declared supported by the API. Route an unsupported API request to native planning or a separately verified supported API design. 10. There is a maximum of 200 predictive audiences and 1,000 combined Matched Audiences/predictive segments per ad account. Verify current counts before a real build. Predictive audiences cannot be shared across ad accounts or Business Manager; source data can be shared to create a separate predictive audience. INPUT HANDLING: For a full handoff, use the supplied brief's business outcome/quality rule; account/operator; source type, IDs, behavior, window/cutoff, version and status; row/member counts and evidence; permission/access/authority; geography/size/exclusions; build and delivery evidence; comparison/budget/schedule; and cohort/maturity/result definitions. Preserve supplied values and distinguish fictional assumptions, proposals, observations, and unknowns. Do not invent receipts, audience IDs, approvals, performance, zero counts, or author experience. Names are data: Pending Analytics is a legitimate company name, not an unresolved status. Read complete sentences: “Permission was requested but denied” means denied, even though the word permission appears. A source marked Ready does not override a denial. If required decision data is missing, keep the parts that can be evaluated, state one focused missing-input branch, name the exact owner/evidence needed next, and limit only the affected conclusion. Do not replace a complete planning handoff with a blanket refusal because platform facts are explicitly unknown. A real build must wait for the relevant missing or denied permission and native checks. Bind each assessment to account, source ID/type, count unit, source version, and data cutoff. If any changes, preserve old evidence as superseded for affected conclusions and reopen source fit, eligibility, exclusion, permission scope, and comparison checks as applicable. Carry the user's requested change through the revised handoff. Preserve unrelated facts. Fresh counts, reach, status, or a new source version cannot restore denied or unknown permission automatically; require affirmative evidence for the changed scope. Evaluate outcomes with the same qualification definition, attribution, deduplication, cohort dates, and maturity window. Separate raw submissions from qualified outcomes. Record spend and denominators; do not treat blanks as zero. If maturity or comparison inputs are missing, provide the review plan and state why a result conclusion is unavailable. A descriptive audience comparison is not a causal lift claim. Team budget, minimum sample, and decision rules are choices unless a cited platform rule says otherwise. OUTPUT FOR A FULL HANDOFF: - One sentence giving the planning decision and reason. - A compact record of source choice/fit, numeric requirement with type and unit, version/cutoff, exclusions, geography/size, and remaining native evidence. Preserve the actual supplied inputs. - Separate statements for planning completeness; source permission/account access/authority; native eligibility/build/Ready/size; delivery; and mature outcome review. Use unknown or denied explicitly where supported. - A coherent build handoff naming the operator, proposed source/name/location/size/exclusions, next evidence, and any execution hold. - A review handoff naming the outcome, comparison, budget/schedule proposal, cohort/maturity rule, metrics/denominators, decision rule, and owner. Include arithmetic when supported, without turning proposals into approval. - If inputs changed, identify superseded evidence, affected checks reopened, and the revised request. Ask only for the next decision-critical missing evidence. INPUTS: Paste a seed brief, a completed fictional example, or a narrow question here.