AppLovin Shopify Integration: Pixel, Catalog and Validation Setup Before You Spend

The AppLovin Shopify integration is set up by installing the AppLovin app from the Shopify App Store, connecting your AppLovin Ads account, enabling the theme extension, confirming the AppLovin app embed is switched on in your theme, and saving. That gets the pixel on the store. It does not prove the data is right. Before you spend, validate your ecommerce events, purchase values, item data, transaction IDs, AppLovin click parameters and server-event deduplication, then connect purchase history and a clean product catalog.

This page is the implementation checklist. If you want the full picture of accounts, goals, audiences and bidding first, read how AppLovin works end to end. This page stays on the plumbing.

The short version

Step	What you do	What “done” means
1. Install	AppLovin app from the Shopify App Store → Connect existing account → Connect	The store shows as connected in AppLovin Ads Manager
2. App embed	Enable Theme Extension → confirm the AppLovin app embed is on → Save	The embed is on in the live theme, not only a draft theme
3. Validate	Check events in Events Manager and with the AppLovin Pixel Helper	Purchases arrive once, with value, currency, item data and a transaction ID
4. History	Connect Shopify or upload order history in Events Manager	Prospecting and Discovery have the purchase data they need
5. Catalog	Shopify sync, Pixel-built catalog or daily CSV feed	IDs, prices, availability, images and URLs match the store; disapprovals near zero
6. Measurement	Record the attribution mode and your comparison sources	You know what “platform ROAS” is counting before the first report

Non-Shopify store? Steps 3 to 6 are the same. Step 1 and 2 become the AppLovin Pixel through Google Tag Manager.

Why setup decides performance

AppLovin Ads optimizes toward the signal you send it. A missing purchase value, a doubled checkout event or a stale feed doesn’t throw an error. It just teaches the model the wrong thing, and the result shows up weeks later as “AppLovin doesn’t work for us.”

When nobody can say why performance dropped, WKND’s published view is that the cause is almost always the goal, the feed or fatigued creative. Two of those three are set during implementation.

Path A: the AppLovin Shopify app (step by step)

AppLovin’s Shopify integration documentation gives this sequence:

1. Install the AppLovin app from the Shopify App Store.
2. Choose Connect existing account.
3. Click Connect to link the store to your AppLovin Ads account.
4. Click Enable Theme Extension.
5. In the theme editor, confirm the AppLovin App embed is enabled.
6. Click Save.

AppLovin’s consumer brands page describes the AppLovin Pixel as installed through the Shopify App Store or Google Tag Manager. WKND’s earlier guide notes that AppLovin’s web setup guidance says the Shopify app can configure the pixel, purchase tracking and product catalog synchronization. AppLovin’s Shopify integration steps cover installing the app, connecting your account and enabling the App Embed; its order history guide adds that a Shopify store that installed and connected the app is ready for order history. After connecting, open the Catalog Manager in Ads Manager and confirm your products synced before you launch.

The step people miss: the app embed

Installing the app is not the same as tracking. The pixel loads through the theme’s app embed. If step 5 is skipped, or the embed is switched on in a draft theme that was never published, the app looks installed and nothing fires on the live store.

Check it in the theme editor of the published theme, then check again after any theme change or theme duplication. Publishing a new theme is an easy way for a working setup to break quietly.

Headless Shopify

On a headless storefront the theme extension may not be available. AppLovin’s documentation offers a Continue without theme extension option for that case. WKND’s earlier guide notes that AppLovin’s support documentation gives more specific headless instructions and cautions against sending checkout events through both GTM and the Shopify integration. That is the fastest way to double-count purchases. AppLovin’s Google Tag Manager guide is explicit: in a Shopify headless setup, let the Shopify app handle event tracking on the checkout page and do not fire the GTM pixel there.

Path B: connect from AppLovin Ads Manager

You can also start from the AppLovin side. In AppLovin Ads Manager, open your account name → Integrations → Connect Shopify → Go to Shopify App Store, then finish the same install and app embed steps. If you’re new to the interface, our AppLovin Ads Manager walkthrough shows where Integrations and Events Manager sit.

AppLovin pixel setup with Google Tag Manager (non-Shopify sites)

If your store isn’t on Shopify, AppLovin’s consumer brands page lists Google Tag Manager as the other supported way to install the AppLovin Pixel. AppLovin has a dedicated Google Tag Manager integration page in its support center.

We’re not reproducing the tag-by-tag steps here, because they’re the part of the setup most likely to change. Follow AppLovin’s Google Tag Manager guide: it installs the AppLovin Pixel as a Custom HTML tag with your event key, assumes a working ecommerce data layer, and tells Shopify sites to use the AppLovin Shopify app instead.

What doesn’t change on a GTM build:

• The pixel should fire on every page, not only product and checkout pages.
• Purchase must fire once per order, on the confirmation, with the order’s value and currency.
• If you also send server events, they need a shared ID so AppLovin can deduplicate them.
• Don’t run GTM and a platform integration for the same checkout events.

Lead-gen and service businesses have one more piece. WKND’s earlier guide notes AppLovin recommends its Conversion API alongside the Pixel, including sending lead values so low-quality leads can be valued at zero.

Validate the AppLovin pixel before you spend

This checklist comes straight from WKND’s published setup requirements: validate required ecommerce events, purchase value, item data, transaction IDs, AppLovin click parameters, and server-event deduplication.

Check	What to confirm	Why it matters
Required ecommerce events	AppLovin’s required events for purchase sites (page_view, view_item, add_to_cart, begin_checkout, purchase) fire on the right pages	Missing mid-funnel events leave the model with only the last step
Purchase value	Every purchase carries a value and the correct currency	ROAS bidding optimizes toward value. No value, no ROAS goal worth trusting
Item data	Product and variant IDs on events match the catalog	This is how events and catalog items connect
Transaction IDs	Each order sends a unique ID	Lets you reconcile against Shopify and spot duplicates
AppLovin click parameters	AppLovin’s click parameters survive redirects, UTMs and checkout	If they’re stripped, conversions can’t be tied back to the ad
Server-event deduplication	Browser and server events for the same order count once	Double-counted purchases inflate ROAS and mislead the model

How to run the checks

• Place a real test order and follow it into AppLovin Events Manager. Confirm it arrives once, with the value, currency and transaction ID you expect.
• Use the AppLovin Pixel Helper. It’s a Chrome extension, AppLovin Pixel Helper, linked from AppLovin’s site. It shows which pixel events fire on the page you’re viewing.
• Match the order in Shopify. Same transaction ID, same value. If the numbers differ, find out why now, not after a week of spend.
• Click a test ad link with AppLovin’s parameters through to checkout, and confirm they’re still present on the landing page and at purchase.
• Check the launch checklist. AppLovin publishes a web launch checklist. Use it as the platform’s minimum, and this table as ours.

Do not assume the pixel works because the tag exists. Verify the events AppLovin actually receives.

Upload purchase history in Events Manager

AppLovin’s audience strategies are Universal (all customer types), Prospecting (net-new customers) and Discovery (people who have never visited your site), according to its consumer brands page. WKND’s earlier guide notes that AppLovin’s support documentation says Prospecting and Discovery need sufficient historical purchase data, provided through the Shopify integration or by uploading purchase history. AppLovin introduced Discovery campaigns in February 2026.

That’s why this step belongs in setup, not later. Without history, the platform can’t tell a new customer from a returning one.

• On Shopify: connect the store so order history is available.
• Off Shopify, or with gaps: upload order history in Events Manager.
• The file: CSV only, up to 200 MB per file, with these exact headers: country_code, currency, email, event_name (always purchase), event_timestamp, transaction_id, user_id and value; zip is optional. AppLovin deduplicates on transaction_id and strongly encourages uploading all available order history (order history data).

If your goal is new-customer growth, and it usually should be for a channel you’re testing for incrementality, this step decides whether that goal is even available.

AppLovin dynamic catalog: feed setup and hygiene

After the video and Interactive Page, AppLovin can show a Dynamic Catalog of products before the click. Our guide to where the Dynamic Catalog sits inside the ad sequence covers the placement. Here’s the setup.

Three ways to build the catalog

Option	Best for	Watch out for
Shopify catalog	Shopify stores using the AppLovin app	Products excluded or unpublished in Shopify won’t be there to show
Pixel-built catalog	Stores where the pixel sees product data on pages	Only as good as the item data on your product pages
Daily CSV feed	Custom stacks, or when you need control over fields	A feed that stops refreshing goes stale without any alarm

AppLovin also documents third-party feed integrations.

What has to match

Whichever option you choose, match these to the live store:

• Item and variant IDs: the same IDs your pixel sends on events.
• Pricing: including sale prices.
• Availability: out-of-stock items shouldn’t be promoted.
• Images: usable, current product imagery.
• URLs: each item lands on the right product or variant page.

Offering Catalog for small assortments and services

If you sell a handful of products, or a subscription or service, AppLovin’s Dynamic Catalog documentation describes an Offering Catalog for smaller assortments and non-product offers such as service tiers, memberships and courses. AppLovin describes the Offering Catalog as best for brands with “fewer than five or six distinct products”, such as a core subscription offer.

Attribution discrepancy basics (read before your first report)

Your first AppLovin report won’t match Shopify, and it won’t match your attribution tool. That’s normal. The goal is to know why before it becomes an argument.

• Record the reporting mode. One AppLovin resource, Analyzing campaign performance, describes click-based attribution. The Support Center’s Measurement and attribution page describes two modes, Clicks and Clicks and views. Both are live AppLovin pages, so check which mode your account uses and keep it fixed when comparing periods.
• Know the windows. WKND’s earlier guide notes D0 covers the first 24 hours and D7 a 192-hour window, with D14 and D28 metrics also appearing in reporting.
• Expect fast conversions. AppLovin reports that “80% of web conversions happen within 24 hours of click.” That’s AppLovin’s figure, and it’s one reason D0 is a common starting point.
• Connect a comparison source. AppLovin lists third-party measurement integrations including Northbeam, Triple Whale and others.

Platform ROAS is the engine’s scorecard. Whether that revenue is incremental is a separate question, covered in AppLovin attribution and incrementality.

Common AppLovin Shopify setup failures

These are the failures we check first. Each one can look like a media problem.

1. App installed, embed off. The app shows as connected, the live theme has the embed disabled. Nothing fires.
2. Theme change broke tracking. A new or duplicated theme was published without the embed.
3. Purchases counted twice. Headless or custom checkout sending events through both GTM and the Shopify integration, or server events without deduplication.
4. Purchases without value. The event fires but carries no value or the wrong currency, so ROAS goals optimize toward noise.
5. Click parameters stripped. A redirect, link shortener or checkout step drops AppLovin’s parameters.
6. Event health not checked. When there’s no dedicated platform support, WKND checks open rejections and event health first.
7. Feed disapprovals. Missing fields or disapproved items shrink what the engine can show. We check the disapproval count in the Catalog Manager first.
8. Stale feed. The CSV stopped updating, or prices and stock drifted from the store. We check feed freshness next to disapprovals.
9. No purchase history. Prospecting or Discovery launched without the historical purchases they need.

If tracking and the feed are clean and delivery still stalls, the constraint is usually the goal or the creative. That’s covered in why AppLovin ads stop scaling.

How WKND handles this

Setup is its own service at WKND: AppLovin Axon setup and onboarding, part of managing Axon Ads Manager end to end, from account and feed setup onward.

What that includes, from our published requirements:

• Account and billing. New accounts use prepay. Add a backup card and 2FA, then invite WKND with the needed access level.
• Tracking. Shopify app or AppLovin Pixel via GTM, then the full validation list above: required ecommerce events, purchase value, item data, transaction IDs, AppLovin click parameters and server-event deduplication.
• Purchase history. Connect Shopify or upload order history in Events Manager so Prospecting and Discovery are available.
• Catalog. Shopify, Pixel-built catalog or daily CSV feed, matched on item/variant IDs, pricing, availability, images and URLs, or an Offering Catalog for smaller assortments and services.

The team behind it has managed $5M+ in Axon ad spend across 50+ Axon accounts and deployed 5,000+ Creative Sets since Axon Ads Manager opened.

Speed and accuracy aren’t a trade-off when the checklist is done in order. From one onboarding client:

“Dude we were live in 5 days. That has to be a record lol”

— Anand Dixit, Groomie

That’s one client’s experience, not a promised timeline. Setup time depends on your stack, your feed and how quickly access is granted.

If you’re already live and not sure the setup is right, our account review looks at exactly these inputs.

If you want the integration done and managed for you, see AppLovin agency for Shopify brands.

FAQ

Does AppLovin work with Shopify?

Yes. AppLovin has an app in the Shopify App Store. You install it, connect your AppLovin Ads account, enable the theme extension, confirm the AppLovin app embed is on and save. AppLovin describes the Shopify app and Google Tag Manager as the two ways to install the AppLovin Pixel.

How do I install the AppLovin Shopify app?

Install the AppLovin app from the Shopify App Store, choose Connect existing account, click Connect, click Enable Theme Extension, confirm the AppLovin App embed is enabled in your theme and click Save. You can also start in AppLovin Ads Manager under your account name → Integrations → Connect Shopify.

How do I set up the AppLovin pixel without Shopify?

Use Google Tag Manager. AppLovin lists GTM as the supported pixel path for non-Shopify sites and has a Google Tag Manager integration page in its support center. Follow AppLovin’s current GTM steps, then run the same validation checks: events, purchase value, item data, transaction IDs, click parameters and deduplication.

How do I know my AppLovin pixel is working?

Place a test order and confirm it appears once in AppLovin Events Manager with the right value, currency and transaction ID. Use the AppLovin Pixel Helper Chrome extension to see which events fire on each page. Then match the order to Shopify.

Does AppLovin work with headless Shopify?

It can, but the theme extension may not be available. AppLovin’s documentation includes a Continue without theme extension option and separate headless guidance. The main risk is sending checkout events through both GTM and the Shopify integration, which double-counts purchases.

What is the AppLovin dynamic catalog?

It’s the product or offer set AppLovin can show after the video and Interactive Page. You can build it from Shopify, from the pixel or from a daily CSV feed. Item and variant IDs, prices, availability, images and URLs should match your store. Smaller assortments and services can use an Offering Catalog.

Why doesn’t AppLovin match Shopify?

Different systems count differently: attribution mode, windows, time zones and view-through treatment all vary. Record which AppLovin reporting mode is active, keep it fixed, and reconcile against Shopify and a third-party tool. A large, unexplained gap is often a tracking issue such as duplicate purchases.

Get the setup checked before you spend

A broken setup doesn’t announce itself. It spends. If you’re launching AppLovin Ads, or you’re live and the numbers don’t add up, start with a review of the inputs.

GET AN AXON ACCOUNT REVIEW → Goal history · feed and event health · creative fatigue · incrementality readiness. Written findings inside five business days.