How Excluded Sales Channels work in Aghanim Connect Google Analytics plugins

Aghanim Connect exposes an Excluded Sales Channels setting in both the Google Analytics plugin and the Google Analytics for Firebase plugin. This setting controls which purchase channels are not sent by that plugin.

Available channel options

The available sales-channel values are:

• game_hub
• checkout
• android_sdk
• checkout_link

How to think about the two plugins

• Google Analytics plugin: used for the GA4 web stream.
• Google Analytics for Firebase plugin: used for the Firebase iOS / Android streams.

Because the two plugins send data to different destinations, it is normal for them to use different Excluded Sales Channels configurations.

Mirror-image configuration pattern

In many setups, the two plugins are configured as mirror images of each other: each plugin excludes the sales channels that should belong to the other destination. This helps ensure that each purchase lands in exactly one analytics stream instead of being duplicated.

A confirmed example configuration is:

• Google Analytics plugin — exclude checkout. This keeps Checkout-originated purchases created via server-to-server flow out of the GA4 web stream.
• Google Analytics for Firebase plugin — exclude game_hub and checkout_link. This keeps Game Hub and checkout-link purchases out of the Firebase iOS / Android streams.

With that setup, the intended result is:

• Game Hub purchases go to the GA4 web stream only.
• Native Checkout purchases go to the Firebase iOS / Android streams only.
• The same purchase should not appear in both destinations.

user_id note

If you use ga4_user_id, the expected outcome is that user_id is sent as that value across the relevant streams, rather than falling back to a prefixed player identifier format.

Important rollout note

If you are changing both channel routing and user_id mapping, deploy the routing change first or ship both together. Otherwise, duplicate purchase rows may begin sharing the same final user_id, which can contaminate per-user revenue reporting.

Verification checklist

• Confirm user_id has the expected value across all target streams.
• Confirm the same transaction_id does not appear twice in unintended streams.
• During validation, avoid over-filtering on transaction_id until you confirm how each platform emits it.