Migration · 12 min read
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.
The window is the playbook
The headline mechanic of this migration - connecting your accounts and installing a pixel - takes about an hour. The reason this playbook is 30 days long is that the value of the migration hides in the overlap: the time it takes to check the Shopify order import, compare Admaxxer's pixel data with Triple Whale's, and let your team cycle through their weekly reporting rhythm in both tools so the decision to retire Triple Whale is data-backed.
A same-day cutover gets you running on Admaxxer, but it gives you no leverage to investigate a discrepancy. If on day 7 your CFO points at a number and asks "why is this different from last week," you want both pixels still firing so you can pull the source data from both sides. The 30-day window buys you exactly that.
The other reason: attribution models differ. Your Triple Whale reports use one model and window; Admaxxer offers several models you can switch between. Without running both for at least 14 days, you cannot distinguish between a real change in attribution and the mechanical effect of a different model running on the same traffic.
From first connection to retirement, in four phases
Each phase has a clear goal and a quantitative exit criterion. You don't advance to the next phase until the exit criterion is met - that's what keeps the playbook honest against the temptation to rush the parity window.
| Phase | Goal + exit criterion |
|---|---|
Days 1-3 — Pixel install + connections | Get the Admaxxer pixel firing alongside Triple Whale's pixel, connect your store and ad accounts, and let the Shopify order import run. Exit: Shopify, Meta, Google Ads and (if you use it) TikTok show as connected on /integrations; the Shopify connection shows the order-history import running or done; the Admaxxer pixel fires on page views and purchases (checked in the browser's network tab). |
Days 4-7 — Shopify order check | Confirm the imported orders and the new orders arriving since you connected match what Shopify reports. Exit: order count and revenue match Shopify Admin for the period Admaxxer covers (about the last 60 days before you connected, plus every day since); any difference is explained (usually refunds, currency or a second store). |
Days 7-14 — Pixel parity | Run both pixels side by side for at least 7 days and compare daily orders, revenue and top sources with Triple Whale and with your store. Exit: daily orders and revenue agree within a few percent, or the difference is explained; known systematic differences (attribution model and window) are written down. |
Days 14-28 — Reporting parity + shadow | Run your team's weekly KPI report in BOTH tools. Have your ad ops team work from Admaxxer (dashboards, Ads Manager, Maxxer chat) for daily operations. Exit: the weekly report agrees on blended MER and the top-3 acquisition sources, or the differences are explained; the team is comfortable answering first-line questions in Admaxxer. |
The full 30-day timeline
Each row is an action and the canonical Admaxxer surface where you perform it. Copy this table into a Notion task list and tick rows as you complete them.
| Day + action | Surface |
|---|---|
Day 1 — Install the Admaxxer pixel on Shopify as a Custom Pixel (Settings -> Customer events). Optionally serve it from your own subdomain with a first-party tracking domain. | /documentation/install/shopify |
Day 1 — Connect Shopify. Admaxxer starts importing your recent order history automatically; progress shows on the Shopify connection. | /integrations |
Day 1 — Connect Meta (Connect with Facebook or a pasted token) and pick your Pixel if you want Admaxxer to send purchases server-side. | /integrations |
Day 1 — Connect Google Ads with Google sign-in. | /integrations |
Day 2 — Connect TikTok Ads with an access token and Klaviyo with a private API key, if you use them. | /integrations |
Day 3 — Open Ads Manager and check your Meta and Google campaigns appear with spend. Optionally ask Maxxer in /chat to list your campaigns. | /ads-manager + /chat |
Days 4-7 — Check the Shopify order import finished, then compare order count and revenue with Shopify Admin -> Analytics for the same days. | /dashboard |
Days 7-14 — Pixel parity window. Both pixels run side by side. Each morning, compare daily orders, revenue and top sources, and check the Tracking Health badge. | /marketing-acquisition |
Day 14 — Pick the Admaxxer attribution model closest to the one your Triple Whale reports use, so you compare like with like. | /documentation/attribution-models |
Days 14-21 — Run your team's weekly KPI report in BOTH tools. Compare blended MER, new-customer revenue and the top-3 sources. | Both tools |
Days 21-28 — Team works from Admaxxer for daily ad ops (dashboards, Ads Manager, Maxxer chat). | /dashboard + /ads-manager + /chat |
Day 29 — Export the Triple Whale reports you want to keep, then cancel the subscription. Leave the pixel for one more day in case you need to check something. | Triple Whale billing settings |
Day 30 — Remove the Triple Whale script from your store. Confirm it no longer loads in a fresh incognito session. Migration done. | Shopify Admin |
Why running both pixels at once is safe
The first concern every Shopify-savvy operator raises: "won't two pixels conflict?" They won't. Here are the three facts that make the parallel window safe.
- Separate namespaces. Admaxxer's pixel uses its own global name and its own storage keys (prefixed admaxxer), so it doesn't read or overwrite another analytics pixel's cookies or storage.
- Separate endpoints. Out of the box the Admaxxer pixel loads from and sends to admaxxer.com. With a first-party tracking domain it uses a subdomain you own (for example t.yourbrand.com) set up with one CNAME record. Either way it doesn't share requests with another pixel.
- Small extra weight. Running two pixels for a month adds one more small script to your storefront. Check your own page-speed numbers before and after install if you want to measure it.
How to check the Shopify order import
When you connect Shopify, Admaxxer imports your recent order history in the background: about the last 60 days, which is what Shopify shares with apps by default. Progress shows on the Shopify connection ("Importing order history...", then the number of orders imported). New orders arrive through Shopify's order notifications from then on. Older orders are not imported, and orders placed before the Admaxxer pixel was installed have no visitor journey, so attribution builds up from install day.
Once the import is done, pick a few days inside the covered period and compare each day's order count and revenue in Shopify Admin with Admaxxer's dashboard for the same days. If they don't match:
- Small order-count gap. Usually refunds or cancellations - Shopify reports treat them differently depending on the report. Compare gross order counts with gross, net with net.
- Revenue off by a few percent. Usually currency. Admaxxer records Shopify orders in your store currency and shows them in your display currency; if the two differ, amounts are converted (see /settings/exchange-rates). Compare in the same currency.
- Import failed or larger gaps. If the Shopify connection shows the import as failed, it shows the reason and a Retry button; a retry doesn't duplicate orders already imported. If the numbers are still off, check that you connected the right store, then contact support.
Days 7–14 — the parity check that protects the cutover
For at least 7 consecutive days, both pixels fire on every page view and every purchase. Each morning, open Sources & Attribution and compare:
- Orders and revenue. Admaxxer's daily orders and revenue against Triple Whale's and your store's. Larger gaps usually trace back to one of: one pixel firing on a page the other doesn't (a custom thank-you page, an off-Shopify subscription portal), or a consent banner holding back one pixel but not the other.
- Tracking Health badge. The badge on Sources & Attribution compares, per channel, the conversions Admaxxer's pixel attributed with the conversions the ad platform reports, and flags drift over 10% or 30%. See the tracking health reference.
- Attribution model output. The two tools' default models may differ. To compare like for like, pick the Admaxxer model closest to the one your Triple Whale reports use before pulling the parity report. Once both are on comparable models, the top-3 acquisition sources should broadly agree.
Why Triple Whale and Admaxxer disagree on top-source ranking
Check which attribution model and lookback window your Triple Whale reports use. Admaxxer lets you switch between several models on the same data, so you can pick the closest match for the parity window, then look at the others:
- Last click and first click — all credit to the final or the first touch.
- Linear — equal weight to every touch in the path (or every paid touch).
- Time decay — more weight to recent touches.
- Position-based — most credit to the first and last touch, the rest spread across the middle.
- Markov and Shapley — data-driven credit based on each channel's contribution to conversion paths. They need enough conversion paths to be stable.
See /documentation/attribution-models for the full breakdown and the cases each model is built for.
Connections don't carry over — reconnect each platform
You can't move connections from Triple Whale to Admaxxer. Instead, connect each platform in Admaxxer on /integrations. It takes a few minutes per platform. Connecting doesn't change your campaigns: Admaxxer only changes a campaign when you confirm it, in Ads Manager or through Maxxer.
If you want Admaxxer to send purchases to Meta or TikTok from the server, turn that on per connection — see the server-side conversion setup playbook. Forwarding to Google Ads is not available yet.
How each platform connects (Pinterest Ads and Amazon Ads can't be connected yet):
Shopify: Connect your store. Admaxxer imports about the last
60 days of orders and receives new orders from then on.
Meta: "Connect with Facebook", or paste a long-lived token.
Google Ads: Connect with Google sign-in.
TikTok Ads: Paste an access token from TikTok's business tools.
Klaviyo: Paste a private API key.
Pinterest /
Amazon Ads: Not available yet.
What to do with the data you've already paid for
Admaxxer has no importer for Triple Whale exports, so historical Triple Whale reports can't be loaded into Admaxxer's dashboards. Export what you want to keep before you cancel and store it for retrospective comparison.
Going forward, Admaxxer's pixel and your connected store and ad accounts are the source of truth. Inside Admaxxer, history starts with about the last 60 days of Shopify orders and grows from install day, so year-over-year comparisons for older periods come from your exports.
What to export from Triple Whale before you cancel:
- Orders and attribution reports for as much history as you need.
- Creative-level reports, for comparing creative performance year over year.
- Post-purchase survey responses, if you collected any there.
What goes wrong when teams rush this
Reading these before you start is the highest-leverage 90 seconds of your migration.
- Skipping the pixel parity window. You retire Triple Whale on day 1, then find on day 7 that Admaxxer's pixel misses purchases from an unusual checkout (a custom thank-you page or an off-Shopify subscription portal), with no second source to compare against.
- Comparing different attribution models. The two tools may credit the same orders differently because they use different models or windows. If you don't line the models up during the parity window, you'll see a 'gap' that is really a model difference, not a tracking gap.
- Expecting full order history on day 1. Shopify shares about the last 60 days of orders with apps, and orders before the Admaxxer pixel was installed have no visitor journey. Year-over-year comparisons inside Admaxxer build up from install day, so keep your Triple Whale exports for older periods.
- Expecting tokens to carry over. Connections can't be moved from Triple Whale. Reconnect each platform in Admaxxer on day 1 so data starts flowing straight away; connecting doesn't change your campaigns.
- Cancelling Triple Whale on day 7 instead of day 30. You lose the side-by-side comparison window. If a finance report in week 2 disagrees, you can't go back and check the other tool's numbers. The overlap costs less than one wrong budget decision.
The five items that close out the migration
About 30 minutes of work on day 30. Each item has a verifiable exit state - don't mark complete until you've checked the artefact.
- Confirm pixel parity. Compare Admaxxer's daily orders and revenue with Triple Whale's and your store's for the prior 14 days, and check the Tracking Health badge on Sources & Attribution. A steady, explained difference (for example a different attribution model) is fine; an unexplained gap is not.
- Confirm Shopify order totals. Compare Admaxxer's order count and revenue with Shopify Admin for the period Admaxxer covers. If the import on the Shopify connection shows as failed or incomplete, click Retry there before you go on.
- Export what you want to keep, then cancel Triple Whale. Export the historical Triple Whale reports you want to keep, then cancel the subscription from Triple Whale's billing settings before the next renewal. Check Triple Whale's own billing terms for when the cancellation takes effect.
- Remove the Triple Whale script from your store. Remove Triple Whale's pixel wherever it was installed: an app, a theme code snippet, or a custom pixel under Shopify Admin -> Settings -> Customer events. Save the change.
- Confirm the Triple Whale pixel stops firing. Reload your storefront in a fresh incognito window with DevTools -> Network open and filter by the domain the Triple Whale script used to load from. There should be zero requests. If anything remains, look for another place the tag was installed.
The first 60 days on Admaxxer
Once Triple Whale is retired, three surfaces are worth prioritising in your team's rotation. The first is Maxxer - the AI agent in /chat, running on your own AI provider key. It reads your Meta and Google Ads campaigns and your analytics, and changes a campaign only after you confirm. The Maxxer playbook explains what it can and can't do.
The second is Ads Manager, which puts each campaign's first-party revenue and ROAS next to the platform's own numbers, with a change history of every pause and budget edit.
The third is incrementality. Once you have a few weeks of data, read the incrementality testing guide to get a lift number for your main paid channels before making big budget moves.
Frequently asked questions
- Why a 30-day migration instead of a same-day switch?
- Two reasons. (1) Pixel parity: Admaxxer's pixel should run alongside your existing pixel for at least 14 days so you can confirm event counts and attribution are aligned, or different in ways you understand. (2) History: Admaxxer imports your recent Shopify orders (Shopify shares about the last 60 days by default), and older orders have no Admaxxer pixel journey, so attribution builds up from install day. By day 30 both tools have run side by side, your team has run its weekly reports in both, and the decision to retire Triple Whale is backed by data.
- Does my Triple Whale pixel conflict with the Admaxxer pixel?
- No. Admaxxer's pixel uses its own namespace and its own storage keys, so it does not interfere with another analytics pixel. You can run both for the whole overlap; the only cost is a little extra script weight. If you serve your current pixel from your own domain, you can do the same with Admaxxer's pixel through a proxy so ad blockers treat it as first-party.
- What about my historical attribution data in Triple Whale?
- Admaxxer has no importer for Triple Whale exports. Export the historical reports you want to keep from Triple Whale before you cancel and store them for retrospective comparison. Going forward, Admaxxer's pixel and your connected store and ad accounts are the source of truth.
- Can I migrate ad-platform tokens from Triple Whale or do I need to reconnect?
- You reconnect each platform in Admaxxer on /integrations: Meta with Connect with Facebook or a pasted token, Google Ads with Google sign-in, TikTok with an access token, plus your store. Connecting does not change your campaigns. Admaxxer only changes a campaign when you confirm it, either in Ads Manager or through Maxxer, its AI agent.
- What does the day-30 retirement look like in practice?
- (1) Confirm pixel parity: compare Admaxxer's daily orders and revenue with Triple Whale's and your store's for the prior 14 days, and check the Tracking Health badge on Sources & Attribution. (2) Confirm Admaxxer's order count and revenue match Shopify Admin for the period Admaxxer covers. (3) Cancel your Triple Whale subscription. (4) Remove the Triple Whale script from your Shopify theme and confirm it no longer loads in a fresh incognito session. Total time on day 30: about 30 minutes.
Run this playbook in your own dashboard
Admaxxer ships the pixel + server-side purchases to Meta, TikTok and Klaviyo + Maxxer AI agent + cohort analytics out of the box. The playbook above becomes a live surface in your account after a 5-minute setup.