Skip to main content

Madabina Store Integrations: Pixels, GA4, GTM, and Events

· 7 min read
Madabina Editorial Team
Madabina Editorial Team
Seller and developer education

A storefront connected to separate marketing and analytics measurement destinations.

Madabina’s merchant store settings provide five measurement integrations: Meta/Facebook Pixel, TikTok Pixel, Google Analytics 4 (GA4), Google Tag Manager (GTM), and the OpenAI measurement pixel. They report storefront activity to the destinations you configure. They do not, on their own, prove that a cash-on-delivery order was confirmed or delivered. This guide maps the current events, shows how to check a setup, and explains the limits before you use the numbers for marketing decisions.

Where the settings apply​

Open the merchant workspace for the store you intend to measure, then open Settings → Integrations. The identifiers are saved per store. Check the selected store before editing; a setting on one store should not be treated as a setting for another. The fields accept a Meta Pixel ID, TikTok Pixel ID, GA4 measurement ID, GTM container ID, or OpenAI pixel ID. Use the ID from the matching provider account. Do not paste a script or access token into an ID field.

Only configure destinations that you manage. Pixel IDs are browser-visible identifiers rather than passwords, but avoid publishing real IDs in screenshots, examples, or support posts. Review the privacy notice and any consent obligations that apply to your audience and the provider terms before enabling tracking.

What Madabina currently sends​

The current storefront implementation maps four actions to provider events. A destination may report, attribute, or name each event differently according to its own product and settings:

  1. Store or category listing viewed: GA4 receives view_item_list; Meta and TikTok receive ViewContent; OpenAI receives contents_viewed. The GTM data layer event is view_item_list.
  2. Product viewed: GA4 receives view_item; Meta and TikTok receive ViewContent; OpenAI receives contents_viewed. The data layer event is view_item.
  3. Checkout begins: GA4 receives begin_checkout; Meta and TikTok receive InitiateCheckout; OpenAI receives checkout_started. The data layer event is begin_checkout.
  4. Order created successfully: GA4 receives purchase; Meta receives Purchase; TikTok currently receives CompletePayment; OpenAI receives order_created. The data layer event is purchase.

The data layer also carries Madabina’s original event name alongside the ecommerce object. That helps a GTM container tell a product view from a listing view even when they share a provider event name. The actual data shape is limited to the fields implemented in the storefront; do not assume this is a full marketing CRM or a server-to-server conversions API.

A four-stage numbered diagram showing the order of storefront listing, product, checkout, and created-order events.

The event names shown in the diagram are identifiers. The article text above describes the corresponding customer actions.

The five integrations and what each is for​

Meta/Facebook Pixel​

Enter the Pixel ID supplied by Meta. The current Madabina mapping sends ViewContent for listing and product views, InitiateCheckout when checkout starts, and Purchase after a store order is successfully created. These signals can help Meta report ad interactions and support eligible audience or optimization features. A browser event is not an independent confirmation of payment or delivery; compare it with the store’s order records.

TikTok Pixel​

Enter the TikTok Pixel ID. Madabina currently sends ViewContent, InitiateCheckout, and CompletePayment. TikTok’s updated event guidance renamed CompletePayment to Purchase. TikTok says existing setups remain operational and legacy events are converted on its backend for reporting, audience creation, and optimization; newly created pixels should use Purchase. The Madabina setting accepts an ID; it does not let you rename the emitted event. Check the current TikTok standard-event guidance and supported event list when planning a new campaign.

Google Analytics 4​

Enter the GA4 measurement ID beginning with G-. Madabina sends view_item_list, view_item, begin_checkout, and purchase at the corresponding storefront actions. Google’s GA4 ecommerce documentation describes the standard event conventions. Use GA4 to inspect activity and funnels, then reconcile order and delivery outcomes separately. A purchase event emitted after order creation is not evidence that a COD parcel reached its customer.

Google Tag Manager​

Enter the GTM container ID beginning with GTM-. When the container is present, Madabina pushes the event name, an ecommerce object, and a madabina_event value into dataLayer. Use Google’s data layer guide to understand how custom events trigger tags. In GTM, map only the events and parameters you need; keep preview/debug mode private and publish only reviewed changes.

GTM is a routing and tag-management layer, not an analytics destination by itself. A tag in the container can send to Meta or GA4. If you also enter the same destination’s direct ID in Madabina, the same user action can be sent through both routes and counted twice. Choose one route per destination unless you have a deliberate, tested deduplication design.

OpenAI measurement pixel​

Enter the OpenAI pixel ID for the store. Madabina currently reports contents_viewed, checkout_started, and order_created with the supported content shape. See the official OpenAI Measurement Pixel and supported events references for the event schema and current platform behavior. The order_created name means an order was created; it does not mean cash was collected or a parcel was delivered.

Privacy and checkout-start behavior​

The browser checks the order form’s phone field locally for the minimum digit threshold used by the current implementation, then emits one checkout-start event. It does not place the entered phone number in that event payload. This describes the Madabina tracking bridge; it does not describe every script you may add through GTM or the data practices of the destination platforms. Review all tags you control and avoid sending direct identifiers unless you have a clear, permitted reason and the appropriate safeguards.

A safe way to check the setup​

  1. Confirm that you selected the right store and entered the provider’s correct ID format.
  2. Check the provider’s browser/debug tool: GA4 DebugView or Tag Assistant, Meta Events Manager, TikTok Events Manager, and OpenAI’s current pixel diagnostics where available.
  3. Open a public listing and one product page. Confirm that one expected view event arrives at the intended destination.
  4. Start the checkout form only as far as needed to see the checkout-start signal. Do not submit someone else’s contact details.
  5. Validate an order-created signal only with an order you are authorized to place and prepared to manage as a real store record. Never create an artificial “sale” to improve ad reporting.
  6. Compare events with Madabina’s order list and fulfillment status. Check for duplicate events before interpreting campaign performance.

Diagram separating browser events, order records, confirmation, delivery, and financial reconciliation.

Use platform diagnostics for event delivery and store records for COD confirmation, fulfillment, and financial outcomes.

Read the signal in context​

Use event reports to find where shoppers leave the storefront journey. Use order records to see which submitted requests became valid orders, then fulfillment data to determine which orders were delivered and paid. Keep these datasets side by side, with consistent date ranges and status definitions.

For practical setup order, continue with the Madabina store launch guide. For offer, content, and channel planning, read the online store marketing guide; for campaign costs and COD outcomes, see the media-buying guide.

Sources​