> ## Documentation Index > Fetch the complete documentation index at: https://docs.innkeepr.ai/llms.txt > Use this file to discover all available pages before exploring further. # Set Up Seed Audiences on Meta ## Overview Innkeepr Seed Audiences are custom audience lists uploaded to Meta Ads Manager. They contain visitors ranked by predicted incremental lift based on your selected objective. Meta uses these lists as a basis for Lookalike Audiences (LALs) in ad sets. This guide covers the setup of Innkeepr Seed Audiences on Meta, including audience structure, testing, and scaling. ## Prerequisites **Technical Requirements:** * Active Meta Ads Manager account * Innkeepr integration connected to your Meta account * Sufficient conversion data for signal generation (minimum 30 days recommended) **Timeline at a Glance:** | Phase | Duration | What Happens | | ----------------- | --------------- | ---------------------------------------------------------- | | Audience setup | Immediate | Audiences created and uploaded to Meta | | Audience matching | 24–48 hours | Meta matches the uploaded users and populates the audience | | Testing phase | 2–4 weeks | Performance comparison against broad targeting | | Scaling | After 2–4 weeks | Budget reallocation based on results | ## Audience Types Innkeepr provides two seed audience types for Meta: **Custom Audiences** User lists uploaded directly to Meta. These lists contain visitors ranked by predicted incremental lift based on your selected objective. The objective determines what the ranking optimizes for — for example conversion probability, customer lifetime value, or average order value. They are used as source audiences for Lookalike Audiences. **Value-Based Audiences** Lists of users identified by email address, where each entry has an assigned value based on predicted incremental impact. Unlike custom audiences, value-based audiences require an email address for each user — visitor-level data without email is not sufficient. Meta uses these values to build Lookalike Audiences that prioritize finding users similar to the highest-value entries, not just the full list. This gives Meta an additional signal for LAL expansion. Email handoff to Innkeepr works via shop system integration (e.g. Shopify) or Innkeepr Identify. **Learn more:** * [Shop System Integrations](/guides/integrations) * [Innkeepr Identify](/guides/spec-identify) ## Setup Instructions **Step 1: Create Audience Buckets** There are different ways to use seed audiences on Meta, and not every setup works equally well across all accounts. The optimal configuration depends on factors like audience size, conversion volume, and product category. As of March 2026, we recommend the following setup as a starting point: **Recommended bucket structure:** | Bucket | Audience Type | Innkeepr Percentile | Lookalike Size | Rationale | | -------- | -------------------- | -------------------------- | -------------- | ------------------------------------------------------------- | | Bucket 1 | Custom Audience | Top 0–10% | 1% LAL | Most selective signal, smallest but highest-quality lookalike | | Bucket 2 | Custom Audience | Top 10–20% | 5–10% LAL | Broader signal, medium-sized lookalike | | Bucket 3 | Custom Audience | Top 20–30% | 10% LAL | Broadest signal, largest lookalike for reach | | Bucket 4 | Value-Based Audience | Based on incremental value | 10% LAL | LAL expansion weighted by predicted incremental impact | The logic: more selective source audiences (smaller percentile) are paired with smaller LALs to maintain signal quality. Broader source audiences can support larger LALs because the expansion is less sensitive to individual user variation. **Step 2: Upload Audiences to Meta** 1. **Create audiences** in Innkeepr for each percentile bucket 2. **Select "Meta"** as your destination 3. **Upload** — Innkeepr sends `innkeepr_targeting` events to your connected Meta pixel 4. **Verify events in Meta Events Manager** — after the first upload, the `innkeepr_targeting` event appears in your Events Manager. You need to approve the event before Meta processes the audience data. Without this approval, audiences will not populate. 5. **Create Lookalike Audiences** in Meta Ads Manager based on each uploaded bucket, using the LAL sizes from the table above **Step 3: Set Up the Campaign Structure** Test Innkeepr audiences against broad targeting within a single campaign using separate ad sets. **Campaign structure:** | Ad Set | Targeting | Purpose | | ------- | -------------------------------- | ---------------------- | | Control | Broad (no audience targeting) | Baseline performance | | Test 1 | Bucket 1 — Top 0–10%, 1% LAL | Highest-quality signal | | Test 2 | Bucket 2 — Top 10–20%, 5–10% LAL | Medium signal | | Test 3 | Bucket 3 — Top 20–30%, 10% LAL | Broadest signal | | Test 4 | Bucket 4 — Value-Based, 10% LAL | Value-weighted signal | **Important:** Keep all other variables identical across ad sets: * Same **creatives** (images, videos, copy) in every ad set * Same **optimization event** (e.g. Purchase, Add to Cart) * Same **bid strategy** * Same **placements** (or all set to Advantage+) The only difference between ad sets should be the audience targeting. If creatives or other settings differ, performance differences cannot be attributed to the audience signal. **Step 4: Set Budget Allocation** Start all ad sets with the **same daily budget** using **ad set budget optimization (ABO)**. Do not use campaign budget optimization (CBO / Advantage Campaign Budget) during the test phase — CBO shifts spend unpredictably between ad sets, making it difficult to compare performance. After 1–2 weeks, you can begin scaling individual ad sets based on observed performance (see Monitor & Optimize). ## Monitor & Optimize **Weeks 1–2: Observation Phase** * Do **not** adjust budgets, bids, or creatives during the initial learning phase * Monitor that all ad sets are **spending their allocated budget** and exiting the learning phase * Verify that conversions are being tracked correctly across all ad sets **Weeks 2–4: Evaluation** * Compare **ROAS, new customer share, and AOV** across ad sets * Identify which buckets outperform broad targeting and by how much * If a bucket underperforms broad consistently, it can be paused **After Week 4: Dynamic Scaling** Once you have sufficient data (2–4 weeks minimum), begin scaling: * **Increase budget** on the best-performing Innkeepr ad sets incrementally (20–30% per increase, not more) * **Measure how much additional spend** the Innkeepr audiences can absorb while maintaining comparable performance to broad * The goal is to determine what share of total campaign spend Innkeepr audiences can cover at equal or better performance than broad targeting * Continue monitoring after each budget increase — allow 3–5 days for Meta's algorithm to stabilize before evaluating > **Scaling question to answer:** How much additional spend can Innkeepr audiences absorb compared to broad targeting, at the same or better CPA/ROAS? This determines the incremental budget capacity that Innkeepr unlocks for your Meta campaigns. ## Best Practices **Creative Isolation** The test is only valid if creatives are identical across all ad sets. If you want to test new creatives or add additional creatives during the test, add them to all ad sets at the same time. Never add creatives to only some ad sets — this makes performance differences between ad sets unattributable. **Lookalike Size Selection** The recommended LAL sizes (1%, 5–10%, 10%) are starting points. Depending on your market size and target geography, you may need to adjust: * Smaller markets (e.g. single country, DACH): start with 1%, 3%, 5% * Larger markets (e.g. EU-wide, US): 1%, 5–10%, 10% works well ## Troubleshooting **Audiences Not Populating** | Possible Cause | Solution | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `innkeepr_targeting` event not verified | Open Meta Events Manager and check if the `innkeepr_targeting` event is listed. If it shows as unverified, approve it. Audiences will not populate until the event is verified. | | Pixel not connected correctly | Verify that the correct Meta pixel ID is configured in Innkeepr | | Insufficient audience size | Meta requires a minimum audience size — check that the source audience in Innkeepr contains enough users | **All Buckets Underperform Broad** | Possible Cause | Solution | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Insufficient data in Innkeepr model | Verify that enough conversion history was available when audiences were created | | LAL sizes too narrow | Test with broader LAL sizes (e.g. 5% instead of 1%) | | Audience stale | Check if corresponding targeting events from Innkeepr arrive at the correct pixel and that the events are verified | **Performance Drops After Sales Phases** Performance drops can coincide with sales events (e.g. Black Friday, seasonal promotions). During and after these phases, audience composition and conversion patterns shift temporarily. Innkeepr typically detects these phases automatically and adjusts the underlying models accordingly. If a performance drop persists for more than 1–2 weeks after a sales event has ended, reach out to the Innkeepr team to verify that the model has recalibrated correctly. Learn more * [Audience Signals](/guides/signals-and-activation/audience-signals) * [Set Up Audience Signals on PMax](/guides/how-to-guides/pmax) * [Set Up Conversion Signals on Google](/guides/signals-and-activation/conversion-signals)