Intercepting GA Events as Conversions

Overview

Convert's tracking script can intercept GA4 events fired on the page and track them as conversion goals. This requires specific conditions to be met.

Requirements for Conversion Events

For a GA event to be tracked as a Convert conversion:

1. The GA event must be imported in the Convert UI as a goal
2. send_to must match — If the event payload includes a send_to property, its value must exactly match the measurementId connected in the Convert UI at the experience level
3. At least one bucketed experience must be attributed to the goal connected to the intercepted event

If send_to is absent from the event, it is accepted regardless of which GA4 property fired it.

Additional Requirements for Revenue Events

For GA purchase events (revenue tracking), two extra conditions apply:

The event must also conform to the standard GA4 purchase event specification.

How send_to Matching Works

• Experiences auto-inherit the GA property from the project level but can be changed per experience
• A single experience can have a different GA property connected to it
• Importing GA goals registers only the event name (text) — it is not tied to a specific GA4 property
• The send_to check happens at runtime when the event fires on the page

Troubleshooting

If conversions are not being tracked:

1. Verify the GA event name is imported as a goal in Convert UI
2. Check if the event includes send_to — if so, confirm it matches the measurement ID in the experience settings
3. For revenue events, verify transaction_id and value are present and valid
4. Confirm at least one experience is bucketed and linked to that goal
5. Ensure the event follows the standard GA4 event specification