Facebook コンバージョン API (CAPI) 設定 ガイド for Shopify (2026)

If you run Facebook ads for your Shopify ストア, you have probably noticed that reported performance has deteriorated since Apple's iOS 14+ privacy changes rolled out. コンバージョン appear lower, ROAS seems worse, and your ad 最適化 feels less effective. The problem is not necessarily that your ads are performing worse — it is that your tracking is missing a large portion of コンバージョンs.

The Facebook Pixel is a JavaScript snippet that runs in the visitor's browser. When an iOS user opts out of tracking (which 75-85% now do), the Pixel cannot fire. When a visitor uses an ad blocker, the Pixel is blocked. When third-party cookies are restricted (increasingly the default), the Pixel's ability to match users degrades. The result: Facebook sees fewer コンバージョンs, attributes less 売上 to your ads, and optimizes your campaigns based on incomplete data.

Facebook コンバージョン API (CAPI) solves this by sending コンバージョン events directly from your Shopify server to Facebook's servers. いいえ browser involved, no JavaScript to block, no cookie to restrict. When a 顧客 completes a purchase on your Shopify ストア, Shopify sends the purchase event to Facebook server-to-server, along with 顧客 data (email, phone, IP address) that Facebook uses to match the コンバージョン to the ad click that initiated it.

This guide walks through the complete CAPI setup for Shopify, explains how event deduplication works, and covers how your on-site tools (ポップアップs, アップセルs, and other apps) interact with server-side tracking.

How Facebook コンバージョン API Works

The コンバージョン API is a server-side integration that allows you to send web events directly from your server to Facebook. Instead of relying on a browser-based pixel that runs JavaScript on the user's device, CAPI makes HTTPS POST requests from your server to Facebook's Graph API endpoint.

When a 顧客 takes an action on your Shopify ストア — views a product, adds to カート, initiates チェックアウト, or completes a purchase — two things happen simultaneously in a properly configured setup:

1. Browser-side (Pixel): The Facebook Pixel JavaScript fires in the visitor's browser and sends the event to Facebook. This works for visitors who have not blocked tracking.
2. Server-side (CAPI): Shopify's server sends the same event directly to Facebook via the コンバージョン API. This works regardless of the visitor's browser settings, iOS version, or ad blocker status.

Facebook receives both events, uses event deduplication to count them as a single コンバージョン (not double), and uses the server-side data to fill gaps where the pixel was blocked. The result is more complete コンバージョン data, better attribution, and more effective ad 最適化.

Pixel vs CAPI: Understanding Both Systems

機能	Facebook Pixel	コンバージョン API
How it sends data	Browser JavaScript	Server-to-server HTTPS
Blocked by iOS 14+	はい (for opted-out users)	いいえ
Blocked by ad blockers	はい	いいえ
Affected by cookie restrictions	はい	いいえ
Tracks browsing behavior	はい (PageView, scroll, etc.)	Limited (server-triggered events)
データ accuracy	60-80% (declining)	95%+ (server-verified)
設定 difficulty	Easy (paste code snippet)	Moderate (Shopify handles most)
Recommended use	Always on (alongside CAPI)	Always on (alongside Pixel)

iOS 14+ Impact on Facebook Ad Tracking

Apple's App Tracking Transparency (ATT) framework, introduced with iOS 14.5 in April 2021, fundamentally changed how Facebook advertising works. Here is what happened and why CAPI is now essential:

What Changed

Before iOS 14, the Facebook app on iPhones could track user activity across apps and websites using Apple's IDFA (Identifier for Advertisers). This allowed Facebook to see when someone who clicked an ad later purchased on your website, even across sessions and devices. When Apple required apps to ask permission before tracking, 75-85% of iOS users chose to opt out.

Impact on Shopify Advertisers

• Under-reported コンバージョンs: Facebook cannot see purchases from opted-out iOS users via the Pixel. A ストア with 50% iOS トラフィック might see 20-40% of コンバージョンs disappear from Facebook reporting.
• Degraded ad 最適化: Facebook's algorithm learns from コンバージョン data. With less data, it makes worse decisions about who to show your ads to, leading to higher CPAs and lower ROAS.
• Attribution window reduction: Facebook shortened the default attribution window from 28 days to 7 days, further reducing reported コンバージョンs.
• Limited event tracking: iOS 14+ limits each domain to 8 prioritized コンバージョン events, down from unlimited events before.

How CAPI Fixes These Issues

CAPI bypasses all browser-level restrictions because it sends data server-to-server. When a 顧客 completes a purchase, Shopify sends the purchase event to Facebook directly, along with 顧客 information (hashed email, phone number, and IP address) for user matching. Facebook can then attribute the purchase to the original ad click, even for opted-out iOS users.

Setting Up CAPI on Shopify (ステップ-by-ステップ)

Shopify has made CAPI setup straightforward through its Facebook & Instagram 販売 channel. いいえ custom coding is required for the standard implementation.

ステップ 1: Install the Facebook & Instagram Channel

In your Shopify admin, go to 販売 channels → Add channel → Facebook & Instagram. If you already have this channel installed, make sure it is updated to the latest version.

ステップ 2: Connect Your Facebook Business Manager

Follow the setup wizard to connect your Facebook Business Manager account. You will need to authenticate with a Facebook account that has admin access to the Business Manager. Select the correct Ad Account, Facebook Page, and Pixel to connect.

ステップ 3: Enable コンバージョン API

In the Facebook & Instagram channel settings, navigate to the データ sharing section. You will see three data sharing levels:

• Standard: Uses Facebook Pixel only (browser-side tracking).
• Enhanced: Uses Facebook Pixel with additional browser-side data matching.
• Maximum: Uses both Facebook Pixel and コンバージョン API (recommended). This is the setting you want.

Select Maximum to enable CAPI. Shopify will automatically configure server-side event sending for all standard ecommerce events.

ステップ 4: Verify Domain

Domain verification is required for proper CAPI and Aggregated Event Measurement (AEM) functionality. In Facebook Business Manager, go to Business Settings → Brand Safety → Domains. Add your Shopify domain and verify it using the DNS TXT record method or HTML meta tag method. Shopify's Facebook channel often handles this automatically.

ステップ 5: Configure Aggregated Event Measurement (AEM)

After domain verification, configure your 8 prioritized events in Events Manager. Go to Events Manager → Aggregated Event Measurement → Configure Web Events. Set your events in priority order (highest to lowest):

1. Purchase
2. Initiateチェックアウト
3. AddToカート
4. ViewContent
5. Lead (if you collect email signups)
6. AddPaymentInfo
7. Search
8. PageView

Events and Event Matching

CAPI sends events to Facebook using 顧客 matching parameters. The more parameters you provide, the higher the match rate — meaning Facebook can more accurately attribute コンバージョンs to ad clicks.

Key Matching Parameters

• Email address (hashed) — the strongest matching signal. Available when 顧客 provide their email at チェックアウト or through signup forms.
• Phone number (hashed) — another strong signal, especially for mobile コンバージョンs.
• IP address — helps match anonymous browsing sessions to known users.
• User agent — browser and device information used for probabilistic matching.
• fbclid — the Facebook click ID parameter appended to URLs when users click ads. The strongest deterministic matching signal when available.
• fbc and fbp cookies — Facebook browser cookies that Shopify can access and pass to CAPI.

Shopify's CAPI implementation automatically sends all available matching parameters. For purchase events (where the 顧客 has provided their email and phone at チェックアウト), match rates typically exceed 90%. For earlier funnel events (PageView, ViewContent), match rates are lower because less 顧客 data is available.

Event Deduplication: Avoiding Double-Counting

When both the Pixel and CAPI send the same event, Facebook needs to know they represent the same action, not two separate actions. This is handled through event deduplication using an event_id parameter.

When Shopify sends a Purchase event, both the Pixel and CAPI include the same event_id (typically the Shopify order ID). Facebook sees both events, matches them by event_id, and counts them as a single コンバージョン. If only one arrives (because the Pixel was blocked), Facebook counts the CAPI event alone.

Shopify's built-in integration handles deduplication automatically. If you are using custom CAPI implementations or third-party tracking apps, ensure they use the same event_id format as your Pixel events to avoid double-counting.

Testing Your CAPI 設定

After setup, verify that CAPI is working correctly before relying on its data for 最適化 decisions.

Use Facebook's Test Events Tool

In Events Manager, go to Test Events. This shows real-time events as they arrive from both the Pixel and CAPI. Visit your Shopify ストア, view a product, add to カート, and complete a test purchase. You should see events from both "Browser" (Pixel) and "Server" (CAPI) sources.

Check Event Match Quality

In Events Manager, navigate to the 概要 tab and check the Event Match Quality (EMQ) score for each event. This score (1-10) indicates how well your server events can be matched to Facebook users. Aim for a score of 6 or higher. Scores below 4 indicate missing 顧客 parameters.

Verify Deduplication

In the Test Events view, check that duplicate events are being properly deduplicated. You should see a "Deduplicated" label on matching Pixel/CAPI event pairs. If events are not being deduplicated, check that both sources are using the same event_id.

Monitor the Diagnostics Tab

Events Manager's Diagnostics tab flags issues with your setup — missing parameters, high error rates, or deduplication problems. Check this tab weekly for the first month after setup, then monthly after that.

How CAPI Works With ポップアップs, アップセルs, and Other アプリ

If you use Shopify apps like EA スピンホイール メールポップアップ for email collection or EA アップセル & クロスセル for アップセルs, you might wonder how these interact with CAPI tracking.

ポップアップ Email/SMS Signups

When a visitor submits their email through a スピンホイール ポップアップ, this is typically tracked as a Lead or CompleteRegistration event by the Facebook Pixel (browser-side). CAPI does not natively capture this event because it happens before チェックアウト. However, when that visitor later purchases, the email they provided at signup is sent to Facebook via CAPI as a matching parameter, improving the match rate for the purchase event.

In this way, ポップアップs actually improve CAPI performance — by collecting 顧客 email addresses earlier in the journey, you provide Facebook with a stronger matching signal for the eventual purchase event.

アップセル and クロスセル Purchases

When a 顧客 accepts an アップセル offer and adds an additional product to their order, the final purchase event captured by CAPI reflects the total order value, including any アップセル items. Facebook sees the full 売上 from the コンバージョン, which improves your reported ROAS. This is one reason why アップセル apps like EA アップセル & クロスセル are particularly valuable for Facebook advertisers — they increase the 売上 attributed to each Facebook-driven purchase.

送料無料バーs and Other コンバージョン ツール

On-site コンバージョン tools like 送料無料 bars, sticky add-to-カート buttons, and カウントダウンタイマーs operate independently of CAPI. They influence the visitor's behavior on your ストア (increasing the likelihood and size of a purchase), and CAPI captures the resulting purchase event with the full order value. Better on-site コンバージョン means more purchase events for Facebook's algorithm to optimize against.

Optimizing CAPI for Maximum ROAS

Once CAPI is set up and verified, these 最適化s squeeze more value from your Facebook advertising:

1. Maximize event match quality. Send as many 顧客 parameters as possible — email, phone, name, city, state, zip code. Shopify sends most of these automatically for purchase events. For earlier funnel events, collecting email through ポップアップs provides additional matching signals.
2. Use value-based 最適化. With accurate purchase data from CAPI, enable value-based bidding in your Facebook campaigns. This tells Facebook to optimize for highest-value purchases, not just any purchase, improving ROAS.
3. Monitor event match quality weekly. A drop in EMQ score often indicates a technical issue — check that the Facebook channel is properly connected and all matching parameters are being sent.
4. Keep the Pixel and CAPI running simultaneously. Do not remove the Pixel when you add CAPI. The Pixel still captures real-time browsing signals that CAPI cannot (scroll depth, time on page, micro-interactions) which help Facebook build richer audience profiles.
5. Prioritize your コンバージョン events correctly. Under AEM, arrange your 8 events with Purchase as the highest priority. Facebook will always attempt to capture the highest-priority event for each user within the 7-day attribution window.
6. Use UTM parameters consistently. While CAPI handles Facebook attribution, UTM parameters help you verify Facebook's reported data against your own analytics (GA4, Shopify アナリティクス) for a more complete performance picture.

Common CAPI Issues and Solutions

Issue: Event Match Quality score is low (below 4). Ensure Shopify's Facebook channel is set to "Maximum" data sharing. Check that 顧客 email and phone fields are populated at チェックアウト. デメリットider collecting emails earlier via ポップアップ forms to improve matching.

Issue: Events are being double-counted. Check that event deduplication is working by verifying event_id consistency between Pixel and CAPI events. If using a third-party tracking app alongside Shopify's built-in channel, you may have conflicting implementations.

Issue: CAPI events show in test mode but not in production. Ensure your Facebook channel is fully connected and not in a disconnected or error state. Go to the channel settings and re-authenticate if needed. Check for any API errors in the Diagnostics tab.

Issue: Reported コンバージョンs still seem too low. CAPI recovers most but not all lost コンバージョンs. Some data loss is permanent under iOS ATT. Focus on trends rather than absolute numbers — if your ROAS trend improves after CAPI implementation, it is working correctly.

よくある質問

とは Facebook コンバージョン API for Shopify?

Facebook コンバージョン API (CAPI) is a server-side tracking method that sends コンバージョン events directly from Shopify's servers to Facebook. Unlike the Facebook Pixel which runs in the visitor's browser and can be blocked by iOS privacy settings, ad blockers, and cookie restrictions, CAPI sends data server-to-server and cannot be blocked. It recovers 20-40% of コンバージョン data lost to iOS 14+ privacy changes.

How do I set up Facebook コンバージョン API on Shopify?

Install Shopify's Facebook & Instagram 販売 channel. Connect your Facebook Business Manager. In the channel's データ Sharing settings, select "Maximum" to enable both Pixel and CAPI. Verify your domain in Facebook Business Manager. Configure your 8 prioritized events under Aggregated Event Measurement. Shopify handles all server-side event sending automatically — no coding required.

Does Facebook CAPI replace the Facebook Pixel?

いいえ. CAPI works alongside the Pixel, not as a replacement. The recommended setup uses both simultaneously. The Pixel captures browser-side events from non-iOS users and provides real-time browsing signals. CAPI captures コンバージョンs from iOS users and ad-blocker users that the Pixel misses. Facebook deduplicates matching events using event_id to avoid double-counting.

なぜ is my Facebook ad ROAS dropping after iOS 14?

iOS 14+ App Tracking Transparency requires apps to ask permission before tracking, and 75-85% of users opt out. Without CAPI, the Facebook Pixel cannot see these users' コンバージョンs, causing artificially deflated ROAS numbers. Your ads may be performing better than reported. Setting up CAPI recovers the lost data, giving Facebook more accurate numbers to report and optimize against.

Do ポップアップs and アップセルs track through Facebook コンバージョン API?

ポップアップ interactions (like email signups from EA スピンホイール ポップアップ) are typically tracked by the Pixel as Lead events. CAPI handles the purchase event server-side. When ポップアップs collect email addresses, they actually improve CAPI performance by providing Facebook with a matching parameter for the eventual purchase. アップセル 売上 is included in the total purchase value captured by CAPI.

向上させる Facebook ROAS With Better コンバージョン率s

Accurate tracking with CAPI is step one. ステップ two is converting more of your Facebook トラフィック. EA apps increase コンバージョン率s, AOV, and email capture — all of which improve your Facebook ad performance. 無料 to install.

Browse All EA アプリ — 無料