Ecommerce PPC strategy: purchase tracking, campaigns and contribution
An ecommerce PPC strategy needs reliable purchase measurement, accurate product data and campaign roles that can be evaluated against the store’s economics. Validate the conversion and value before changing bids, then assess Search, Performance Max and budget with their attribution limits visible. Reconcile platform results with store orders and contribution. Named case reports can inform questions without predicting another retailer’s outcome.

The short version
- Validate the event. Purchases, identifiers, value and goals need a consistent definition.
- Give campaigns a purpose. Search priority depends on query identity and eligibility; exclusions do not prove zero overlap.
- Maintain product data. Technical limits and eligibility are prerequisites to inspect, not guarantees of revenue.
- Read attributed results carefully. ROAS differs from contribution, profit and incremental sales.
- Use cases with scope. Astrid & Miyu and IKEA are first-party reports with specific periods, currencies and measurement definitions.
Connect ecommerce PPC strategy to purchase economics
An ecommerce PPC strategy connects the catalog, purchase measurement, campaign roles, spending limits and commercial contribution. Start by checking that the events and values used for bidding represent the intended purchase. Then assess structure, feed and budget against the store's economics. Clicks and platform-attributed ROAS are useful observations, but neither establishes profit or incremental sales.
Ecommerce PPC management needs a shared definition of an order and its value. Agree how discounts, shipping, tax, returns and cancellations appear in the store and reporting. Identify which system supplies each field and who can investigate a mismatch. A growing conversion count is hard to interpret if its event definition changed during the comparison.
Organize the work into connected responsibilities, with a review cadence chosen for the store's rate of change:
- Campaign purpose: distinguish brand demand, category/product queries, catalog coverage and bounded experiments.
- Measurement: validate purchases, identifiers, value, currency and the bidding goals actually applied.
- Product data: maintain accurate identifiers, variants, content, availability and landing-page consistency.
- Budget: plan permitted spend, pacing and a decision process for seasonal or promotional changes.
- Commercial review: compare attributed results with store orders and contribution, noting limits to the inference.
The named case studies illustrate specific reporting and campaign issues. They are Resourcifi's first-party accounts, with their own periods and attribution, rather than independent benchmarks. If the team lacks the capacity to inspect these inputs, evaluate the responsibilities described in hiring a PPC specialist before choosing a management arrangement.
Give each campaign a clear job
Choose a campaign structure that makes its jobs and overlaps understandable. A candidate design separates branded Search, non-brand Search, catalog-led Performance Max and a bounded test. This is a planning framework, not a required account template. Confirm the catalog, query evidence, conversion goals and budget justify each component before creating it.
| Campaign | Job | Key settings |
|---|---|---|
| Brand Search | Address branded-query demand | Separate reporting; assess query identity, eligibility and overlap |
| Non-brand Search | Test a category/product query and destination plan | Match types, relevant queries, landing pages and eligibility |
| Performance Max | Use the goal-based campaign across available inventory | Goals, product scope, destinations and applicable brand controls |
| Test cell | Investigate a defined expansion question | Agreed allocation, comparison, acceptance and stop condition |
Google documents prioritization between eligible Search keywords and Performance Max search themes.4 Exact query identity and eligibility matter: an eligible identical exact-match Search keyword can receive priority under the documented rules. That does not mean Search always owns every relevant query or that a campaign label guarantees which one serves.
Inspect the current eligibility and configuration when observed delivery differs from the plan. Check the keyword, ad, budget and relevant settings rather than interpreting every overlap as a bidding failure. Phrase or broad coverage and Performance Max themes need their own review; do not assume an exact-match rule applies unchanged to every match type.
When branded traffic is handled separately, Google recommends brand exclusions for Performance Max.5 Verify the control's actual inventory and configuration, then inspect reporting. It is a way to manage the intended boundary, not proof that all overlap or cannibalization has disappeared. Brand and non-brand reporting also cannot by itself establish which orders would have occurred without advertising.
Use product groupings the merchandising team can maintain: category, availability, promotion or a consistently defined margin group. Check which products and destinations each campaign can use. A clean structure should help explain what changed and why; excessive subdivision can create management work without answering a useful decision.
Choose the Search and Performance Max roles
Use Search or Performance Max according to the demand, inventory and controls the account needs. Search can express a deliberate keyword and landing-page plan. Google describes Performance Max as a goal-based campaign spanning its advertising inventory.3 Neither label establishes a preferred budget share, a guaranteed efficiency advantage or incremental sales.
| Question | Search | Performance Max |
|---|---|---|
| Inventory | Assess the configured Search delivery | Goal-based delivery across Google inventory |
| Planning inputs | Keyword/match and destination plan | Goal, product and asset scope to investigate |
| Identical query | Eligible identical exact-match priority follows the documented rules | Delivery depends on eligibility and the relevant prioritization conditions |
| Controls to inspect | Keywords, eligible ads, budget and destinations | Applicable exclusions, product scope, goals and destinations |
| Candidate role | Deliberate query/category coverage | Coverage across the configured campaign inventory |
| Review risk | Confusing brand demand or constraints with causal performance | Misreading attributed results or unintended goal/product scope |
Compare the role, measurement and product mix before comparing ROAS. Brand demand, customer familiarity, different products and attribution can influence the reported result. A higher-return campaign is not automatically the best place for the next unit of spend, and an aggregate channel gap does not identify the causal contribution of either campaign.
Questions before expanding Search
- Which queries and products have evidence of useful orders, and which landing pages support the intent?
- What is eligible and actually serving, including any budget or policy constraints?
- Can the team explain brand versus non-brand results and the return/cancellation treatment?
- Does the selected bid strategy meet its campaign-specific eligibility and data conditions?
Questions before expanding Performance Max
- Are the conversion goals and reported values the ones the store intends to optimize?
- Are the catalog and destinations eligible, accurate and appropriate for the intended scope?
- Which exclusions and other available controls implement the planned boundary?
- What reporting and test design will show whether added spend serves the commercial objective?
Google's target-ROAS guidance has campaign-specific eligibility requirements and uses reported conversion values.6 Verify the current requirement for the chosen type rather than applying one conversion-count threshold to every account. A target is a bidding objective, not a promised return.
Validate purchases and preserve measurement history
Validate the conversion definition before changing bids. Check the goals applied to the campaign, the purchase event, unique identifiers, value and currency. A platform can report a strong ratio for an event that does not represent the commercial outcome. Reconcile the event with the store and preserve the measurement history when changing the setup.
Resourcifi's IKEA UAE case distinguishes app-open conversions from purchase revenue.2 The older 2024 definition reports 475,000-plus app opens and 28.1x ROAS; the January-November 2025 purchase period reports AED 34.9 million on about AED 5.7 million spend at 6.12x.2 Read it as a named first-party measurement example: ratios based on different event/value definitions are not comparable returns on the same outcome. A corrected purchase measure also remains attributed revenue, rather than independently measured incremental sales.
For a store review, follow the actual order through confirmation, event delivery, reporting and any cancellation or return. Test repeated page loads, delayed delivery and the same purchase arriving through more than one path. Document what each platform deduplicates and what remains an application responsibility.
Purchase measurement checks
- Goals: inspect the conversion actions used for bidding in the actual campaign. Google distinguishes primary actions from secondary observation actions, with custom-goal conditions.8 Decide deliberately whether an action belongs in the commercial objective; “purchase only” is a design choice, not a universal platform rule.
- Transaction identity: send a transaction-specific identifier. Google Ads uses IDs to detect duplicates for the same conversion action; a static identifier can cause real orders to be undercounted.9
- GA4: its purchase event includes
transaction_idto help avoid duplicate purchase events.11 Consistent identifiers aid reconciliation but do not automatically reconcile every platform's counting and attribution. - Value: establish the included components, discount and currency. Test ordinary, discounted and partially refunded orders using the store's actual handling.
- Change record: keep the effective date and affected campaigns when goals, tags or values change. Assess a suitable observation period from the workflow and data rather than assuming a universal learning duration.
Compare store, GA4 and Ads order/value reports over a matched period. Investigate consent, timezone, attribution window, event delivery and return treatment before declaring every gap an error. Fix a confirmed instrumentation problem, then establish the new baseline instead of claiming an improvement from a changed denominator.
Maintain accurate and eligible product data
Treat product data as an operating dependency. Confirm that the item, identifier, variant, price, availability and landing page agree, then investigate eligibility issues and content. Merchant Center's product-data specification defines the fields and technical constraints; satisfying them does not guarantee a ranking, impression or revenue lift.10
Prioritize an actionable feed queue: products that cannot serve, mismatched commercial information, missing or incorrect identifiers, confusing variants and content that fails to describe the item. Keep the merchandising source and update process visible so a repaired field does not revert on the next import.
| Attribute | Google's rule | What to do |
|---|---|---|
| Title | Maximum 150 characters | Accurately identify the item and variant; the limit is not a target length |
| Description | Maximum 5,000 characters | Describe the actual item and verify the applicable field format |
| GTIN | Applicability depends on the item and specification | Use the real assigned identifier where required/applicable |
| Custom labels 0-4 | Up to 5 per product; 1,000 unique values per label across the account | Maintain a clear grouping vocabulary and verify campaign use |
For titles and descriptions, state the product accurately and distinguish relevant variants. Avoid promotional or keyword-heavy text that conflicts with the field rules or landing page. For identifiers, use the appropriate real product information rather than inventing values to clear a diagnostic. Check the current specification for the country, category and selected program.
For management labels, agree a small vocabulary that someone can maintain: for example, an explicitly defined contribution group, season or clearance status. Verify the selected campaign's supported grouping and filtering behavior. A label called “high margin” is useful only if its underlying cost and return assumptions are current and consistently applied.
Inspect the whole item journey after a feed change: selection, destination, variant and checkout. If the store experience is the problem, evaluate the Shopify product-page and conversion work alongside the ads. A campaign adjustment cannot establish that a mismatched or unusable product page is fixed.
Allocate budget against a defined question
Allocate budget from campaign purpose, measured outcomes, product economics and uncertainty. Preserve a controlled way to test an expansion and a reason to stop it. A case study's channel allocation is historical context, not a default budget split for another retailer.
| Engine | Share of spend | Revenue | Share of revenue | ROAS |
|---|---|---|---|---|
| Search | 28% | £4.2M | about 49% | 10.33x |
| Performance Max | 62% | £4.1M | about 48% | 4.66x |
| Shopping + Demand Gen | 10% | £0.2M | about 2% | n/a |
| Total | 100% | £8.49M | about 100% | 5.95x |
The Astrid & Miyu case describes a particular campaign mix and reported results.1 Its spend and revenue shares do not isolate incrementality or establish that reallocating another account to the same percentages will reproduce the outcome. Rounded channel amounts also need to remain distinct from an exact total.
Before a seasonal increase, confirm stock, delivery capacity, landing pages, promotion dates and purchase measurement. State the spend authority and commercial limit. Use the campaign's actual delivery and conversion lag to plan review, rather than changing several inputs and attributing the next result to whichever change seems plausible.
For most average-daily-budget campaigns, Google's billed limits are 2 times the average daily budget on a day and 30.4 times it over a month. Pay-for-conversions campaigns have no daily limit under the stated rules, and changes or mid-month starts alter the applicable calculation. Served cost can differ from billed cost.13 Model the applicable rule for the actual campaign instead of treating the displayed daily average as a hard daily cap.
For a test, choose the question, allocation, comparison and evidence required to continue. Keep the budget and measurement boundary clear enough to investigate failures. Report changes in product mix, promotions and tracking alongside spend so the review can distinguish a commercial shift from a campaign effect.
Explain revenue, attribution and contribution
Report attributed purchases, value and ad spend alongside store reconciliation and contribution. Keep brand, campaign and product context visible. ROAS is attributed revenue divided by ad spend; it is not profit, a causal estimate or a complete view of the cost to acquire an order.

For an illustrative product group, assume each $100 of revenue leaves $40 after the included non-ad variable costs. If all of that contribution is available for ads, the simplified break-even ROAS is 1 / 0.40 = 2.5. Returns, fulfillment, fees and other relevant costs must already be treated consistently; excluded costs or a required remaining contribution increase the needed return. This is chosen arithmetic, not a recommended universal target.
Use a contribution basis appropriate to the decision and explain its included costs. Do not call a gross-margin shortcut full profitability. When setting a target ROAS, verify how the platform represents the target and whether the conversion value corresponds to revenue, margin or another agreed value. Keep that definition visible in the report.
What the commercial review should contain
- Comparable values: orders, attributed revenue, spend and ROAS by meaningful campaign and brand boundary, with periods and currency.
- Delivery context: Performance Max channel reporting shows delivery across channels and inventory, rather than causal lift.12 Interpret the report within that attribution scope.
- Reconciliation: store, GA4 and Ads counts and values, with differences investigated and explained.
- Commercial inputs: product mix, order value, returns, stock constraints and the chosen contribution calculation.
- Decisions: changes made, evidence for the next action, unresolved uncertainty and the spending authority involved.
If reported ROAS rises while store results do not, investigate the definitions and attribution as well as product mix and timing. That pattern is a question to examine, not proof of one particular tracking fault. Incrementality requires an appropriate causal evaluation beyond attributed reporting.
Interpret the Astrid & Miyu and IKEA cases
Read the Astrid & Miyu and IKEA UAE cases as different named examples: campaign mix and reporting in the first, conversion definition in the second. Resourcifi publishes both as first-party cases. Preserve their periods, currencies and attribution, and use them to frame diligence rather than forecast another store's result.
| Measure | Astrid & Miyu | IKEA UAE |
|---|---|---|
| Issue described | Campaign mix and attributed results | 2024 app-open conversions distinguished from later purchases |
| Comparison boundary | January-November 2025 program | 2024 app-open versus January-November 2025 purchase definitions |
| Reported revenue | GBP 8.49 million | AED 34.9 million, purchase period |
| Reported ad spend | GBP 1.43 million | About AED 5.7 million, purchase period |
| Reported ROAS | 5.95x blended; Search 10.33x; PMax 4.66x | 6.12x purchase-based; not like-for-like with older 28.1x |
| Other reported fields | Additional summary fields lack a documented common order denominator; no derived order/AOV claim | 44,000+ conversions; AED 776 average; AED 128 cost/conversion |
| Interpretation | Attributed case result, not profit or incremental sales | Changed definition and period; no isolated causal lift |
For Astrid & Miyu, ask how brand, product mix, seasonality and campaign attribution relate to the published result. A channel with a higher reported ROAS does not establish the best marginal allocation or the sales that would disappear without it. The Astrid & Miyu case study supplies the named context.
For IKEA UAE, ask exactly which conversion and value were counted before and after the change. Preserve that discontinuity rather than treating two unlike ROAS figures as a continuous performance improvement. The IKEA UAE case study addresses that measurement issue; the purchase result still has attribution limitations.
Bring the purchase definition, current campaign goals, feed diagnostics, store reconciliation and spending constraints to a PPC management discussion through the contact page. Those inputs help identify which problem should be addressed first and what evidence would support the next budget decision.
Ecommerce campaign and measurement questions
What belongs in an ecommerce PPC strategy?
Does Search always take priority over Performance Max?
How do we check purchase conversion tracking?
How much can Google spend above a daily budget?
Is a 2.5x ROAS profitable?
Can we copy the Astrid & Miyu campaign allocation?
Why is the IKEA ROAS comparison qualified?
Like this? Get more from Resourcifi in Google Search.
Sources
- Resourcifi, Astrid and Miyu PPC Case Study. Resourcifi reports GBP 8.49 million revenue on GBP 1.43 million spend and 5.95x blended ROAS for January-November 2025. The channel view reports approximately GBP 4.2 million Search, GBP 4.1 million Performance Max and GBP 0.2 million Shopping/Demand Gen revenue. Search is reported at 28% of spend/10.33x ROAS and PMax at 62%/4.66x. The page also reports 112,000 conversions, GBP 73.96 AOV and 4.66% conversion rate.
- Resourcifi, IKEA UAE PPC Case Study. Resourcifi reports replacing the 2024 app-open conversion definition with purchase events for IKEA UAE. The older case description reports 475,000-plus app opens at AED 0.04 and an inflated 28.1x ROAS not representing purchase revenue. Its January-November 2025 purchase period reports AED 34.9 million revenue, about AED 5.7 million spend, 6.12x ROAS, 44,000-plus conversions, AED 776 average transaction and AED 128 cost per real conversion. Monthly reported revenue is AED 2.0 million in February and AED 6.1 million in November, roughly 3x.
- support.google.com, About Performance Max campaigns - Google Ads Help. Performance Max is a goal-based campaign type spanning Google's advertising inventory.
- support.google.com, About keyword matching options - Google Ads Help. Google Ads documents query matching and prioritization between eligible Search keywords and Performance Max themes.
- support.google.com, About brand exclusions - Google Ads Help. Google recommends brand exclusions when branded traffic is handled separately from Performance Max.
- support.google.com, About Target ROAS bidding - Google Ads Help. Target ROAS uses reported conversion values and has campaign-specific eligibility requirements.
- support.google.com, About primary and secondary conversion actions - Google Ads Help. Google distinguishes primary conversion actions used for bidding from secondary actions used mainly for observation.
- support.google.com, Use a transaction ID to minimize duplicate conversions - Google Ads Help. Unique transaction IDs let Google Ads detect duplicate conversions for the same action.
- Google Merchant Center Help, Product data specification. The current product specification sets a 150-character title maximum, 5,000-character description maximum, up to 5 custom labels per product named 0 through 4, and 1,000 unique values per custom label across the Merchant Center account. GTIN applicability is conditional and should use the actual assigned identifier.
- developers.google.com, Recommended events | Google Analytics | Google for Developers. GA4's purchase event has a transaction_id parameter to help avoid duplicate purchase events.
- support.google.com, About the channel performance report - Google Ads Help. Performance Max channel reporting shows delivery across channels and inventory.
- Google Ads Help, About spending limits. For most average-daily-budget campaigns, billed daily limits are 2 times the budget and monthly limits 30.4 times it, with changes and mid-month starts affecting applicable limits. Pay for Conversions has no daily spending limit but retains the specified monthly limit. Served costs can exceed a limit while billed costs remain constrained. Ad scheduling does not reduce the monthly cap to the number of scheduled active days.
Paid & growth
How to hire a PPC expert: evidence, scope and judgment
Learn how to hire a PPC expert through measurement evidence, relevant account judgment and clear scope. Agree budget auth...
Read guide →
AI in marketing
AI search optimization tools: compare coverage, cost and measurement
Compare AI search optimization tools by prompt coverage, billing units and exports. Build an auditable answer panel and c...
Read guide →
AI in marketing
AI use cases in marketing: tasks, approval and measurement
Compare AI use cases in marketing through task evidence, campaign approval and outcome measurement. Plan a bounded workfl...
Read guide →
AI in marketing
How to use AI in marketing: workflows, review and measurement
Learn how to use AI in marketing through workflow ownership, content review, campaign controls and attribution checks tha...
Read guide →
Mobile & apps
25 mobile app ideas worth building, with costs and revenue models
25 mobile app ideas across AI, health, fintech and commerce, with the core features, a sourced build cost range and the m...
Read guide →
Strategy, architecture & ops
Agentic design patterns: choose the right control flow
Compare agentic design patterns by task, evidence, tools and control flow. Test retrieval, routing, agents, cost and reco...
Read guide →
Agents & RAG
Agentic RAG: step selection, retrieval patterns and evaluation
Understand agentic RAG through routing, corrective retrieval and evaluation, with practical tests for step selection, sou...
Read guide →
Agents & RAG
AI agent development cost: build effort, usage and operating work
Estimate AI agent development cost from scoped build tasks, model calls, tools and upkeep, with a worked support budget a...
Read guide →
Agents & RAG
AI agents for customer service: define actions and verify resolution
Build AI agents for customer service with explicit identity, knowledge, action and handoff checks. Measure verified resol...
Read guide →
