Turn first-party consent into ad performance.
A consent-event audience is built from events that fire only after explicit consent — every record carries the consent state, the event signal, and the resolved identity.
Read the full version
arqam360.com/playbook
The 5-step workflow
Step 1
Capture consent.
Bilingual web banner OR native iOS sheet / Android dialog. Per-category toggles. Result: a per-visitor consent record (timestamp, IP, regulation context, method).
Step 2
Capture events.
Once consent = granted, the SDK auto-fires page_view, purchase, add_to_cart, lead. Every event is gated by category; no leakage.
Step 3
Stitch identity.
Anonymous device IDs merge into known identities the moment the user logs in. Deterministic match on email / userId — same person across surfaces.
Step 4
Build the segment.
Combine consent state with event criteria in a visual rule editor. consent.marketing = granted AND events.purchase ≥ 2
Step 5
Sync to ad platforms.
Server-side forward to 10 destinations (Meta CAPI · GA4 · sGTM · TikTok · Snap · LinkedIn · HubSpot · Mixpanel · BigQuery · Google Enhanced Conversions) with consent flags attached.
Web + mobile, same engine
Salla · Zid · Shopify · WordPress · Custom HTML
iOS SDK (Swift + SwiftUI) · Android SDK (Kotlin + Compose)
Why pixel audiences are failing
Most users opt out of ATT.
App Tracking Transparency makes cross-app tracking opt-in. Industry trackers report opt-in rates around 25%.
Consent Mode v2 is required.
Without it, Google Ads cannot attribute conversions from users who haven't opted in. Modeled conversions depend on the consent signal.
Five active regimes.
Saudi PDPL (active enforcement, 2024). UAE Federal Decree 45/2021. Egypt 151/2020. Bahrain 30/2018. Oman 6/2022.
Quickstart — one line per surface
Web
<script data-key="ak_..." src="cdn.arqam360.com/widget-v2.js"></script>
iOS
Arqam360.shared.configure(apiKey: "ak_...")
Android
Arqam360.configure(this, apiKey = "ak_...")