This PR will add an option to either enable UA, enable GA4 or enable both at the same time (although they would use the same tracking id which seems to work from the testing i've done) Config paths have been kept as is so it should not break existing installations (so long as no plugins have been made on the GAClient)

The old Model/GAClient had been renamed to Model/UAClient since this is the more appropriate name, other than that it shouldn't have changed.

Latest version is not working with Magento 2.4.4 and PHP 8.1

[09-Aug-2022 08:09:13 UTC] PHP Fatal error: During inheritance of IteratorAggregate: Uncaught Exception: Deprecated Functionality: Return type of TheIconic\Tracking\GoogleAnalytics\Parameters\CompoundParameterCollection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/domains/domain.nl/releases/20220809065139/vendor/theiconic/php-ga-measurement-protocol/src/Parameters/CompoundParameterCollection.php on line 95 in /var/domains/domain.nl/releases/20220809065139/vendor/magento/framework/App/ErrorHandler.php:61

The method random_int expects int as parameters. 1E8 and 1E9 result in floats, so they have to be cast. Otherwise, the whole thing runs into a type error

Not sure how to reproduce (yet), but some transactions are logged twice in Google Analytics. Many transactions also appear twice in the system.log with a few seconds apart, but most of them are shown only once in Google Analytics. So there might be some filtering/deduplication happening on the Google side.

[2021-02-04 09:31:35] main.INFO: elgentos_serversideanalytics_requests:  ["https://ssl.google-analytics.com/collect?ti=16000000118&tr=175&tt=30.37&ts=0.0000&ta=B2C&v=1&tid=UA-XXX-2&uip=92.xx.xx.xx&cid=xxx.xxx&dp=%2Fcheckout%2Fonepage%2Fsuccess%2F&pa=purchase&ec=Checkout&ea=Purchase&t=event&pr1id=sku.42&pr1nm=Product&pr1pr=175.0000&pr1qt=1.0000"] []
[2021-02-04 09:31:36] main.INFO: elgentos_serversideanalytics_requests:  ["https://ssl.google-analytics.com/collect?ti=16000000118&tr=175.0000&tt=30.3700&ts=0.0000&ta=B2C&v=1&tid=UA-XXX-2&uip=92.xx.xx.xx&cid=xxx.xxx&dp=%2Fcheckout%2Fonepage%2Fsuccess%2F&pa=purchase&ec=Checkout&ea=Purchase&t=event&pr1id=sku.42&pr1nm=Product&pr1pr=175.0000&pr1qt=1.0000&pr1ps=27432"] []

As you can see, both are very similar with a few tiny differences:

Rounding is different:

tr=175
tr=175.0000

tt=30.37
tt=30.3700

Item position is missing in the first:

pr1qt=1.0000"
pr1qt=1.0000&pr1ps=27432"

Again, not really sure if this is causing the issue or just coincidence. But leaving here for reference.

When an order is created with Creditcard, this message occurs:

For Analytics object, you must specify a value to be set for setAffiliation

I think that can only occur when $order->getStoreName() returns null. With iDeal this doesn't happen, but it does with CreditCard. Perhaps because the order is captured directly?

This might be depending on your use case, but if a customer has disabled Google Analytics (eg using Ublock or similar extensions), the _ga cookie is never set. This will prevent the order from dispatching to GA Measurement Protocol.

I understand that it's generally preferred to use the actual user/client ID but this is not always possible. In our case, we would rather still record the purchase in Analytics, so that the revenue is correct, even though it cannot be traced to any marketing action.

Excuse the mess of commits, feel free to squash 😅 This allows the ga_user_id to be saved to the quote by a headless frontend via GraphQL

This can then be passed on to the order to provide serverside tracking for this client id. This gets picked up in https://github.com/elgentos/magento2-serversideanalytics/blob/master/Observer/SaveGaUserId.php#L97 which was accidentally in there by accident.

This prevents https://github.com/elgentos/magento2-serversideanalytics/issues/5 from happening, even if its fault lies outside this module.

If for any reason, an even is already sent, it should not happen again. Otherwise the order might be tracked twice.