Documentation · 10 Playbooks
Admaxxer Playbooks
Ten evergreen playbooks for DTC marketing teams. Tactical recovery guides (iOS 17, BFCM), migration plans (GA4, Triple Whale), methodology deep-dives (geo-lift, subscription LTV), and product references (Maxxer AI ad ops, server-side CAPI). Each one is single-source-of-truth, premium-rendered for humans, and full-content for AI crawlers.
All 10 playbooks
iOS 17 Link Tracking Protection: How DTC Brands Recover Ad Attribution
iOS 17's Link Tracking Protection strips fbclid, gclid and other click IDs from links opened in Mail, Messages and Safari Private Browsing. No script can read an ID removed before the page loads. What you can recover is the match: keep the click IDs that do arrive, and send each order server-side with hashed customer data and the order ID as event_id.
BFCM Black Friday Attribution Playbook: 7-Day Tracking Plan for DTC Brands
Black Friday / Cyber Monday compresses a quarter of ad spend into 96 hours, and that is when a broken token, a missing pixel or a campaign stuck in learning costs the most. This playbook is a 7-day pre-BFCM checklist your team runs by hand, plus how to read Admaxxer's numbers on peak day and in the 30 days after.
GA4 vs Admaxxer for DTC Ecommerce: When to Switch and Why
Google Analytics 4 is free. It also samples large reports, caps event-level retention on the free tier, and has no built-in ad-spend joining. For DTC brands spending real money on ads, that gap shows up as misattributed campaigns. This playbook compares GA4 and Admaxxer on the metrics that decide DTC budget allocation, with a 30-day migration plan.
Click ID Server-Side Recovery: gclid, fbclid, ttclid for CAPI
gclid (Google), fbclid (Meta), ttclid (TikTok), msclkid (Microsoft) and other click IDs link an ad click to a conversion. This playbook shows the recovery pattern: capture click IDs at landing, keep them in first-party storage on your domain, join orders back to visits by hashed email, and send them to Meta and TikTok server-side. Forwarding to Google Ads is not available yet.
Subscription LTV Cohort Analysis: 30/60/90/180-Day DTC Subscriber Math
Subscription DTC brands (skincare clubs, supplements, pet food, coffee) cannot judge ad campaigns on first-order AOV: a $40 subscriber who renews eight times is worth far more than a $200 one-time buyer. This playbook lays out 30/60/90/180-day subscriber cohort math you build from your billing export, and how to cross-check it against Admaxxer's per-ad LTV.
Server-Side Conversion API Setup: Meta CAPI + TikTok Events API in One Hour
Meta's Conversions API and TikTok's Events API recover signal that iOS link stripping, Safari ITP and ad blockers suppress in the browser. This playbook walks the one-hour setup in Admaxxer (forwarding to Google Ads is not available yet): connect your ad accounts, pick your Pixel, send a test event, verify deduplication by event_id, then run a daily parity check by hand.
Geo-Lift Incrementality Testing: 14-Day True-ROAS Measurement Method
Last-click ROAS counts conversions that would have happened anyway. Geo-lift testing pauses spend in test regions, keeps it in matched control regions, and compares revenue. This playbook walks the design and the math, and how Admaxxer's geo-lift tests fit in: you pick the regions and pause the spend; Admaxxer fits a synthetic control and reports the lift with a p-value.
Multi-Currency Revenue Tracking: USD-Equivalent Consolidation for Global DTC
A DTC brand selling in USD, EUR, GBP, AUD and CAD has several revenue numbers, and ad accounts billed in yet another currency. This playbook covers how Admaxxer shows everything in one workspace display currency, where its exchange rates come from, how to pin your own rate, and how to separate currency movement from real growth in your own reporting.
AI Ad Operations with Maxxer: What's Automated and Where You Stay in Charge
Maxxer is Admaxxer's in-app AI agent. It reads your campaigns, ad performance and analytics (revenue, profit, LTV) and can pause, resume and change daily budgets on Meta and Google campaigns, but only after you confirm each change. This playbook explains exactly what Maxxer can do, what needs your confirmation, and what it cannot do at all.
Triple Whale to Admaxxer: A 30-Day Migration Playbook
Migrating off Triple Whale is straightforward in theory (install the pixel, connect your accounts), but the 30-day overlap is where the value hides: that is how long it takes to compare pixel events, re-baseline your reporting and get your team comfortable. This playbook is a week-by-week plan to migrate without losing a day of insight.
Frequently asked questions
- Which Admaxxer playbook should a DTC brand start with?
- Start with the iOS 17 Attribution Recovery playbook + the Server-Side Conversion API Setup playbook. Together they recover the ~30% of ad attribution that iOS 17 Link Tracking Protection silently strips and the additional ~15-25% that Safari ITP + ad-blockers suppress. Both are <60 minutes of setup work and the lift compounds across every other playbook.
- Are these playbooks generic articles or do they map to live Admaxxer surfaces?
- Both. Every playbook describes a tactic any DTC brand can apply with the right tooling. On Admaxxer, the same tactic is wired into a live surface: the BFCM playbook drives /alerts pre-BFCM recommendations; the geo-lift playbook is implemented at /incrementality; the AI ad ops playbook is the /chat agent (Maxxer). Reading the playbook tells you the theory; running it inside Admaxxer skips the engineering.
- How often are the playbooks updated?
- Quarterly review for facts that change (iOS releases, click-ID lists, ad-platform API versions, FX rate sources). The methodology playbooks (geo-lift, subscription LTV cohort math, MMM) are evergreen and only refreshed when the underlying statistics change. Each playbook surfaces its dateModified at the top — if a date is stale, flag it via /support.
- Can AI assistants (ChatGPT, Claude, Perplexity) cite these playbooks?
- Yes. Each playbook ships with Article + FAQPage + BreadcrumbList JSON-LD that matches the visible content (Google AI Optimization Guide §4), a single h1 with first-paragraph TL;DR (§3), semantic HTML5 landmarks (§2), and is listed in robots.txt + sitemap.xml + llms.txt (the three surfaces every AI crawler we know about consults). How Admaxxer is built for AI search is covered at /documentation/ai-optimization.
Want every playbook running in your dashboard?
Install Admaxxer's first-party pixel, paste your Meta + Google tokens, and the 10 playbooks above become live surfaces in your account — not just articles.