Day 1 is assigned to a specific date by the 2ME team based on your batch start date.
📅 Check your confirmation email for your full task schedule.
Haven't received it? Email hello@clarigital.com and we'll sort it out quickly.
📅 Week 2 · Tuesday
day-08
What is Clarigital?.
Today you'll learn: what Clarigital is and why businesses pay for it — explained so clearly you could teach it to your parents by tonight.
⏱ ~20 mins
📖 Read + Quiz + Submit
✅ Need 3/5 to unlock
🔒 Tuesday only
Week
Week 2 of 8
Day
8 of 56
Program
2-Month Program
📖 Read This First — About 8 Minutes
After iOS 14, a Pixel-only setup misses 30-50% of conversions. CAPI restores what the browser can no longer see.
The Meta Pixel is a JavaScript snippet that fires in the user's browser and sends conversion events to Meta when a user takes an action (purchase, form submit, add to cart). Before iOS 14.5, this worked reliably. After iOS 14.5, Apple's App Tracking Transparency framework caused users to opt out of tracking, breaking browser-based Pixel tracking for a significant portion of iOS users.
The solution is the Conversions API (CAPI) — a server-to-server connection that sends conversion events directly from the business's server to Meta, bypassing browser-based tracking restrictions entirely. CAPI doesn't rely on cookies or browser permissions because it operates at the server level. The complete tracking setup uses both: Pixel for browser-level events, CAPI for server-level events, with deduplication to prevent double-counting.
🕵️
Think of tracking like a surveillance system. The Pixel is a camera inside the store - it sees what happens when customers are in the building. CAPI is a camera at the server room - it records what the system itself processes regardless of what customers do with their browsers. After iOS 14, some customers started blocking the in-store camera. The server room camera still records everything.
🌐
Meta Pixel (Browser-Side)
JavaScript snippet fires events from the user's browser: PageView, ViewContent, AddToCart, InitiateCheckout, Purchase. Affected by iOS ATT and browser ad blockers.
🖥️
Conversions API (Server-Side)
Sends the same events directly from the web server to Meta. Not affected by browser privacy settings. Requires developer implementation or Shopify/WooCommerce plugin.
🔢
Deduplication
When both Pixel and CAPI fire the same event, Meta needs to deduplicate to avoid counting it twice. Use matching event_id parameters in both Pixel and CAPI calls.
📊
Event Match Quality
Meta rates how well you can match events to real users (0-10 score). Send hashed customer data (email, phone, name) with CAPI events to improve match quality and attribution.
🔮 Aggregated Event Measurement (AEM): Meta also introduced AEM which limits event tracking to 8 conversion events per domain and prioritises them in a defined order. For Pixel-only setups, this means you must choose your 8 most important events and rank them by priority. CAPI reduces this restriction's impact but AEM still applies to your reporting window configuration.
💡
Read the reference page below before taking the quiz.
Why did the Meta Pixel become less accurate after Apple's iOS 14.5 update?
A
A: Meta changed how the Pixel works in response to iOS 14
B
B: Apple's App Tracking Transparency requires users to opt in to tracking, causing many iOS users to block browser-based tracking
C
C: The Pixel was removed from the iOS App Store
D
D: iOS 14.5 blocked Meta from operating in the App Store
OK Apple's ATT framework requires apps to ask users for permission to track them across other apps and websites. A majority of iOS users chose to opt out, breaking the Pixel's cookie-based tracking for those users. CAPI bypasses this by operating server-to-server.
NO Apple's ATT required opt-in for tracking across apps and websites. Most iOS users opted out, breaking cookie-based Pixel tracking for them. CAPI bypasses this by operating at the server level.
Question 2 of 5
How does the Conversions API solve the iOS 14 tracking problem?
A
A: It forces iOS users to accept tracking cookies
B
B: It sends conversion events directly from the web server to Meta, bypassing browser-based tracking restrictions entirely
C
C: It replaces the Meta Pixel entirely
D
D: It uses a different type of cookie that iOS 14 permits
OK CAPI operates server-to-server. When a purchase happens, the server directly POSTs the event data to Meta's API. No browser cookie. No iOS permission needed. The data is sent before it even reaches the user's browser, making it immune to browser-side privacy restrictions.
NO CAPI sends events server-to-server. No browser involvement means no cookie restrictions, no iOS ATT interference. The event is sent directly from the business server to Meta.
Question 3 of 5
What is event deduplication and why is it necessary when using both Pixel and CAPI?
A
A: Removing duplicate keywords from ad campaigns
B
B: Preventing Meta from counting the same conversion event twice when both Pixel and CAPI report it
C
C: Consolidating multiple ad accounts into one
D
D: Merging similar custom audiences
OK If both the Pixel and CAPI fire for the same purchase, Meta would count it as 2 conversions. Deduplication uses a unique event_id that's the same in both the Pixel and CAPI calls - Meta uses this ID to identify and count the event only once.
NO Deduplication prevents double-counting when both Pixel and CAPI fire for the same event. A shared event_id in both calls tells Meta it's the same event, so it counts it once.
Question 4 of 5
What data should be sent with CAPI events to improve Event Match Quality (EMQ)?
A
A: The user's browser type and version
B
B: Hashed customer data: email address, phone number, and name to help Meta match the event to a specific user profile
C
C: The exact time the user spent on the product page
D
D: The campaign ID that drove the conversion
OK Hashed PII (email, phone, name) sent with CAPI events allows Meta to match the server-side event to a specific user profile even without a cookie. Meta hashes this data before matching. Higher EMQ means better attribution accuracy.
NO Hashed email, phone, and name improve Event Match Quality by allowing Meta to identify which user performed the action even without a cookie. Always send available customer data with CAPI.
Question 5 of 5
What is Aggregated Event Measurement (AEM) and how does it affect Pixel setup?
A
A: A tool for measuring cross-channel attribution
B
B: A Meta framework limiting tracking to 8 prioritised conversion events per domain, requiring domains to be verified in Meta Business Manager
C
C: A method for measuring the impact of video ads
D
D: A GA4 feature for aggregating event data across properties
OK AEM limits Pixel tracking to 8 conversion events per verified domain. You must rank them 1-8 by business priority. Events beyond 8 won't be trackable. Domain verification in Meta Business Manager is required before any Pixel events will function post-iOS 14.
NO AEM limits you to 8 prioritised conversion events per verified domain. You must verify your domain in Meta Business Manager and rank your 8 most important events. This is required for Pixel tracking post-iOS 14.
–of 5
Answer all 5 questions, then check your score.
✏️ Your Task
🔒
Score 3/5 to unlock this
Complete the quiz above first. The moment you score 3 or more, this section unlocks.
🏅
🎉 Day 8 — done!
Day 9 opens Wednesday.
📝 Today's Task
Someone in your family runs a small business. In 3–4 sentences, explain Clarigital to them like you're actually WhatsApp-ing them right now. Your own words — not copied from the page.
Start like this: "So there's this platform I was reading about — it's basically for businesses that get too many WhatsApp messages to handle manually. It lets them..."
0 / 800
From your registration confirmation email. Can't find it?
Submitting before 11 PM IST on your assigned Tuesday counts as Day 8 complete.
Week 2 · Coming Tomorrow
Day 9 — Google Tag Manager - Container Setup & Tag FiringOpens Wednesday on your assigned date.