GA4 MENA E-Commerce Event Taxonomy & BigQuery Schema
Deploy a complete GA4 e-commerce event taxonomy and BigQuery SQL suite built specifically for Middle East retail, COD, and BNPL.
Problem it addresses
Build an exhaustive GA4 e-commerce taxonomy and BigQuery SQL schema pack for MENA: 1) Extended e-commerce event taxonomy specification (including cod_placed, cod_verified, bnpl_selected, delivery_completed), 2) BigQuery SQL query templates that require adaptation and validation against your GA4 export schema (unnesting events, customer lifetime value, blended attribution), 3) GTM Web and Server-Side container examples that require review and configuration before import.
Who it is for
PRO operating in high-growth e-commerce, digital publishing, and direct-response marketing across Saudi Arabia, UAE, and Egypt.
What is inside
Key files listed in the README repository architecture:
data/event_dictionary.csvdocs/mena-payment-tracking-guide.mddocs/mena_custom_dimensions.mdgtm/gtm-web-container-template.jsonLICENSEREADME.mdschema/ga4_mena_event_schema.jsonschemas/ga4-event-taxonomy.jsonSOURCES.mdsql/bigquery_ecommerce_unnester.sqlsql/customer_ltv_analysis.sqltests/test_data_integrity.py
How to evaluate and use it
- Read the README first and confirm that the documented problem matches your use case.
- Inspect the listed files to find the data, tools, templates, and tests relevant to your task.
- Follow the repository’s Quick Start and check prerequisites before running commands.
- Compare outputs with documented examples and review limitations before using them in a decision or client workflow.
Quick Start from the README: python -m unittest discover -s tests
Scope and limitations
- Required E-Commerce Parameter Consistency: Enforces official items array schemas with item_id, item_name, price, and item_category.
- Currency Normalization: Multi-currency regional transactions (SAR, AED, EGP, USD) must be explicitly passed at event level to prevent conversion distortion.
- BigQuery Partitioning: Daily event export partitions require integer transaction timestamps (event_timestamp) for performant querying.
This page summarizes the available documentation; it does not establish performance or business results. Verify data and prerequisites before use.