🡠 Back
How AFRUS records your donors' actions? Part 1 of 3
Reading time
1
Tracking
June 19, 2026
afrus.ai
Where to set up tracking codes, how data submission works, and what event is recorded at each step of the funnel.
📍
Where do I set up the tracking codes?
Two places in the AFRUS panel — each with a different role
⚠️ Important: you must set up tracking in both places: on the landing page and in the widget. The landing captures the session start (UTMs, cookies). The widget uses that data to send each funnel event. If you only configure one, you lose critical information.
📄 Part 1A — Landing Page Setup
Path: Fundraising → Landings → edit the landing → Advanced Data tab
Step 1 — Fundraising → Landings
Step 2 — Edit the landing → Advanced Data
| Field | What to enter | What it's for |
|---|---|---|
| Analytics track | Select Google Analytics | Activates GA4 tracking on the landing page |
| Google Analytics ID | G-XXXXXXXXXX | Injects gtag.js, reads UTMs and creates the _ga cookie — the thread connecting the entire GA4 session |
| Facebook Pixel | Your Meta Pixel ID | Captures the _fbc cookie when a visitor comes from an ad (?fbclid=). Without this, Meta Ads attribution degrades |
🧩 Part 1B — Widget Setup
Path: Widgets → edit the widget → left sidebar → Advanced
Step 1 — Go to Widgets
Step 2 — Edit widget → Advanced section
| Section | Fields | What it's for |
|---|---|---|
| Facebook CAPI | Pixel ID + Access Token | AFRUS sends funnel events to Meta CAPI using the _fbc cookie from the landing. Both fields are required. |
| Protocolo de medición | Measurement ID + API Secret | AFRUS sends events to GA4 using the client_id from the _ga cookie created on the landing. Both fields are required. |
| Google Tag Manager 4 | GTM Container ID (GTM-XXXXXX) | If you manage tracking through GTM, enter the ID. AFRUS will publish events to the dataLayer. |
✅ Recommended minimum setup: Landing: Facebook Pixel ID + Google Analytics ID · Widget: Pixel ID + Access Token + Measurement ID + API Secret
🔄
How does AFRUS send data?
Server, browser and GTM dataLayer
🖥️ From the server
- Triggered after the payment gateway confirms the payment
- Works even if the donor closes the browser
- Envía a: Meta CAPI GA4
🌐 From the browser
- Triggered in real time at each widget step
- Publishes events to the
dataLayerfor GTM - Envía a: Meta CAPI GA4 GTM
🍪 Cookies AFRUS preserves
_ga — Google AnalyticsGA4 session client_id. AFRUS reads it in each event to maintain attribution. Falls back to UUID if not present.
_fbc y _fbp — Meta_fbc is created when the visitor comes from an ad (?fbclid=). _fbp identifies the browser for cross-event attribution.
⚠️ Watch out for cookie banners: if your site blocks _ga or _fbc before the user accepts, attribution breaks mid-funnel.
💡 In summary: AFRUS sends each event from the server and browser, and publishes it to the
dataLayer. The three signals are coordinated so Meta counts a single conversion with maximum data quality.📊
The donor's journey step by step
Event names in AFRUS, GTM, Meta and GA4
1
Widget view — First contact
The donor sees the widget on your landing page.
AFRUS: startGTM: startMeta: ViewContentGA4: view_item
2
Amount selection — Concrete interest
The donor chooses how much to donate.
AFRUS: add_to_cartGTM: add_to_cartMeta: AddToCartGA4: add_to_cart
3
Contact details — Lead captured
The donor enters name and email. Lead created in the database when information is valid.
AFRUS: generate_leadGTM: generate_leadMeta: LeadGA4: generate_lead
4
Payment start — High intent
The donor moves to the payment screen.
AFRUS: begin_checkoutGTM: begin_checkoutMeta: InitiateCheckoutGA4: begin_checkout
5
Payment method — One step before
The donor selects their payment method (card, bank transfer, etc.). Field available in dataLayer: ecommerce.payment_type.
AFRUS: add_payment_infoGTM: add_payment_infoMeta: AddPaymentInfoGA4: add_payment_info
★
Donation confirmed! ⭐ — Conversion
The payment gateway confirms the charge. Meta receives the real amount (value), currency, content_type (one_time or recurring) and frequency. For asynchronous payments (Niubiz, PIX, boleto), AFRUS waits for real confirmation.
On the thank-you page: GA4 receives
purchase with a unique transaction_id. Meta receives Purchase deduplicated against AFRUS CAPI.AFRUS: purchaseGTM: purchaseMeta: Purchase/DonateGA4: purchaseConversión ★
⚡ For registration widgets (no payment): the
register event is sent to Meta (Lead) and GA4 (sign_up), but is NOT published to the GTM dataLayer. Use generate_lead as a GTM trigger instead.📋 Reference table — all names by platform
| Paso | AFRUS | GTM | Meta | GA4 | Tipo |
|---|---|---|---|---|---|
| Widget view | start | start | ViewContent | view_item | Interest |
| Amount selection | add_to_cart | add_to_cart | AddToCart | add_to_cart | Interest |
| Contact details | generate_lead | generate_lead | Lead | generate_lead | Lead |
| Checkout start | begin_checkout | begin_checkout | InitiateCheckout | begin_checkout | High intent |
| Payment method | add_payment_info | add_payment_info | AddPaymentInfo | add_payment_info | High intent |
| Donation ⭐ | purchase | purchase | Purchase/Donate | purchase | Conversion ★ |
| Registration ⭐ | register | no publicado | Lead | sign_up | Conversion ★ |
🧩 Events by widget type
| Widget type | Funnel events |
|---|---|
| All | start · add_to_cart · generate_lead |
| Donation (one-time or recurring) | start · add_to_cart · generate_lead · begin_checkout · add_payment_info · purchase ★ |
| Registration / Signup | start · add_to_cart · generate_lead · register ★ (sin dataLayer) |
Continue to Part 2 → GTM, configuration and deduplicationPart 2 →
Related Tutorials
Tracking
June 22, 2026
Benefits, Verification, and FAQ Part 3 of 3
What's new in your campaigns, how to verify everything is working, known limitations, and FAQ.
afrus.ai
Tracking
June 22, 2026
GTM, Setup, and Deduplication Part 2 of 3
How to use your GTM tags with AFRUS events, scenario-based setup, and how to avoid double-counting conversions.
afrus.ai