LaneyGuide
Browse featuresServer-side conversion tracking and delivery

Verify conversion delivery and provider receipt

Check the source reservation or purchase ID, state, customer, and time.

How-toVerified Oct 12, 2026Owner Laney Product

After this taskTransmission, receipt, deduplication and reporting delay are distinguished.

Starting conditions and inputs

Verify configuration and identify one source event.

Values for this task

entry_url, source_id, event_id, destination_id, event_time, provider_events_url

Command sequence

open "$entry_url" && snapshot -i

get text body

# Outside browser: If the current UI does not expose the outbox, obtain the matching event-ID delivery result from the operator.

open "$provider_events_url" && snapshot -i

get text body
Ref targets and expected results
#Command / refTarget and verification
1get textRead source reservation or purchase ID, amount and time.
2Outside browserIf the current UI does not expose the outbox, obtain the matching event-ID delivery result from the operator.
3openEvent receipt page for that destination
4get textCompare receipt and amount for the same event ID.

Check the result

Transmission, receipt, deduplication and reporting delay are distinguished.

Resuming after interruption

Read the same source IDs again. Check organization and time range before treating an empty result as missing data.

Check the source outcome

Check the source reservation or purchase ID, state, customer, and time. For purchases, compare amount and currency with payment evidence. A pending source does not establish a completed conversion.

Check sending evidence

Check event delivery and the destination account with your connection contact. Distinguish successful, pending, and failed transmission. Retain event IDs and errors. Successful source storage does not prove external delivery.

Check provider receipt

Find the same event in provider testing or diagnostics. Compare its ID, type, amount, and time. Provider receipt and attributed conversions in advertising reports are separate results.

Investigate gaps and duplicates

For gaps, check customer matching, permitted fields, destination, and delay. For duplicates, compare browser and server event IDs. Do not resend the same event under new IDs before checking its existing result.

On this page