Google Ads
The Provider Is Connected. One Merchant-ID Mismatch Can Break the Redemption Trail.

Updated: November 2, 2026
Validate the external redemption provider and merchant identifier as one joined identity before launch. Google Ads API v26.1 exposes Local Services redemption-provider information, including the provider and external merchant ID. The connection is only useful when that identifier matches the provider’s record exactly and stays stable through booking, redemption, refund and reporting.
Why provider configuration is an identity problem
A redemption trail spans at least two systems: Google Ads and the external provider. The provider name may be correct while the merchant ID points to the wrong location, uses a legacy value, or differs in punctuation or casing from the provider’s canonical record.
Those errors are dangerous because the campaign may still run. The failure appears later as missing redemptions, unattributed value or an unexplained reconciliation gap. Treat the identifier as a financial join key, not a descriptive label.
Define the cross-system identity contract
| Checkpoint | Required evidence | Failure to prevent |
|---|---|---|
| Provider | Supported provider value and active connection | Using a similarly named integration |
| Merchant ID | Exact provider-side canonical identifier | Copying a display name or stale ID |
| Location scope | Mapped business and service area | Joining the wrong branch |
| Redemption event | Provider transaction reference and timestamp | Recording an untraceable aggregate |
| Reversal | Refund or cancellation status | Leaving reversed value in results |
Run merchant-ID QA before activation
- Export the canonical merchant record from the provider.
- Verify the supported provider value in the Google Ads integration.
- Compare the external merchant ID character for character.
- Confirm the mapped location and service-area ownership.
- Complete a test booking and redemption when supported.
- Trace the transaction through reporting and reversal states.
- Lock the identifier and document the change-control owner.
Test the join, not only the configuration screen
A saved field proves that the platform accepted a value; it does not prove the provider resolves that value to the intended merchant. The strongest QA follows one test transaction from ad or lead context to provider record, redemption status and finance-ready output.
If redemptions disappear, compare IDs, location scope, timestamps and provider status before changing campaign bids. An identity failure can look like media underperformance even when customer demand is unchanged.
Redemption identity controls
- Use immutable IDs rather than display names.
- Restrict who can change provider mappings.
- Version legacy-to-current merchant-ID migrations.
- Normalize time zones before daily reconciliation.
- Remove cancellations and refunds from net value.
- Alert on sudden redemption-count discontinuities.
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
Connect this operating review with MTC’s external redemption reconciliation guide. 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 the provider, merchant ID, location, activation date, test transaction, responsible owner and provider-side evidence in one launch manifest. Screenshots alone are insufficient if they do not show the canonical record.
Revalidate after provider migrations, business-location changes or integration upgrades. A stable campaign configuration can still break when the provider changes the identity behind the join.
Frequently asked questions
Is the merchant name sufficient for reconciliation?
No. Use the exact external merchant identifier required by the provider and preserve the mapping.
What is the best launch test?
Trace one supported test transaction through provider recognition, redemption and reporting.
Should a missing redemption trigger bid changes?
Not until identity, provider status and tracking continuity have been checked.
