CAPI daga saba & bin abubuwan da suka faru
A tsallake masu toshe talla da ƙuntatawar ITP ta tura zirga-zirgar MousePlayer ta kwantenar First-Party Server-Side GTM na wurin, a bi cikakken nazarin cinikin lantarki.
1. Bayanin yanayin bin diddigi
MousePlayer V2 yana gabatar da ingantaccen Event Router da yake ba da damar sarrafa yadda bayanai suke tafiya daga burauzar mai amfani zuwa sabobinmu. Ana iya zaɓar yanayi uku dabam:
- Web Only (tsohon saiti): Yana watsa duk bayanai ta WebSockets kai tsaye zuwa MousePlayer. Ya fi dacewa da kallon kai tsaye, amma yana iya shafuwa da masu toshe talla masu ƙarfi.
- Yanayin Hybrid: Mafi kyawun ɓangarorin biyun. Yana aika ƙananan bayanan matsayin manuni/gungurawa ta WebSockets don kallon kai tsaye mai santsi, yayin da manyan sauye-sauyen DOM da abubuwan da suka faru na musamman ake haɗawa a rukuni a tura su cikin tsaro ta Server-Side GTM na wurin ta HTTP POST.
- Pure CAPI: Haɗa bayanai a rukuni ta HTTP POST 100%. Mafi girman sirri, babu WebSockets, first-party gaba ɗaya. Bayani: kallon kai tsaye yana kashe a wannan yanayin.
2. Saita Google Tag Manager (shawara)
Hanyar da ta fi sauƙi don aiwatar da yanayin Hybrid ko Pure CAPI ita ce amfani da samfuran GTM Community na hukuma namu. A sauke fayilolin .tpl da ke ƙasa a shigo da su cikin wuraren aikin GTM.
Mataki 1: saita abokin hulɗa & tag na saba
A kwantenar Server-Side GTM, a shigo da samfurin Ingest Client . A saita shi ya saurara a hanyar musamman (misali, /mp_capi). Sannan, a shigo da Connector Tag, a saita shi ya yi aiki a abin da ya faru na mouseplayer_batch , a girka kwantenar.
Mataki 2: saita tag na Web GTM
A kwantenar Web GTM, a shigo da SDK Tag. A zaɓi “Configuration & Initialization” a matsayin Tag Type, a shigar da Channel ID, a zaɓi Yanayin Hybrid, a manna URL na wurin ƙarshen ssGTM (misali, https://metrics.yourdomain.com/mp_capi).
3. Girkawa da hannu (ba tare da GTM ba)
Idan an fi son rubuta rubutun kai tsaye, dole a ayyana object na window.mp_config kafin loda snippet na bin diddigi.
4. Bin funnel na cinikin lantarki
A bi cikakkiyar hanyar abokin ciniki. Amfani da daidaitattun sunayen abubuwan da suka faru yana ba MousePlayer damar samar da kyawawan rahotannin funnel na cinikin lantarki ta atomatik a wurin aikin yanar gizo. Duk abubuwan da suka faru suna dacewa gaba ɗaya da yanayin CAPI da Web-Only.
1. view_item
A tayar da wannan abin da ya faru idan mai amfani ya kalli takamaiman shafin samfuri.
2. add_to_cart
A tayar da wannan abin da ya faru idan mai amfani ya ƙara abu a kwandon sayayya.
3. begin_checkout
A tayar da wannan abin da ya faru idan mai amfani ya je allon checkout.
4. purchase
A tayar da wannan abin da ya faru bayan nasarar biyan kuɗi ko tabbatar da oda.
5. Abubuwan da suka faru na musamman & samun masu sha’awa
Ba a iyakance ga cinikin lantarki ba. A bi aika fom, rajistar wasiƙar labarai, ko hulɗar musamman ta manhajar yanar gizo.
Samun masu sha’awa (aika fom)
A tayar da wannan abin da ya faru idan mai amfani ya aika fom na tuntuɓa ko ya nemi tayin farashi cikin nasara.
Hulɗar UI ta musamman
A fahimci yadda masu amfani suke hulɗa da abubuwa masu sarkakiya kamar kalkuletoci, tagogi, ko sauya shafukan zaɓi.
6. Iyakokin sigogi & jagorori
Nau’in bayanai: MousePlayer yana gano nau’ikan sigogi ta atomatik. A aika lambobi a matsayin integers ko floats (misali, 150.00, ba "150.00") don kunna cikakkiyar tace lambobi (misali, “Price > 100”) a dashboard.
| Doka | Bayani |
|---|---|
| Tsawon sunan abin da ya faru | Iyakar haruffa 128. A yi amfani da snake_case don mafi kyawun karantawa (misali, user_signup). |
| Tsawon mabuɗin siga | Iyakar haruffa 64 ga kowane sunan mabuɗi (misali, transaction_id). |
| Ƙimomin rubutu | Ana yanke sigogin rubutu zuwa haruffa 255 don tabbatar da mafi kyawun aikin rumbun bayanai. |
| Sirrin bayanai | Kada a aika bayanan gane mutum (PII) kamar ɗanyen adireshin imel, ainihin sunaye, ko kalmomin sirri a matsayin sigogin abin da ya faru. |