Multiple GA4 Properties

Overview

Convert can work with multiple GA4 properties on the same page. Understanding how event interception works is key to correct configuration.

How It Works

Concept	Details
Event name	Imported GA goals are just event names (text). Convert does not store the source GA4 property.
`send_to` check	When the tracking script sees an event: if `send_to` is present, it must match the measurement ID configured for the experience. If `send_to` is absent, the event is accepted regardless of source.
Revenue events	Additionally require valid `transaction_id` (non-empty) and `value` > 0.

Frequently Asked Questions

Does the imported goal have to come from the same GA4 property?

No. Importing registers the event name only. The GA4 property used in the GA UI and the property configured in Convert's integration are independent. What must match (when present) is the send_to value in the live event.

What if the integration points to a different property?

Same rule: if the event's send_to does not equal the project/experience-level measurement ID, Convert ignores the event.

Revenue goal with track_revenue on but using another property?

A revenue event is rejected when either send_to mismatches the integration property, or transaction_id / value are invalid.

Practical Guidance

Simplest setup: Point the Convert GA4 integration (project or experience level) to the same measurement ID the page uses in its gtag / send_to calls
Multiple properties coexisting: Either:
- Fire a duplicate event without a send_to parameter, or
- Ensure the send_to value matches the measurement ID configured for the specific experience

Under these conditions, Convert and GA4 operate correctly with multiple properties.