Overview
Audience signals in Performance Max provide Google’s algorithm with targeting guidance. By default, PMax optimizes broadly across all users. Innkeepr audience signals narrow that guidance using incremental prediction models — they identify users who are more likely to convert because of an ad, rather than users who would convert regardless. This guide walks you through setting up a test-vs-control campaign structure with Innkeepr audience signals. After completing all steps, you will have two comparable PMax campaigns running: one with Innkeepr signals applied, one without, allowing you to measure the difference.Prerequisites
Technical Requirements:- Active Google Ads account with Performance Max campaigns enabled
- Sufficient conversion data for signal generation (minimum 30 days recommended)
| Phase | Duration | What Happens |
|---|---|---|
| Signal setup | Immediate | Audiences created and linked |
| Campaign learning phase | 30–60 days | Google’s algorithm adapts to new signals |
| Performance stabilization | 60–90 days | Reliable data for evaluation |
Important: Do not evaluate performance before the 60-day mark. PMax needs time to collect data, optimize bid strategies, and stabilize across inventory types. Early results are unreliable.
Understanding Signal Parameters
Before configuring your signals, it helps to understand what each parameter controls:| Parameter | What It Does | Example |
|---|---|---|
| Lookback Window | How far back Innkeepr analyzes user behavior to build the signal. Shorter windows reflect recent behavior; longer windows include more historical data. | 30 days = recent activity. 90 days = longer-term behavioral patterns. |
| Percentile Threshold | Which share of users to include, ranked by predicted incremental conversion probability. Lower percentages are more selective. | Top 50% = broader signal. Top 30% = more selective signal. |
| Conversion Lag | Accounts for products where purchases happen days or weeks after the initial interaction. Without this, the model may undercount users who convert later. | No lag = fast-converting products (fashion, FMCG). 180 days = longer purchase cycles (insurance, furniture). |
Setup Instructions
Step 1: Design Your Campaign Structure Why a campaign split (not an asset group split)? As of February 2026, Google does not allow access to click-based performance data at the asset group level through the API. Only campaign-level data includes full-funnel metrics (clicks, CTR, CPC, conversions, ROAS). Testing in separate campaigns is the only way to accurately compare performance. Budget Allocation:| Campaign | Budget Share | Purpose |
|---|---|---|
| Test (with Innkeepr signals) | 20–30% | Measures signal impact |
| Control (without signals) | 70–80% | Baseline for comparison |
Why not 50/50? A smaller test budget reduces risk during the learning phase while still generating enough conversion volume for comparison. Increase the test share once you have sufficient data to evaluate results.Step 2: Create Signal Configurations Create 2–3 asset groups in your test campaign, each targeting the same products but with a different audience signal configuration. Recommended Starting Configurations:
| Signal | Lookback | Percentile | Conversion Lag | Best For |
|---|---|---|---|---|
| Signal 1 | 30 days | Top 50% | None | Fast-converting products (fashion, FMCG) |
| Signal 2 | 30 days | Top 50% | 180 days | Products with delayed purchase decisions |
| Signal 3 | 90 days | Top 30% | 180 days | High-value, long-consideration products |
Not sure which configuration fits your use case? Contact our team — we can help determine the right parameters based on your conversion data and product categories.Step 3: Create and Apply Audiences in Innkeepr
- Create audiences in Innkeepr based on your selected configurations
- Select “Google Analytics” as your source — the audience list is uploaded via GA4 and then becomes available in your linked Google Ads account
- Set the Audience Type to Seed
- Configure parameters — set lookback window, percentile threshold, and conversion lag according to your chosen configuration
- Link audiences to the corresponding asset groups in your test campaign in Google Ads
- Innkeepr seed audiences — these are your primary audience signals
- Search terms — custom search themes that are relevant to your products
- Demographics (age, gender, household income, parental status) — these restrict the signal unnecessarily and overlap with what Google already optimizes for
- Interests and detailed demographics (in-market, affinity audiences) — adding these dilutes the Innkeepr signal with broad Google segments
- Other first-party user lists (CRM uploads, website visitors, customer match lists) — mixing other lists with Innkeepr signals makes it impossible to attribute performance to a specific signal source
- Identical target ROAS (tROAS) across both campaigns — mismatched tROAS invalidates the comparison (see Best Practices below)
- Proportional daily budgets — 20–30% for test, 70–80% for control
- Identical asset groups in both campaigns, except for the audience signals in the test campaign
- Similar inventory types enabled across both campaigns — ensure test and control use the same inventory configuration (Search, Display, Shopping, Video, Discover)
- Test and control campaigns have identical tROAS values
- Budget split is 20–30% test / 70–80% control
- Audience signals are applied only to test campaign asset groups
- Asset groups (products, creatives, ad copy) are identical across both campaigns
- Inventory types match across both campaigns
- Conversion tracking is verified and capturing all relevant conversions
- Innkeepr audience sizes are sufficiently large (check in the Innkeepr dashboard)
Monitor & Optimize
Weeks 1–4: Hands Off- Do not adjust tROAS, budgets, or signals during the initial learning phase
- Review the PMax placement report weekly to understand spend distribution
- Expect inventory shifts — campaigns with Innkeepr signals may allocate more to Display/Video early on (this is expected behavior)
- Compare ROAS, CPA, and conversion volume at the campaign level (test vs. control)
- If performance is significantly off target, make small adjustments (10–20% tROAS change) — but always adjust tROAS on both test and control campaigns equally, otherwise the campaign with higher tROAS will lose spend
- Allow 7–14 days after any adjustment before re-evaluating
- Aim for 50–100+ conversions per campaign before drawing conclusions
Best Practices
Target ROAS Alignment Set identical tROAS values across test and control campaigns. Google Ads gives more bidding flexibility to campaigns with lower tROAS, which skews results and makes it difficult to isolate the effect of audience signals. If you need to adjust tROAS, always adjust both campaigns equally — otherwise the campaign with higher tROAS will receive less spend.- Use your standard tROAS as the baseline for both campaigns
- Only adjust tROAS if both campaigns deviate from target, and always by the same margin
- Align the actual tROAS value with your business objectives and historical performance
Troubleshooting
ROAS Below Target After 60+ Days| Check | Action |
|---|---|
| Inventory distribution | Review placement report — is spend concentrated in low-performing channels? |
| Signal configuration | Confirm audience signals match campaign objectives and product type |
| tROAS setting | Increase by 10–20% to push Google toward higher-quality inventory |
| Conversion tracking | Verify all conversions are being captured correctly |
| Possible Cause | Solution |
|---|---|
| Budget too low | Increase daily budget to accelerate data collection |
| tROAS too restrictive | Lower tROAS to allow broader bid participation |
| Insufficient demand | Verify products have adequate search volume |
| Too many campaigns | Consolidate — small budgets spread across many campaigns prevent learning |
| Possible Cause | Solution |
|---|---|
| Signals too restrictive | Broaden from Top 30% → Top 50%, or extend lookback from 30 → 60 days |
| Audience size too small | Check signal size in Innkeepr dashboard |
| Signals not applied | Verify audiences are linked to correct asset groups |
| Insufficient time | Some configurations need 60+ days — wait before concluding |