Idukki
Skip to content
Analytics + A/B testing

GA4 + Meta Pixel attribution, how Idukki forwards events

Where each event fires (view_item, add_to_cart, purchase), the schema we send and how to verify it in GA4 / Events Manager.

5 min read · last updated 2026-04
On this page

Idukki forwards every UGC interaction into your existing GA4 + Meta Pixel as first-class events. No extra tag manager rules required.

Events fired

  • idukki_widget_view, widget enters viewport
  • idukki_post_click, user clicks a tile
  • idukki_hotspot_open, user opens a product hotspot
  • idukki_add_to_cart, user adds a tagged product to cart from the widget
  • idukki_purchase, a session that touched a widget completes a purchase

Verify in GA4

Open GA4 → Realtime. Trigger a click on your widget on staging. The event should appear within 5 seconds with the correct collection ID and post ID parameters.

Attribution model

In Idukki, toggle between last-click, first-click and linear attribution. We expose the same event with model_attribution attached so you can replay history without re-instrumenting.

Was this page helpful?

Still stuck?

Email us at support@idukki.io or open the in-app chat. We answer within one working day.

Talk to a human

Related guides

4-min setupDTC + B2B brands37 KB runtimeReal G2 reviews

Stuck?

A real human is faster than a search box.

In-app chat replies under 5 minutes during EU + US business hours. Status of a ticket? Email support@idukki.io and we’ll surface it.

  • No credit card
  • Cancel anytime
  • SOC 2 + GDPR

Where Idukki ships

Same data model. Every surface a shopper meets.

We use cookies

We use essential cookies to run this site and optional analytics cookies to understand how it’s used. You can change your choice anytime in our privacy policy.

GA4 + Meta Pixel attribution, how Idukki forwards events. Help — Idukki