Configure conversion destinations and matching
Identify the receiving account and destination, such as a Meta dataset or Google Ads conversion action.
After this taskDestination and field scope match, with one identifiable test event.
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
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.
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.
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.
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.
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.