Events API & Conversion Tracking

First-party tracking

Our JavaScript tracker (or WooCommerce/Shopify integration) runs on your storefront, assigns a visitor key and session, captures UTM and click IDs from landing URLs, and sends events to EcomSolveBD servers. This is first-party, server-side processing — not a third-party pixel owned by EcomSolveBD on your domain for ads (though you may also run platform pixels separately).

Events we support

• Page View / landing page view
• View Content (view item)
• Add to Cart
• Begin Checkout
• Purchase (manual send from Orders for quality control)

Server-side delivery

After ingest, we map events to your configured conversion actions and send via Meta CAPI, TikTok Events API, and Google Ads uploadClickConversions. Uploads include click identifiers (gclid, gbraid, wbraid) and/or hashed email when available and when you have enabled enhanced conversions / user data features.

Attribution reporting

We unify spend and conversion data across platforms to calculate ROAS, CPA, and channel performance. Attribution uses click IDs, UTMs, and identity graph signals where configured — results are estimates subject to each platform's modeling.

Event match quality

Match quality improves when you send valid click IDs from ad clicks, consistent order IDs for purchases, and hashed email/phone normalized per platform rules. We hash PII using SHA-256 before transmission to Google/Meta/TikTok.

Consent

You are responsible for obtaining lawful consent from shoppers (cookie banner, privacy policy, regional requirements). Configure your storefront to fire tracking only after consent where required.

Dynamic remarketing

When enabled, cart events include product IDs (with optional prefix/suffix) in cart_data for Google dynamic remarketing. Merchant Center / feed settings must match your catalog.