UAE analytics is measuring purchase at order placement and calling it revenue — a COD non-delivery rate of 15-25% means the real number is significantly lower

A GA4 fulfilment conversion event is implemented using Shopify's order fulfilment webhook and the GA4 Measurement Protocol. When an order status changes to fulfilled in Shopify — either manually or through your logistics provider's integration — the webhook sends a POST request to a server-side function. That function calls the GA4 Measurement Protocol endpoint with a custom event (typically named "order_fulfilled") and passes the order value, order ID, and product details as event parameters. The event appears in GA4 as a custom event and can be marked as a conversion. Because it fires from the server via the Measurement Protocol, it is not dependent on the buyer's browser being open at the time of fulfilment.

Importing GA4 events into Google Ads requires linking your GA4 property to your Google Ads account through the Google Ads admin under Linked Accounts, then navigating to Goals in Google Ads, selecting Conversions, and choosing Import from Google Analytics 4. You select the specific GA4 conversion event you want to import — in the UAE COD context, this should be the fulfilment event rather than the purchase event — and set it as the primary conversion action for the relevant campaigns. Once the import is active, the standalone Google Ads conversion tag on the order confirmation page should be switched to "Secondary action" status so it no longer influences bid optimisation.

Arabic-language buyer segmentation in GA4 uses the browser_language dimension, which captures the language setting of the buyer's browser. In GA4's Explore section, create a custom segment with the condition browser_language contains "ar" to filter sessions from Arabic-language browsers. Apply this segment alongside a country filter (country equals "United Arab Emirates") to isolate UAE Arabic-language sessions. For acquisition channel analysis, create a comparison view with the Arabic segment applied to see which channels are driving Arabic-language traffic and what their conversion rates are relative to English-language sessions. This segmentation approach does not require changes to your Shopify store's language settings.

Meta Conversions API for a Shopify store targeting UAE buyers is implemented through either Shopify's native CAPI integration or a server-side GTM setup. In Shopify, go to your Facebook and Instagram sales channel settings and enable server-side event sharing at the maximum data sharing level. This sends purchase, add to cart, and initiate checkout events from the server to Meta's CAPI endpoint. For UAE campaigns specifically, verify that your Meta Pixel and CAPI are sending the client_ip_address and client_user_agent parameters with each event, as these improve event match quality for UAE buyers whose browser privacy settings may prevent cookies from being set. Event match quality below 6.0 in Meta's Events Manager indicates insufficient parameter data and should be investigated.

True ROAS for a UAE campaign with significant COD volume is calculated as: (fulfilled order revenue attributed to the campaign) divided by (campaign spend). The denominator is straightforward — use your Google Ads or Meta Ads spend figure for the campaign. The numerator requires the GA4 fulfilment event to be imported into Google Ads and tagged with the campaign source. To calculate this without the Measurement Protocol fulfilment event in place, you can apply an offline correction: take your GA4 purchase event revenue attributed to the campaign and multiply by (1 minus your COD non-delivery rate). If your overall COD non-delivery rate is 20% and GA4 attributes AED 50,000 in purchase revenue to a campaign, the corrected fulfilled revenue figure is AED 40,000. Dividing by campaign spend gives you the true ROAS. Implementing the fulfilment event removes the need for this offline correction.