Skip to content
Astera Technology

Match advertised session options to landing-page options

Check each advertised option and qualifier against the supplied landing inventory.

List advertised option tuples

Synthetic creative offers weekday online session W and weekend in-person session K, both demo-only. Landing inventory contains W online demo and K online demo. Local readiness needs the same session/modality/demo tuple. The K modality differs; no real availability or commercial promise is made.

Advertised/landing option tuples
OptionAdvertisedLanding
WWeekday/online/demoSame
KWeekend/in-person/demoWeekend/online/demo
Download editable CSV ↓

Compare landing choices

  1. Read approved synthetic option list
  2. Compare all tuple fields
  3. Keep W match
  4. Resolve K modality before readiness

Do not silently change the creative or landing offer to make tuples match without a supplied offer decision.

How many advertised options match fully?

Show the worked answer

One of two, W. K matches weekend/demo but fails the in-person modality.

Resolve missing or contradictory options

Filled campaign-operation checks
CaseDecision or resultReason
Compare option IDs onlyInsufficientK fields contradict
Compare full tupleFind K exceptionModality mismatch
Download editable CSV ↓

Keep the mismatched field in the readiness request. A landing page containing the same session code can still describe a different offer.

Related resources

Development services →