Google Ads
Google Can Generate the Promotion Code. Your System Still Has to Reconcile the Redemption.

Updated: October 30, 2026
Treat every externally redeemed promotion code as a financial identifier, not a creative detail. Map the Google Ads promotion asset to the partner promotion ID, code source and code type, then reconcile issued, redeemed, refunded and rejected codes before using promotion performance to make budget decisions.
What Google Ads API v26.1 added
The October 28, 2026 v26.1 release added external redemption information to PromotionAsset. The fields identify the partner’s promotion ID, whether codes are single-use or multi-use, and whether the source is customer-uploaded or Google-generated.
Those fields improve traceability, but they do not automatically reconcile the partner transaction, order status or refund. The advertiser still needs a shared identifier and a process that connects ad delivery to the commercial ledger.
Define the redemption contract
| Field or event | System of record | Control |
|---|---|---|
| Partner promotion ID | Commerce or partner platform | Stable and immutable mapping |
| Code source | Google Ads configuration | Approved generation authority |
| Code type | Promotion policy | Single-use or multi-use rules |
| Redemption | Order system | Timestamp and order reference |
| Refund or reversal | Finance system | Value removed from net results |
Implement external redemption tracking safely
- Create the promotion in the commerce or partner system.
- Assign and validate the partner promotion ID format.
- Choose code source and use policy before asset creation.
- Store the Google Ads asset resource and partner ID together.
- Ingest redemption, rejection and refund events.
- Reconcile daily during launch and after expiration.
- Report net redeemed value separately from issued-code volume.
Separate promotional response from profitable demand
A code can be copied, shared or redeemed by customers who would have purchased anyway. Evaluate incremental orders, margin after discount, new-customer share and repeat value. Do not treat redemption count as automatic proof of media incrementality.
For multi-use codes, monitor velocity and concentration. For single-use codes, monitor issuance failures, duplicate attempts and unused inventory. A promotion can look weak because codes failed operationally rather than because the ad failed.
Controls that prevent reporting drift
- Use immutable IDs across systems.
- Normalize time zones and currency.
- Record expiration and eligibility rules.
- Remove refunded orders from net value.
- Restrict access to code-generation settings.
- Alert on redemption spikes and partner ID mismatches.
Run a pre-launch decision review
Build one realistic test case from the first row of the framework above, then follow it from the initial marketing signal through the customer action and the reporting record. Ask the channel owner, creative lead, analyst and conversion owner to review the same case independently. Each reviewer should be able to identify what was promised, what evidence supports it, what the customer can control and what event proves the outcome.
Record disagreements before launch. A difference in naming may look minor in a meeting, but it can split reporting, obscure a product limitation or produce a landing experience that answers a different question. Resolve the definitions in the campaign brief and measurement plan, then repeat the test on mobile, where context and controls are easier to lose.
Use a release gate instead of a vague best practice
Approve the work only when the offer facts, interaction state, conversion rule and downstream record reconcile. If any reviewer needs an unstated assumption to explain the result, the system is not ready. Assign an owner and a repair date for every exception, and preserve a small control group or annotated baseline where possible. That turns the launch into a measurable operating decision rather than a one-time interpretation of platform guidance.
Connect the decision to the rest of the system
Pair the reconciliation work with MTC’s raw-versus-adjusted conversion-value audit. The purpose of the link is operational: the upstream promise, measurement rule and downstream experience must describe the same outcome.
Document the learning, not just the result
Keep a launch manifest with asset ID, partner ID, code source, code type, discount economics, audience, start and end dates, and owner. Retain the exact configuration because the v26.1 fields are immutable after creation.
When the offer ends, close the loop with issued, redeemed, rejected, refunded and net-profitable counts. That final ledger is the evidence for future promotion strategy.
Frequently asked questions
Does Google Ads reconcile the final order automatically?
The API fields support external redemption identification; advertisers still need partner and commerce records for full reconciliation.
When should a code be single-use?
Use single-use when abuse, individualized eligibility or precise attribution matters more than broad shareability.
What is the most important reporting metric?
Net contribution after discount, refunds and media cost is more useful than raw code redemptions.
