Server-side conversion tracking and delivery

A pipeline joining acquisition and CRM outcomes and managing conversion events, values and delivery results.

Acceptance

Reconcile source, event IDs, time, deduplication, delivery and monetary definitions.

Boundary

Acceptance is signal delivery; bidding outcomes or ROAS are not guaranteed.

Configure conversion destinations and matching

[blocked]

Identify the receiving account and destination, such as a Meta dataset or Google Ads conversion action.

Starting conditions and inputs

Prepare advertising access and the permitted external-data scope.

Values for this task

entry_url, organization_id, destination_id, event_definition, source_type, source_url

Command sequence

text

open "$entry_url" && snapshot -i
# Outside browser: Provide the integration operator with destination, event kind and customer-matching scope, then complete authentication.
snapshot -i
click "$conversion_account" && snapshot -i
get text body
open "$source_url" && snapshot -i
get text body
# Outside browser: Use the conversion-delivery test to verify the same event ID.

open "$entry_url" && snapshot -i
# Outside browser: Provide the integration operator with destination, event kind and customer-matching scope, then complete authentication.
snapshot -i
click "$conversion_account" && snapshot -i
get text body
open "$source_url" && snapshot -i
get text body
# Outside browser: Use the conversion-delivery test to verify the same event ID.

Ref targets and expected results

#	Command / ref	Target and verification
1	Outside browser	Provide the integration operator with destination, event kind and customer-matching scope, then complete authentication.
2	`click` `$conversion_account`	Conversion connection account
3	`get text`	Read destination ID, organization and account scope.
4	`open`	Source record for the test conversion
5	`get text`	Compare event ID, source ID and permitted matching fields.
6	Outside browser	Use the conversion-delivery test to verify the same event ID.

Check the result

Destination and field scope match, with one identifiable test event.

Resuming after interruption

Read the same IDs again. Preserve correct settings and update only differences.

[blocked]

Identify the destination

Identify the receiving account and destination, such as a Meta dataset or Google Ads conversion action. Check advertising access and conversion setup separately. Compare destination IDs and permissions with your contact.

[blocked]

Choose source outcomes

Choose which inquiry, reservation, or completed-purchase states produce conversions. Do not treat receipt and completion as the same event. Verify completed purchases against actual amount and currency.

[blocked]

Define identity and deduplication

Confirm customer IDs, transaction IDs, attribution identifiers, and duplicate handling. Browser and server copies of one event need a shared identity. Limit exported customer fields to the organization’s reviewed scope.

[blocked]

Prepare a test event

Choose a synthetic customer and unique test event. Prepare the provider’s supported test or diagnostic view. Record amount, currency, and time. Confirm the test method so test results do not contaminate operating metrics.

Verify conversion delivery and provider receipt

[blocked]

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

Starting conditions and inputs

Verify configuration and identify one source event.

Configure conversion destinations and matching

Values for this task

entry_url, source_id, event_id, destination_id, event_time, provider_events_url

Command sequence

text

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

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 / ref	Target and verification
1	`get text`	Read source reservation or purchase ID, amount and time.
2	Outside browser	If the current UI does not expose the outbox, obtain the matching event-ID delivery result from the operator.
3	`open`	Event receipt page for that destination
4	`get text`	Compare 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.

[blocked]

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.

[blocked]

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.

[blocked]

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.

[blocked]

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.