Install and verify campaign conversion tracking

Why use this

1. An advertiser may see conversions in one interface but not know whether the right event reached the intended destination. Duplicate triggers, consent behavior or a mismatch between test and production can make an apparently active tag misleading.

2. This job could specify the intended event path and the evidence needed to review it. Keeping the configuration, consent assumptions and destination observations separate helps an owner avoid relying on a superficial 'tag fired' signal.

Why an agent / simpler alternative

Useful judgment

Map business events to reporting destinations, identify duplicate or missing paths and distinguish technical checks from valid measurement.

Simpler alternative

Use a platform's supported integration when its default event mapping fits the site's needs.

Unsuitable when

Tracking would collect unauthorized personal data, bypass consent or change production without approval.

Proposed inputs

1. Name

   Measurement brief

   Owner

   Authorized owner

   Minimum scope

   Named conversion events and intended destinations

   Quality check

   Define event meaning and permitted data fields

2. Name

   Tracking context

   Owner

   Site/analytics owner

   Minimum scope

   Relevant tag rules and consent-state descriptions

   Quality check

   Identify environment, duplicates and privacy boundaries

Access and setup — proposed or unknown

Proposed minimum

1. Start with a paper event-flow map and synthetic payloads; no tag installation, publishing or live tracking.

Compatibility unknowns

1. Current tag-manager behavior, platform receipt visibility, consent support and runtime compatibility are unknown.

External actions requiring approval

1. Production tag changes, data transmission, expanded tracking and account permissions require explicit approval and privacy review.

Expected deliverable and review checks

Proposed artifact

Proposed tracking configuration with event-to-destination map and unexecuted verification checklist.

Critical checks

1. Check event identity, deduplication, environment and consent behavior; distinguish firing, transport and destination recognition.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   A confirmation page triggers twice

   Why it matters

   Reported conversions can be inflated

   Proposed response

   Specify a deduplication check and inspect trigger overlap.

2. Signal

   A denied-consent case is untested

   Why it matters

   The setup may transmit beyond permitted scope

   Proposed response

   Include that state explicitly and stop rollout until reviewed.

Effort and cost — unknown

Setup work

1. Define event semantics and permitted collection.

Ongoing review

1. Review authorized test evidence and changes to site flows.

Unknowns

1. Destination delays, consent requirements, attribution behavior and implementation costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent three event paths: successful submission, reload duplicate and denied-consent visit; review expected behavior without sending events.

Acceptance checks

1. Identify duplicate risk; preserve consent boundaries; require destination evidence; publish nothing.

Stop conditions

1. Stop if data fields, privacy authority or production-change approval are unclear.

Limits

1. A technical event check cannot establish lawful tracking, accurate attribution or campaign effectiveness.